From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30075 invoked by alias); 4 Apr 2003 02:35:47 -0000 Mailing-List: contact gcc-prs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-prs-owner@gcc.gnu.org Received: (qmail 30055 invoked by uid 48); 4 Apr 2003 02:35:47 -0000 Date: Fri, 04 Apr 2003 02:35:00 -0000 Message-ID: <20030404023547.30054.qmail@sources.redhat.com> To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marwijn.hessel@ict.nl, nobody@gcc.gnu.org From: ljrittle@gcc.gnu.org Reply-To: ljrittle@gcc.gnu.org, gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marwijn.hessel@ict.nl, nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org Subject: Re: libstdc++/10217: problem in building libstdc++-v3 X-SW-Source: 2003-04/txt/msg00127.txt.bz2 List-Id: Synopsis: problem in building libstdc++-v3 State-Changed-From-To: closed->feedback State-Changed-By: ljrittle State-Changed-When: Fri Apr 4 02:35:47 2003 State-Changed-Why: Reopened. This problem is not caused by bad RAM! If you want me to fix this (and I will if possible): Please look at the build log for the failing bootstrap. Rerun the exact command (with the proper cwd) that failed. It should produce the same error output (this step is just to confirm that you have the failing command). Add the -E switch and rerun the command again. Send me the preprocessed output. Or, the problem will likely be obvious to you at that point. Since you are building a cross, I think I see a possible problem with your configure line: you can't expect to be able to build support libraries for the target that require libc if you don't tell the process where to find target-related headers. Sorry... http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217