public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: James E Wilson <wilson@specifixinc.com> To: Paul Lew <paullew@cisco.com> Cc: gcc-bugs@gcc.gnu.org Subject: Re: conflict include file names found in gcc-3.4.1 Date: Sat, 21 Aug 2004 02:58:00 -0000 [thread overview] Message-ID: <4126BA43.1070100@specifixinc.com> (raw) In-Reply-To: <16677.17049.930423.454362@cns-build4.cisco.com> Paul Lew wrote: > > uname -r > 2.4.20-20.7.cisco.4smp This doesn't give me any useful info about the target. This is just a kernel version. I need CPU architecture, OS, etc. See http://gcc.gnu.org/bugs.html for info on reporting bugs. > -I/auto/insbu-cnstools/include -I. -I. > -I../../gcc-3.4.1/gcc -I../../gcc-3.4.1/gcc/. > -I../../gcc-3.4.1/gcc/../include > ../../gcc-3.4.1/gcc/c-opts.c -o c-opts.o If you look at the FSF gcc Makefile, you will see that -I. is the first directory in the include path. Look at the INCLUDES rule. I am guessing that you have local modifications that add the -I/auto/insbu-cnstools/include directory, and that these local mods are putting it in the wrong place. If this is an FSF gcc problem, you will have to explain where the -I/auto/... is coming from. I don't see any explanation other than local mods. The problem here may be that you did not give us complete info. We need to know how to reproduce the problem before we can fix it, and that includes info such as how you configured gcc. -- Jim Wilson, GNU Tools Support, http://www.SpecifixInc.com
next prev parent reply other threads:[~2004-08-21 2:58 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2004-08-20 0:30 Paul Lew 2004-08-21 2:58 ` James E Wilson [this message] 2004-08-25 1:49 ` Paul Lew 2004-08-25 3:59 ` James E Wilson 2004-08-25 5:14 ` Paul Lew
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=4126BA43.1070100@specifixinc.com \ --to=wilson@specifixinc.com \ --cc=gcc-bugs@gcc.gnu.org \ --cc=paullew@cisco.com \ /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).