Re: libstdc++/10217: problem in building libstdc++-v3

Re: libstdc++/10217: problem in building libstdc++-v3

[ehrhardt]

Synopsis: problem in building libstdc++-v3

State-Changed-From-To: open->closed
State-Changed-By: cae
State-Changed-When: Thu Apr  3 15:37:15 2003
State-Changed-Why:
    Indeed. This is even covered by the "Bugs we don't want" section
    at http://gcc.gnu.org/bugs.html#dontwant hence I'm closing this.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217

Re: libstdc++/10217: problem in building libstdc++-v3

[rearnsha]

Synopsis: problem in building libstdc++-v3

State-Changed-From-To: feedback->closed
State-Changed-By: rearnsha
State-Changed-When: Thu Apr 10 09:37:30 2003
State-Changed-Why:
    This is the same problem as PR 10354. The correct way to build a cross-gcc compiler is to configure the compiler with the option
      --with-headers=<path-to-libc-sources>/include
    instead of 
      --without-headers
    
    You can't build the C++ compiler libraries without knowing where these are.

http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217

Re: libstdc++/10217: problem in building libstdc++-v3

[Christian Ehrhardt]

The following reply was made to PR libstdc++/10217; it has been noted by GNATS.

From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: Marwijn Hessel <mwhessel@xs4all.nl>
Cc: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marwijn.hessel@ict.nl,
  nobody@gcc.gnu.org, gcc-gnats@gcc.gnu.org, ljrittle@gcc.gnu.org
Subject: Re: libstdc++/10217: problem in building libstdc++-v3
Date: Fri, 4 Apr 2003 10:29:04 +0200

 On Thu, Apr 03, 2003 at 06:43:45PM +0200, Marwijn Hessel wrote:
 > I have seen these URL's but they do not describe any solution for this
 > problem (or I'm stupid ...).
 
 AAAARG! Sorry! This is my fault. Please accept my appologies.
 I wanted to close PR 10227 but instead closed 10217. Your PR has
 been reopen already. Sorry for the confusion.
 
    regards   Christian
 

Re: libstdc++/10217: problem in building libstdc++-v3

[ljrittle]

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

Re: libstdc++/10217: problem in building libstdc++-v3

[Marwijn Hessel]

The following reply was made to PR libstdc++/10217; it has been noted by GNATS.

From: "Marwijn Hessel" <mwhessel@xs4all.nl>
To: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
Cc: <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
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" <ehrhardt@mathematik.uni-ulm.de>
 To: "Marwijn Hessel" <mwhessel@xs4all.nl>
 Cc: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <marwijn.hessel@ict.nl>;
 <nobody@gcc.gnu.org>; <gcc-gnats@gcc.gnu.org>
 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
 
 

Re: libstdc++/10217: problem in building libstdc++-v3

[Christian Ehrhardt]

The following reply was made to PR libstdc++/10217; it has been noted by GNATS.

From: "Christian Ehrhardt" <ehrhardt@mathematik.uni-ulm.de>
To: Marwijn Hessel <mwhessel@xs4all.nl>
Cc: 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
Date: Thu, 3 Apr 2003 18:11:10 +0200

 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
 
 -- 
 THAT'S ALL FOLKS!

Re: libstdc++/10217: problem in building libstdc++-v3

[Marwijn Hessel]

The following reply was made to PR libstdc++/10217; it has been noted by GNATS.

From: "Marwijn Hessel" <mwhessel@xs4all.nl>
To: <ehrhardt@mathematik.uni-ulm.de>, <gcc-bugs@gcc.gnu.org>,
   <gcc-prs@gcc.gnu.org>, <marwijn.hessel@ict.nl>, <nobody@gcc.gnu.org>,
   <gcc-gnats@gcc.gnu.org>
Cc:  
Subject: Re: libstdc++/10217: problem in building libstdc++-v3
Date: Thu, 3 Apr 2003 17:47:11 +0200

 Hi,
 
 Nice that is not a wanted bug ...
 But what is the solution ????
 
 Regards,
 Marwijn
 
 
 ----- Original Message ----- 
 From: <ehrhardt@mathematik.uni-ulm.de>
 To: <gcc-bugs@gcc.gnu.org>; <gcc-prs@gcc.gnu.org>; <marwijn.hessel@ict.nl>;
 <nobody@gcc.gnu.org>
 Sent: Thursday, April 03, 2003 5:37 PM
 Subject: Re: libstdc++/10217: problem in building libstdc++-v3
 
 
 >
 > Synopsis: problem in building libstdc++-v3
 >
 > State-Changed-From-To: open->closed
 > State-Changed-By: cae
 > State-Changed-When: Thu Apr  3 15:37:15 2003
 > State-Changed-Why:
 >     Indeed. This is even covered by the "Bugs we don't want" section
 >     at http://gcc.gnu.org/bugs.html#dontwant hence I'm closing this.
 >
 >
 http://gcc.gnu.org/cgi-bin/gnatsweb.pl?cmd=view%20audit-trail&database=gcc&pr=10217
 >
 > ----------------
 > This E-mail message, including any attached documentation, is
 > confidential. Should you have received this message wrongly, you are
 > urged to inform the sender at "disclaimer@ICT.nl" and remove the message
 > from your system. Any unauthorised dissemination of the information, in
 > whole or in part, is prohibited. E-mail messages can be subject to
 > change. ICT Automatisering NV and its subsidiaries cannot be held
 > responsible for incorrect, incomplete and/or delayed transfer of
 > messages and possible damage caused by this. Although ICT Automatisering
 > NV (including its subsidiaries) makes every effort to send messages free
 > of viruses by using a viruschecker, ICT Automatisering NV (or its
 > subsidiaries) cannot guarantee that the message and any attachments are
 > actually completely virus free.
 >
 >
 >
 >
 >