This is the mail archive of the
mailing list for the GCC project.
Re: PATCH: Fix libcpp configury/portability issue
- From: Zack Weinberg <zack at codesourcery dot com>
- To: Gerald Pfeifer <gerald at pfeifer dot com>
- Cc: gcc-patches at gcc dot gnu dot org
- Date: Fri, 05 Nov 2004 07:40:16 -0800
- Subject: Re: PATCH: Fix libcpp configury/portability issue
- References: <Pine.BSF.firstname.lastname@example.org><email@example.com><Pine.BSF.firstname.lastname@example.org><email@example.com><Pine.BSF.firstname.lastname@example.org><email@example.com><Pine.BSF.firstname.lastname@example.org><email@example.com><Pine.BSF.firstname.lastname@example.org><Pine.BSF.email@example.com>
Gerald Pfeifer <firstname.lastname@example.org> writes:
> On Thu, 4 Nov 2004, Gerald Pfeifer wrote:
>>> There are no inclusions of libcpp/internal.h anywhere in gcc/java (nor
>>> should there be - any use of that header outside of cpplib is a bug).
>>> And my patch has exactly the same effect as yours, it's just more
>>> readable. Thus I am inclined to think that this must be an unrelated
>> After some debugging, I believe you are right.
> ...and I believe the very same patch you suggested for libcpp helps
> in that case as well.
> Bootstrapped on i386-unknown-freebsd4.10 and i686-pc-linux-gnu.
> What do you think?
Looks sensible to me.