public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Neil Booth <neil@daikokuya.demon.co.uk>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: c++/6001: g++ problems with nested headers from > egcs-2.91.66 until 3.0.0
Date: Wed, 20 Mar 2002 10:16:00 -0000	[thread overview]
Message-ID: <20020320181607.26879.qmail@sources.redhat.com> (raw)

The following reply was made to PR c++/6001; it has been noted by GNATS.

From: Neil Booth <neil@daikokuya.demon.co.uk>
To: Mario Deilmann <Mario.Deilmann@pallas.com>
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: Wed, 20 Mar 2002 18:13:01 +0000

 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.


             reply	other threads:[~2002-03-20 18:16 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-20 10:16 Neil Booth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-03-26  2:16 Mario Deilmann
2002-03-25 10:36 Neil Booth
2002-03-22 11:36 Neil Booth
2002-03-22  1:56 Mario Deilmann
2002-03-21 10:36 Neil Booth
2002-03-21 10:32 neil
2002-03-21  1:36 Mario Deilmann
2002-03-20  1:46 Mario Deilmann
2002-03-19 11:56 Neil Booth
2002-03-19  7:16 mdeil

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=20020320181607.26879.qmail@sources.redhat.com \
    --to=neil@daikokuya.demon.co.uk \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=nobody@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).