I'm confused. Are you actually reporting something that causes Apache to fail to build, or are you just propagating misinformation because it's on a web site?
Apache has built fine for me since 2.0.40 (for which I submitted some patches to get sigwait identified properly, which were graciously accepted). I'm not sure I understand the extent of the bug in the autoconf code. Isn't it just doing a compile-time test to see what the function prototype for setpgrp is? If so, passing 0 or 1 is irrelevant, since the code will never actually be run. How does Apache fail because of this, or how do other projects fail which might affect Apache? Shantonu > |From http://www.osxgnu.org/#jagbugs > | > |"August, 31 2002: Major Bug found in the GNU Autoconf implementation on > |10.2 Jaguar! > |In the file /usr/share/autoconf/autoconf.m4f line 7294 should read: > | > |exit (setpgrp (0,0) == -1);])], > | > |not > | > |exit (setpgrp (1,1) == -1);])], > |As a result any program using GNU configure may not compile (just about > |all of them). \ > |You may wish to edit this file to reflect the above changes" -- > > >
