New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not OK: perl v5.7.3 +DEVEL16824 on i686-linux-64int 2.4.18 (UNINSTALLED) #5489
Comments
From @nwc10../perl -Ilib t/op/int.t This is the same failure that Kay Röpke sees on his smoke I don't know what the problem is (yet) Nicholas Clark Perl Info
|
From [Unknown Contact. See original ticket]On Tue, 28 May 2002 21:07 +0100, Nicholas Clark wrote:
I saw the same problem this morning and it is a glibc bug: -- |
From @nwc10On Tue, May 28, 2002 at 11:17:55PM +0300, Radu Greab wrote:
Thanks. I'm not going mad. And I don't now have to track it down. 1: Detect this at Configure time? Nicholas Clark |
From [Unknown Contact. See original ticket]On Tue, 28 May 2002 22:22 +0100, Nicholas Clark wrote:
Yes, we can work round it by making sure that the second operand of Inline Patch--- pp.c~ Tue May 21 19:01:32 2002
+++ pp.c Wed May 29 00:57:54 2002
@@ -2422,6 +2422,10 @@
dPOPTOPiirl;
if (!right)
DIE(aTHX_ "Illegal modulus zero");
+#ifdef HAS_MODDI3_NEG_BUG
+ if (right < 0)
+ right = -right;
+#endif
SETi( left % right );
RETURN;
}
> 1: Detect this at Configure time?
Could someone skilled at this do the following Configure test: if we Test code: #include <stdio.h> int main() { Thanks, |
From @jhi
At this point in time I prefer any combination of the below: (1) pod/perldelta.pod entry warning about glibc 2.2.5 But I do not feel like twiddling with Configure now, especially -- |
From @nwc10On Wed, May 29, 2002 at 02:17:00AM +0300, Jarkko Hietaniemi wrote:
I was also wondering if we're even doing the right thing with all our games Equally well, any machine with a current buggy library would like the This is partly a question about why we work around broken things that are (3) TODO test in t/op/int.t if we have a way of knowing the libc version. Nicholas Clark |
From @jhiOn Wed, May 29, 2002 at 09:38:58AM +0100, Nicholas Clark wrote:
This is what I did now.
-- |
From @jhiI think this got resolved, so I'm marking the problem ticket as such. |
@jhi - Status changed from 'open' to 'resolved' |
@nwc10 - Status changed from 'resolved' to 'open' |
From @nwc10It's still live, and a couple of smokers are now seeing it. I think the |
From @rspierFinally fixed by jhi in the thread starting with.... Date: Sat, 1 Mar 2003 22:57:51 +0200 Change 18797. |
@rspier - Status changed from 'open' to 'resolved' |
Migrated from rt.perl.org#9402 (status was 'resolved')
Searchable as RT9402$
The text was updated successfully, but these errors were encountered: