public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: "David Arthur" <darthur@tantacomm.com>
To: <gcc-help@gcc.gnu.org>
Subject: STL problems in GCC 4.1.2
Date: Tue, 12 Feb 2008 22:11:00 -0000	[thread overview]
Message-ID: <000301c86dc4$35920a00$500010ac@gx520> (raw)

Hello all,

I have searched archives for info regarding this, but didn't find
anything...
I am trying to compile an app under gcc 4.1.2 and I get _loads_ of STL
errors, relating to templates in STL headers that are unhappy. The strange
thing is that all compiles beautifully under gcc 3.3.3! I have found that
some of the errors can be eliminated by simply rearranging the #include
directives for my many header files, or in some cases, by throwing a
#include <list> (or <string>, <vector> etc.) into my include list.
Does anyone know why this is happening?
I use a large number of included header files and this is a rather large
project (which is why I haven't included any code).

Any help anyone can provide would be greatly appreciated!

Thank you,
Dave

             reply	other threads:[~2008-02-12 22:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 22:11 David Arthur [this message]
2008-02-12 22:23 ` Tom Browder
2008-02-12 22:46   ` David Arthur
2008-02-12 23:20     ` James Tebneff
2008-02-14 22:23       ` David Arthur
2008-02-21 18:14       ` David Arthur
     [not found]         ` <C3E329D4.1C1C%eljay@adobe.com>
2008-02-21 19:27           ` David Arthur
2008-02-21 19:43             ` Eljay Love-Jensen
2008-02-21 20:08               ` David Arthur
2008-02-21 20:17                 ` Eljay Love-Jensen
2008-02-21 22:59                   ` Tom Browder
2008-02-21 22:59                   ` Tom Browder
2008-02-22  9:08                     ` Tom Browder
2008-02-25 14:53                 ` Philipp Thomas

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='000301c86dc4$35920a00$500010ac@gx520' \
    --to=darthur@tantacomm.com \
    --cc=gcc-help@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).