public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "gcc-bugzilla at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/12173] New: IRIX 6 O32 (with as) bootstrap failure due to gcc -g -E warning Date: Thu, 04 Sep 2003 22:36:00 -0000 [thread overview] Message-ID: <20030904223557.12173.ro@techfak.uni-bielefeld.de> (raw) 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 Summary: IRIX 6 O32 (with as) bootstrap failure due to gcc -g -E warning Product: gcc Version: 3.4 Status: UNCONFIRMED Severity: critical Priority: P2 Component: bootstrap AssignedTo: unassigned at gcc dot gnu dot org ReportedBy: ro at techfak dot uni-bielefeld dot de CC: gcc-bugs at gcc dot gnu dot org GCC build triplet: mips-sgi-irix6.5o32 GCC host triplet: mips-sgi-irix6.5o32 GCC target triplet: mips-sgi-irix6.5o32 Between 20030703 and 20030808, bootstrap of mips-sgi-irix6.5o32 (with native as) started to fail configuring libf2c and libobjc. configure: error: Can't find stdio.h. You must have a usable C system for the target already installed, at least including headers and, preferably, the library, before you can configure the G77 runtime system. If necessary, install gcc now with `LANGUAGES=c', then the target library, then build with `LANGUAGES=f77'. make[1]: *** [configure-target-libf2c] Error 1 Looking at config.log, one finds the following: configure:2442: checking for stdio.h configure:2452: /vol/gcc/obj/gcc-3.4-20030808/6.5o32-cc-as/gcc/xgcc -B/vol/gcc/obj/gcc-3.4-20030808/6.5o32-cc-as/gcc/ -B/vol/gcc/share/mips-sgi-irix6.5o32/bin/ -B/vol/gcc/share/mips-sgi-irix6.5o32/lib/ -isystem /vol/gcc/share/mips-sgi-irix6.5o32/include -isystem /vol/gcc/share/mips-sgi-irix6.5o32/sys-include -E -O2 -g conftest.c >/dev/null 2>conftest.out cc1: warning: target system does not support debug output configure: failed program was: #line 2447 "configure" #include "confdefs.h" #include <stdio.h> Comparing this with the old (good) bootstrap, the difference is in the cc1 warning. This boils down to the following minimal testcase: touch test.c ./xgcc -B./ -E -O2 -g test.c > /dev/null cc1: warning: target system does not support debug output I get this warning as of 20030808, but there is no output on 20030703. This is most certainly due to Neil's option processing rewrite. The warning happened before when compiling: ./xgcc -B./ -c -g test.c cc1: warning: `-g': unknown or unsupported -g option The wording is changed now: cc1: warning: target system does not support debug output Environment: System: IRIX sculptor 6.5 07141608 IP32 host: mips-sgi-irix6.5o32 build: mips-sgi-irix6.5o32 target: mips-sgi-irix6.5o32 configured with: /vol/gnu/src/gcc/gcc-dist/configure --prefix=/vol/gcc --with-local-prefix=/vol/gcc --disable-nls mips-sgi-irix6.5o32 How-To-Repeat: Bootstrap gcc as above.
next reply other threads:[~2003-09-04 22:36 UTC|newest] Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-09-04 22:36 gcc-bugzilla at gcc dot gnu dot org [this message] 2003-09-04 22:44 ` [Bug bootstrap/12173] " ro at techfak dot uni-bielefeld dot de 2003-09-04 22:48 ` ro at gcc dot gnu dot org 2003-09-11 21:43 ` ro at gcc dot gnu dot org 2003-09-11 21:46 ` ro at techfak dot uni-bielefeld dot de 2003-09-12 5:26 ` neil at daikokuya dot co dot uk 2003-09-12 15:10 ` aoliva at gcc dot gnu dot org 2003-09-15 20:36 ` ro at techfak dot uni-bielefeld dot de 2003-09-15 21:02 ` ro at techfak dot uni-bielefeld dot de 2003-09-25 18:43 ` ro at techfak dot uni-bielefeld dot de 2003-09-29 17:48 ` aoliva at gcc dot gnu dot org 2003-09-29 19:45 ` ro at techfak dot uni-bielefeld dot de 2003-10-02 0:21 ` ro at techfak dot uni-bielefeld dot de 2003-10-07 21:14 ` cvs-commit at gcc dot gnu dot org 2003-10-07 21:16 ` ro at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20030904223557.12173.ro@techfak.uni-bielefeld.de \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).