This is the mail archive of the
gcc-prs@gcc.gnu.org
mailing list for the GCC project.
Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0
- From: Mario Deilmann <Mario dot Deilmann at pallas dot com>
- To: nobody at gcc dot gnu dot org
- Cc: gcc-prs at gcc dot gnu dot org,
- Date: 21 Mar 2002 09:36:02 -0000
- Subject: Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0
- Reply-to: Mario Deilmann <Mario dot Deilmann at pallas dot com>
The following reply was made to PR c++/6001; it has been noted by GNATS.
From: Mario Deilmann <Mario.Deilmann@pallas.com>
To: Neil Booth <neil@daikokuya.demon.co.uk>
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0
Date: Thu, 21 Mar 2002 10:28:39 +0100 (MET)
Dear Neil,
again thanks for your help. The hint was very helpful to get the right
output but I cannot see why I got an error like
/home/mdeil/bin/../include/g++-v3/sparc-sun-solaris2.7/bits/basic_file_model.h:39:
parse error before `;' token
only because I changed the sequence of some includes. The code with the
nested headers looks syntactically correct for me. The only thing I would
expect from a different include sequence are problems with definitions not
a parse error.
Anyhow I also didn't want to investigate more on this because I have no
clue what I should look for and because I have a workaround if I ommit
nested headers. So if this is enough to close the bugreport please do so.
Viele Gruesse / Best Regards
-- Mario
Mario Deilmann
Senior Sales Engineer
--------------------------------------------------------------------
//// pallas
Pallas GmbH / Hermuelheimer Str. 10 / 50321 Bruehl / Germany
Mario.Deilmann@pallas.com / www.pallas.com
Tel +49-2232-1896-31 / Fax +49-2232-1896-29
--------------------------------------------------------------------
On Wed, 20 Mar 2002, Neil Booth wrote:
> Mario Deilmann wrote:-
>
> > I tried gcc -E -H on both files and there are a LOT of differences (about
> > 1200). I have looked into the differences and most of them obviously are
> > caused by the different include sequence.
> >
> > I have no idea where I should look for the important differences ? Any
> > idea ?
>
> Try
>
> gcc <options> file.c -E -H > /dev/null
>
> which just lists the header trail. Then have a look at the first header
> where they diverge, and figure out why. It's either because your path
> is different, or a command line or builtin macro is different. I can't
> help you any more than that I'm afraid.
>
> Neil.
>