public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Alexandre Oliva <aoliva@redhat.com>
To: ljrittle@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: preprocessor/3243: /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu/bits/gthr.h:98:26: gthr-default.h: No such file or directory
Date: Wed, 20 Jun 2001 13:26:00 -0000 [thread overview]
Message-ID: <20010620202601.9888.qmail@sourceware.cygnus.com> (raw)
The following reply was made to PR libstdc++/3243; it has been noted by GNATS.
From: Alexandre Oliva <aoliva@redhat.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>, libstdc++@gcc.gnu.org
Cc: carlo@alinoe.com, gcc-bugs@gcc.gnu.org, gcc-gnats@gcc.gnu.org
Subject: Re: preprocessor/3243: /usr/local/gcc-3.0/include/g++-v3/i686-pc-linux-gnu/bits/gthr.h:98:26: gthr-default.h: No such file or directory
Date: 20 Jun 2001 17:15:53 -0300
On Jun 19, 2001, Neil Booth <neil@daikokuya.demon.co.uk> wrote:
> aoliva@gcc.gnu.org wrote:-
>> State-Changed-Why:
>> Seems to be a preprocessor bug. #include "file.h" should look for
>> file.h in the directory containing the file being processed first,
>> regardless of the header search path or -I-.
> No, that is not what is implemented, nor is it what is documented.
> So, either the bug lies elsewhere, or we need a good reason to change
> the documented behaviour.
I stand corrected. I didn't know about this detail in the
documentation and implementation of -I-. This means gthr.h must
indeed be fixed to take this possibility into account. Unfortunately,
Carlo's patch isn't enough, since it breaks bootstrap.
--
Alexandre Oliva Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist *Please* write to mailing lists, not to me
next reply other threads:[~2001-06-20 13:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-20 13:26 Alexandre Oliva [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-06-20 8:26 Carlo Wood
2001-06-19 18:16 Zack Weinberg
2001-06-19 13:36 Neil Booth
2001-06-19 6:27 aoliva
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=20010620202601.9888.qmail@sourceware.cygnus.com \
--to=aoliva@redhat.com \
--cc=gcc-prs@gcc.gnu.org \
--cc=ljrittle@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).