public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/4225: bad reference in an object file caused by the include method
Date: Thu, 21 Nov 2002 18:56:00 -0000	[thread overview]
Message-ID: <20021116020604.15765.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/4225; it has been noted by GNATS.

From: Wolfgang Bangerth <bangerth@ticam.utexas.edu>
To: gcc-gnats@gcc.gnu.org
Cc:  
Subject: Re: c++/4225: bad reference in an object file caused by the include
 method
Date: Fri, 15 Nov 2002 20:04:43 -0600 (CST)

 Presently (i.e. at the 3.2.1 stage), the documentation says:
   `CPATH'
   `C_INCLUDE_PATH'
   `CPLUS_INCLUDE_PATH'
   `OBJC_INCLUDE_PATH'
      [...]
 
      `CPATH' specifies a list of directories to be searched as if
      specified with `-I', but after any paths given with `-I' options
      on the command line.  The environment variable is used regardless
      of which language is being preprocessed.
 
      The remaining environment variables apply only when preprocessing
      the particular language indicated.  Each specifies a list of
      directories to be searched as if specified with `-isystem', but
      after any paths given with `-isystem' options on the command line.
 
 I.e., only the part that -isystem implies extern "C" on some systems is 
 now missing. Or at least I could not find it anywhere -isystem is 
 mentioned.
 
 W.
 
 -------------------------------------------------------------------------
 Wolfgang Bangerth              email:           bangerth@ticam.utexas.edu
                                www: http://www.ticam.utexas.edu/~bangerth
 
 


             reply	other threads:[~2002-11-16  2:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-21 18:56 Wolfgang Bangerth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-09-04 15:27 aoliva
2001-09-04  8:26 abetton

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=20021116020604.15765.qmail@sources.redhat.com \
    --to=bangerth@ticam.utexas.edu \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).