public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: A.Simon@kent.ac.uk
To: gcc-gnats@gcc.gnu.org
Subject: preprocessor/10869: -include does not honor include paths
Date: Mon, 19 May 2003 17:16:00 -0000 [thread overview]
Message-ID: <20030519171014.10505.qmail@sources.redhat.com> (raw)
>Number: 10869
>Category: preprocessor
>Synopsis: -include does not honor include paths
>Confidential: no
>Severity: non-critical
>Priority: medium
>Responsible: unassigned
>State: open
>Class: sw-bug
>Submitter-Id: net
>Arrival-Date: Mon May 19 17:16:01 UTC 2003
>Closed-Date:
>Last-Modified:
>Originator: A.Simon@kent.ac.uk
>Release: gcc 3.1 20020420 (prerelease)
>Organization:
>Environment:
MacOS X and others
>Description:
Giving extra include files via -include blah.h does not search the search paths given by -I. This might be intended, but I find it inconvenient.
>How-To-Repeat:
>Fix:
Search the all specified include directories which which were given before -include was specified.
>Release-Note:
>Audit-Trail:
>Unformatted:
next reply other threads:[~2003-05-19 17:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-19 17:16 A.Simon [this message]
2003-05-19 20:18 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=20030519171014.10505.qmail@sources.redhat.com \
--to=a.simon@kent.ac.uk \
--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).