Hi Bruno, I never followed up on this, sorry.
On Sun, Dec 26, 2010 at 04:46:14PM +0100, Bruno Haible wrote: > Hi, > > Reviving an old thread from February 2010. > In <http://lists.gnu.org/archive/html/autoconf/2010-02/msg00013.html> > > There is a bug open about this, though: > <http://gcc.gnu.org/bugzilla/show_bug.cgi?id=40411> > Thank you for commenting on that bug, I agree completely. > I hope this flag won't be used by GCC, because it's a bad idea, just > like the _fmode variable on Windows. It turns out the HP-UX does a very similar thing, but is dependent on the setting of UNIX95 or UNIX_STD environment variables rather than compiler flags (see standards(5) and /usr/lib/unix*.o /usr/lib/hpux*/unix*.o etc). However we've never run into it on HP-UX, mostly because autoconf does not export any env vars in AC_PROG_CC_C99/AC_PROG_CC_STDC, it does, however add -xc99=all on solaris, so even though we consistently set CC, CFLAGS and so on at build time, we sometimes get libraries with __xpg symbols dependent on whether the configure.ac has one of those two macros. We patch our autoconf to not add -xc99=all to avoid the issue. Peter -- Peter O'Gorman [email protected] _______________________________________________ Autoconf mailing list [email protected] http://lists.gnu.org/mailman/listinfo/autoconf
