public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: ljrittle@gcc.gnu.org
To: gcc-bugs@gcc.gnu.org, gcc-prs@gcc.gnu.org, marwijn.hessel@ict.nl,
	nobody@gcc.gnu.org
Subject: Re: libstdc++/10217: problem in building libstdc++-v3
Date: Fri, 04 Apr 2003 02:35:00 -0000	[thread overview]
Message-ID: <20030404023547.30054.qmail@sources.redhat.com> (raw)

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


             reply	other threads:[~2003-04-04  2:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-04  2:35 ljrittle [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-03 16:46 Marwijn Hessel
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=20030404023547.30054.qmail@sources.redhat.com \
    --to=ljrittle@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    --cc=gcc-gnats@gcc.gnu.org \
    --cc=gcc-prs@gcc.gnu.org \
    --cc=marwijn.hessel@ict.nl \
    --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).