From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 9425 invoked by alias); 3 Apr 2003 16:46:01 -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 9411 invoked by uid 71); 3 Apr 2003 16:46:00 -0000 Date: Thu, 03 Apr 2003 16:46:00 -0000 Message-ID: <20030403164600.9410.qmail@sources.redhat.com> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, From: "Marwijn Hessel" Subject: Re: libstdc++/10217: problem in building libstdc++-v3 Reply-To: "Marwijn Hessel" X-SW-Source: 2003-04/txt/msg00106.txt.bz2 List-Id: The following reply was made to PR libstdc++/10217; it has been noted by GNATS. From: "Marwijn Hessel" To: "Christian Ehrhardt" Cc: , , , , Subject: Re: libstdc++/10217: problem in building libstdc++-v3 Date: Thu, 3 Apr 2003 18:43:45 +0200 I have seen these URL's but they do not describe any solution for this problem (or I'm stupid ...). http://gcc.gnu.org/bugs.html#dontwant http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217 The possibility that my ram is bad is nonsense because this problem course on all machines that I tried (three different machines). I'm trying to build a cross compiler (to powerpc-eabi) on a cygwin platform. According to http://gcc.gnu.org/ this should be no problem. But the manual does not say anything about it. The only thing that I could find is http://www.parisc-linux.org/toolchain/PA-Linux-XC-HOWTO-04.html, and these steps fail as described in the problem report. How on earth do I build a cross compiler to powerpc-eabi on a Cygwin platform ??? ----- Original Message ----- From: "Christian Ehrhardt" To: "Marwijn Hessel" Cc: ; ; ; ; Sent: Thursday, April 03, 2003 6:11 PM Subject: Re: libstdc++/10217: problem in building libstdc++-v3 > On Thu, Apr 03, 2003 at 05:47:11PM +0200, Marwijn Hessel wrote: > > Nice that is not a wanted bug ... > > But what is the solution ???? > > See the URL from my previous mail. You have a hardware problem, > most likely bad ram. > > regards Christian