public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Bui Ngoc Huy Binh <Binh.Bui@sophia.inria.fr>
To: Claudio Bley <bley@cs.uni-magdeburg.de>
Cc: gcc-help@gcc.gnu.org
Subject: Re: warnings when compiling
Date: Mon, 21 Oct 2002 04:29:00 -0000	[thread overview]
Message-ID: <3DB3E51D.C6C0AE3C@sophia.inria.fr> (raw)
In-Reply-To: <15795.57215.649515.876285@wh2-19.st.uni-magdeburg.de>

that's ok now. 

thanks.
:)


Claudio Bley wrote:
> 
> >>>>> "Bui" == Bui Ngoc Huy Binh <Binh.Bui@sophia.inria.fr> writes:
> 
>     Bui> Hi, I use gcc release 3.2 to compile my programe. That's ok
>     Bui> but I got the warnings as:
> 
>     Bui> cc1: warning: changing search order for system directory
>     Bui> "/usr/local/include" cc1: warning: as it has already been
>     Bui> specified as a non-system directory ignoring duplicate
>     Bui> directory "/usr/local/include" cc1: warning: changing search
>     Bui> order for system directory "/usr/include" cc1: warning: as it
>     Bui> has already been specified as a non-system directory
> 
>     Bui> I don't understand and i don't know how to fix them ? Can you
>     Bui> help me ?
> 
> I suppose you installed gcc in /usr/local. GCC then regards
> /usr/local/include as a system include directory which implicitly is
> searched for header files after any other non-system include
> directories.
> 
> If you specify -I/usr/local/include (what you don't need to) GCC
> denotes this directory now as a non-system directory and thus changes
> the search order for header files which it was just kind enough
> informing you about.
> 
> Just don't specify /usr/local/include as non-system include directory
> if it already is a system directory.
> 
> >From 'man cpp':
> 
> -I directory
>     Add the directory directory to the end of the list of directories
>     to be searched for header files.  This can be used to override a
>     system header file, substituting your own version, since these
>     directories are searched before the system header file
>     directories.  If you use more than one `-I' option, the
>     directories are scanned in left-to-right order; the standard
>     system directories come after.
> 
> --
> Claudio Bley                                 ASCII ribbon campaign (")
> Debian GNU/Linux advocate                     - against HTML email  X
> http://www.cs.uni-magdeburg.de/~bley/                     & vCards / \

      reply	other threads:[~2002-10-21 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-21  3:05 Bui Ngoc Huy Binh
2002-10-21  4:05 ` Claudio Bley
2002-10-21  4:29   ` Bui Ngoc Huy Binh [this message]

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=3DB3E51D.C6C0AE3C@sophia.inria.fr \
    --to=binh.bui@sophia.inria.fr \
    --cc=bley@cs.uni-magdeburg.de \
    --cc=gcc-help@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: link
Be 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).