public inbox for gcc-help@gcc.gnu.org
 help / color / mirror / Atom feed
From: Philipp Thomas <pth@suse.de>
To: gcc-help@gcc.gnu.org
Subject: Re: STL problems in GCC 4.1.2
Date: Mon, 25 Feb 2008 14:53:00 -0000	[thread overview]
Message-ID: <20080225135850.GE23120@paradies.suse.de> (raw)
In-Reply-To: <000201c874c5$69ff56a0$500010ac@gx520>

Hi David,

* David Arthur (darthur@tantacomm.com) [20080221 21:08]:

> The GCC I am using is what was included in the SuSE Linux Enterprise Server
> 10 installation on the machine I am compiling with, so I am not sure how it
> was built.

Could you make the preprocessed source of one of the failing sources
available or send it to me? Preprocessed source means that you add
-save-temps to the compiler flags and either make available or send me the
resulting .ii file. Maybe I can help in identifying the culprit.

Philipp

-- 
Software engineer
R&D
SUSE LINUX Products GmbH, Maxfeldstr. 5, D-90409 Nuremberg, GERMANY
 

      parent reply	other threads:[~2008-02-25 13:59 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-12 22:11 David Arthur
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 [this message]

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=20080225135850.GE23120@paradies.suse.de \
    --to=pth@suse.de \
    --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).