The gnulib "replace random stuff in libc!" legacy approach to portability bites even glibc... https://sourceware.org/ml/libc-alpha/2015-02/msg00181.html …
-
-
Replying to @RichFelker
@RichFelker glibc is treated the same for gnulib portability checks. We do try to adjust glibc though so the replacements are shortlived1 reply 0 retweets 0 likes -
Replying to @pixelbeat_
@pixelbeat_ Is there an easy way to run all the gnulib checks outside of a particular project's build and get REASONS for any that fail?1 reply 0 retweets 0 likes -
Replying to @RichFelker
@RichFelker For how, see https://sourceware.org/glibc/wiki/Testing/Gnulib …. For why, see var names etc. in config.log. Also th gnulib docs aim to document reasons1 reply 0 retweets 0 likes
Replying to @pixelbeat_
@pixelbeat_ Last time I looked lots of the tests had had various error bits in their return codes and no doc of values except by RTFSing.
8:04 AM - 11 Feb 2015
0 replies
0 retweets
0 likes
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.