This is the mail archive of the gcc-bugs@gcc.gnu.org mailing list for the GCC project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

[Bug bootstrap/12173] IRIX 6 O32 (with as) bootstrap failure due to gcc -g -E warning


PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12173



------- Additional Comments From aoliva at gcc dot gnu dot org  2003-09-12 15:08 -------
This could be construed as a bug in autoconf.  It's already fixed in autoconf
2.5x, that knows to ignore warning messages from the preprocessor when testing
for header files.  Anyway, if -g is not supported, it shouldn't be passed down
to target library configuration, right?

As for why we have to pass -g to the preprocessor, I might instead pass
-fworking-directory if there's any -g* in the command line and no
-fno-working-directory.  This would solve the immediate problem.  The
alternative would be to have -fworking-directory enabled by default, which would
(slightly) impact those who don't need entirely-accurate debug information (or
error mesasges, FWIW).

Which one would be preferrable?


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]