public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "rrr6399 at futuretek dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/12611] Gcc doesn't handle SGI's modularized compiler setup Date: Tue, 14 Oct 2003 03:08:00 -0000 [thread overview] Message-ID: <20031014030824.31469.qmail@sources.redhat.com> (raw) In-Reply-To: <20031014025253.12611.rrr6399@futuretek.com> PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org. http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12611 ------- Additional Comments From rrr6399 at futuretek dot com 2003-10-14 03:08 ------- I moved the -I to the end of the list: stage1/xgcc -Bstage1/ -B/u/ba/rrr6399/opt/gcc-3.3.1/mips-sgi-irix6.5/bin/ -c -g -O2 -DIN_GCC -W -Wall -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -DHAVE_CONFIG_H -I. -Ijava -I. -I./java -I./config -I./../include -I/opt/MIPSpro/74/usr/include java/gjavah.c -o java/gjavah.o and got much better results: In file included from system.h:45, from java/gjavah.c:28: /opt/MIPSpro/74/usr/include/stdio.h:235: warning: conflicting types for built-in function `snprintf' /opt/MIPSpro/74/usr/include/stdio.h:244: warning: conflicting types for built-in function `vsnprintf' /opt/MIPSpro/74/usr/include/stdio.h:269: warning: ignoring #pragma int_to_unsigned fread /opt/MIPSpro/74/usr/include/stdio.h:271: warning: ignoring #pragma int_to_unsigned fwrite In file included from /opt/MIPSpro/74/usr/include/ulocks.h:295, from /opt/MIPSpro/74/usr/include/malloc.h:85, from system.h:313, from java/gjavah.c:28: /opt/MIPSpro/74/usr/include/task.h:123: warning: function declaration isn't a prototype Is there a way to tell gcc to look in /opt/MIPSpro/74/usr/include as the last resort? Thanks, Rob
next prev parent reply other threads:[~2003-10-14 3:08 UTC|newest] Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-10-14 2:52 [Bug bootstrap/12611] New: " rrr6399 at futuretek dot com 2003-10-14 3:08 ` rrr6399 at futuretek dot com [this message] 2003-10-14 3:37 ` [Bug bootstrap/12611] " pinskia at gcc dot gnu dot org 2003-10-14 4:46 ` rrr6399 at futuretek dot com 2003-10-14 4:49 ` pinskia at gcc dot gnu dot org 2003-10-22 6:06 ` wilson at specifixinc dot com 2003-10-24 23:27 ` dhazeghi at yahoo dot com 2003-10-25 1:39 ` pinskia at gcc dot gnu dot org 2003-10-28 2:50 ` rrr6399 at futuretek dot com 2003-10-28 2:56 ` rrr6399 at futuretek dot com 2003-11-08 21:09 ` dhazeghi at yahoo dot com 2003-11-11 14:09 ` rrr6399 at futuretek dot com 2003-11-12 21:52 ` ro at techfak dot uni-bielefeld dot de 2003-11-13 1:57 ` rrr6399 at futuretek dot com 2004-01-21 18:19 ` dhazeghi at yahoo dot com 2004-02-21 15:39 ` rrr6399 at futuretek dot com
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=20031014030824.31469.qmail@sources.redhat.com \ --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).