From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-help-return-31658-listarch-gcc-help=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25562 invoked by alias); 21 Feb 2008 22:59:45 -0000
Received: (qmail 25511 invoked by uid 22791); 21 Feb 2008 22:59:45 -0000
X-Spam-Check-By: sourceware.org
Received: from fg-out-1718.google.com (HELO fg-out-1718.google.com) (72.14.220.159)     by sourceware.org (qpsmtpd/0.31) with ESMTP; Thu, 21 Feb 2008 22:59:24 +0000
Received: by fg-out-1718.google.com with SMTP id d23so155627fga.28         for <gcc-help@gcc.gnu.org>; Thu, 21 Feb 2008 14:59:21 -0800 (PST)
Received: by 10.86.70.8 with SMTP id s8mr10066204fga.29.1203634721390;         Thu, 21 Feb 2008 14:58:41 -0800 (PST)
Received: by 10.86.35.18 with HTTP; Thu, 21 Feb 2008 14:58:41 -0800 (PST)
Message-ID: <8bc817ee0802211458h1d380454g4fa2ffb89d268d50@mail.gmail.com>
Date: Fri, 22 Feb 2008 09:08:00 -0000
From: "Tom Browder" <tom.browder@gmail.com>
To: "Eljay Love-Jensen" <eljay@adobe.com>
Subject: Re: STL problems in GCC 4.1.2
Cc: "David Arthur" <darthur@tantacomm.com>, GCC-help <gcc-help@gcc.gnu.org>
In-Reply-To: <C3E33851.1C2E%eljay@adobe.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <000201c874c5$69ff56a0$500010ac@gx520> 	 <C3E33851.1C2E%eljay@adobe.com>
X-IsSubscribed: yes
Mailing-List: contact gcc-help-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-help.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-help/>
List-Post: <mailto:gcc-help@gcc.gnu.org>
List-Help: <mailto:gcc-help-help@gcc.gnu.org>
Sender: gcc-help-owner@gcc.gnu.org
X-SW-Source: 2008-02/txt/msg00265.txt.bz2
Message-ID: <20080222090800.YY_9VkDNi8S753MY9cP6JGp5AQmd6jJlTBfDx6uvT0Q@z>

On 2/21/08, Eljay Love-Jensen <eljay@adobe.com> wrote:
> Hi Dave,
>
> > The program you gave was entered verbatim, and it compiles with no errors
> > and runs nicely. :)
>
> That indicates to me that the GCC 4.1.2 Standard C++ Library (including the
> STL) is probably working correctly, and something else is causing things to
> go awry.
>
> One possible culprit is that some header file somewhere (not one of the GCC
> 4.1.2 ones) is introducing a #define identifier that is wreaking havoc on
> later #include directives due to identifier collision.  You may be able to
> use g++ -E to assess where that is occurring, if it is indeed occurring.
> [This is my first, best guess.]
...

And don't forget Scott Meyers's admonitions to NEVER use a using
declaration inside a header or in a source file before any #include's.

-Tom