public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/48910] Current working directory in system include search path
Date: Fri, 06 May 2011 10:59:00 -0000	[thread overview]
Message-ID: <bug-48910-4-pUbDSfWReu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-48910-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48910

--- Comment #1 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-05-06 10:59:15 UTC ---
On Fri, 6 May 2011, Adam_5Wu at Hotmail dot com wrote:

> The workaround is to stop inserting "." in the system include search path
> chain.
> 
> In file gcc-4.6.0/gcc/incpath.c, replace
> path = xstrdup (".");
> with
> continue;

But that code is processing an environment variable, and it's absolutely 
standard that empty elements in PATH-like environment variables are 
processed as ".".

What environment variable is set to contain an empty element, and how did 
it get set like that?  The problem is that the environment variable is 
set, and the fix must be to stop it from being set.  If the variable was 
not set by something in GCC, then this is not a GCC bug but a problem with 
your build environment.


  reply	other threads:[~2011-05-06 10:59 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-06  5:34 [Bug c/48910] New: " Adam_5Wu at Hotmail dot com
2011-05-06 10:59 ` joseph at codesourcery dot com [this message]
2011-05-06 20:11 ` [Bug c/48910] " Adam_5Wu at Hotmail dot com
2011-07-23 23:15 ` pinskia at gcc dot gnu.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=bug-48910-4-pUbDSfWReu@http.gcc.gnu.org/bugzilla/ \
    --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: 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).