-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 According to Simon Josefsson on 6/13/2009 10:43 AM: >> Looks pretty much like one of the glibc memchr bugs that were recently fixed: >> <http://sourceware.org/bugzilla/show_bug.cgi?id=10162> > > I'm not sure, the machine where this fails runs glibc 2.7 and the bug > appears to be about glibc 2.10? The machine appears to be a debian > lenny machine. It is GCC compile farm host gcc60, if you have an > account.
I don't (yet, although I should look into getting one). Hey, does the strstr test also fail on this machine, even with the fixed memchr.m4? The logs you pointed to were for SASL, which did not use the strstr module. If test-strstr fails (which I suspect it will), then I need to also modify strstr.m4 to declare that the system strstr needs replacing if memchr is broken. - -- Don't work too hard, make some time for fun as well! Eric Blake e...@byu.net -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (Cygwin) Comment: Public key at home.comcast.net/~ericblake/eblake.gpg Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAko3HroACgkQ84KuGfSFAYDK1wCdH4Hj3qN9aISVlpT8BVildnkA 3gAAn1YhZ6kprsPFGhjMY114sb9J5gfq =/5xu -----END PGP SIGNATURE-----
