public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pilot.mm at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug preprocessor/66932] Preprocessor includes wrong header file
Date: Sun, 19 Jul 2015 17:51:00 -0000 [thread overview]
Message-ID: <bug-66932-4-f4iM8DAw1r@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-66932-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66932
--- Comment #3 from Michael McWilliam <pilot.mm at gmail dot com> ---
(In reply to Jonathan Wakely from comment #2)
> Works for me too, with any version.
>
> gcc_bug$ which gcc
> ~/gcc/4.9.3/bin/gcc
> gcc_bug$ cd gas
> gas$ ./compile.sh
> ^[[3~In file included from ./../include/alloca-conf.h:2:0,
> from as.h:2,
> from as.c:2:
> ./config.h:2:2: warning: #warning "You have included the correct include
> file" [-Wcpp]
> #warning "You have included the correct include file"
> ^
>
>
> Please provide the output of: echo $CPATH $C_INCLUDE_PATH
CPATH is empty
C_INCLUDE_PATH is:
:/usr/local/atlas/include:/usr/local/atlas/include/atlas:/usr/local/atlas/include:/usr/local/atlas/include/atlas
So when I remove the leading : in C_INCLUDE_PATH and delete the duplicated
entries, magically it works. So clearly there is an error on my machine on the
way environment variables are being set... I will have to fix that...
I suppose the problem is a NULL path in the variable leads to undefined
behaviour... maybe gcc could be improved to ignore null paths or spit a warning
or something?
next prev parent reply other threads:[~2015-07-19 17:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-18 19:54 [Bug preprocessor/66932] New: " pilot.mm at gmail dot com
2015-07-19 2:49 ` [Bug preprocessor/66932] " pinskia at gcc dot gnu.org
2015-07-19 13:42 ` redi at gcc dot gnu.org
2015-07-19 17:51 ` pilot.mm at gmail dot com [this message]
2015-07-20 9:27 ` pinskia at gcc dot gnu.org
2021-07-18 23:03 ` 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-66932-4-f4iM8DAw1r@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).