public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: "Marwijn Hessel" <mwhessel@xs4all.nl>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: libstdc++/10217: problem in building libstdc++-v3
Date: Thu, 03 Apr 2003 16:46:00 -0000 [thread overview]
Message-ID: <20030403164600.9410.qmail@sources.redhat.com> (raw)
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
next reply other threads:[~2003-04-03 16:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-03 16:46 Marwijn Hessel [this message]
-- 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
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=20030403164600.9410.qmail@sources.redhat.com \
--to=mwhessel@xs4all.nl \
--cc=gcc-prs@gcc.gnu.org \
--cc=nobody@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).