public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-03 16:46 Marwijn Hessel
0 siblings, 0 replies; 7+ messages in thread
From: Marwijn Hessel @ 2003-04-03 16:46 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-10 9:37 rearnsha
0 siblings, 0 replies; 7+ messages in thread
From: rearnsha @ 2003-04-10 9:37 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, marwijn.hessel, nobody
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-04 8:36 Christian Ehrhardt
0 siblings, 0 replies; 7+ messages in thread
From: Christian Ehrhardt @ 2003-04-04 8:36 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-04 2:35 ljrittle
0 siblings, 0 replies; 7+ messages in thread
From: ljrittle @ 2003-04-04 2:35 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, marwijn.hessel, nobody
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
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-03 16:16 Christian Ehrhardt
0 siblings, 0 replies; 7+ messages in thread
From: Christian Ehrhardt @ 2003-04-03 16:16 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
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!
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-03 15:56 Marwijn Hessel
0 siblings, 0 replies; 7+ messages in thread
From: Marwijn Hessel @ 2003-04-03 15:56 UTC (permalink / raw)
To: nobody; +Cc: gcc-prs
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.
>
>
>
>
>
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: libstdc++/10217: problem in building libstdc++-v3
@ 2003-04-03 15:37 ehrhardt
0 siblings, 0 replies; 7+ messages in thread
From: ehrhardt @ 2003-04-03 15:37 UTC (permalink / raw)
To: gcc-bugs, gcc-prs, marwijn.hessel, nobody
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
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2003-04-10 9:37 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2003-04-03 16:46 libstdc++/10217: problem in building libstdc++-v3 Marwijn Hessel
-- strict thread matches above, loose matches on Subject: below --
2003-04-10 9:37 rearnsha
2003-04-04 8:36 Christian Ehrhardt
2003-04-04 2:35 ljrittle
2003-04-03 16:16 Christian Ehrhardt
2003-04-03 15:56 Marwijn Hessel
2003-04-03 15:37 ehrhardt
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).