public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: prj@po.cwru.edu
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/9427: gcc 3.2.1 -traditional ignores C_INCLUDE_PATH
Date: Thu, 23 Jan 2003 22:06:00 -0000	[thread overview]
Message-ID: <20030123215908.17491.qmail@sources.redhat.com> (raw)


>Number:         9427
>Category:       preprocessor
>Synopsis:       gcc 3.2.1 -traditional ignores C_INCLUDE_PATH
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    unassigned
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Thu Jan 23 22:06:00 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator:     prj@po.cwru.edu
>Release:        gcc version 3.2.1
>Organization:
>Environment:
This is a GNU/Linux system on dual i686 processors.  
>Description:
With -traditional, gcc ignores at least C_INCLUDE_PATH.  I
haven't checked the related variables to see if they work.
This has been broken at least since 3.1, but 2.95.3 works.

$ gcc -v
Reading specs from /package/misc/spf/gcc/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs
Configured with: ../gcc-3.2.1/configure --prefix=/package/misc/spf/gcc-3.2.1-1 --with-as=/package/misc/spf/gcc-3.2.1-1/spf/as --with-ld=/package/misc/spf/gcc-3.2.1-1/spf/ld --enable-threads --enable-libgcj --disable-nls
Thread model: posix
gcc version 3.2.1
>How-To-Repeat:
$ mkdir foo

$ echo foo > foo/foo.h

$ echo '#include <foo.h>' > bar.h

$ C_INCLUDE_PATH=`pwd`/foo gcc -E bar.h 
# 1 "bar.h"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "bar.h"
# 1 "/home/prj/foo/foo.h" 1 3
foo
# 2 "bar.h" 2

$ C_INCLUDE_PATH=`pwd`/foo gcc -E -traditional bar.h 
bar.h:1: foo.h: No such file or directory
# 1 "bar.h"

>Fix:

>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2003-01-23 22:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-01-23 22:06 prj [this message]
2003-01-23 22:28 neil

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=20030123215908.17491.qmail@sources.redhat.com \
    --to=prj@po.cwru.edu \
    --cc=gcc-gnats@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).