public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Phil Edwards <phil@jaj.com>
To: nobody@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org,
Subject: Re: bootstrap/8890: libstdc++ can't be configured
Date: Tue, 10 Dec 2002 12:26:00 -0000	[thread overview]
Message-ID: <20021210202602.2561.qmail@sources.redhat.com> (raw)

The following reply was made to PR bootstrap/8890; it has been noted by GNATS.

From: Phil Edwards <phil@jaj.com>
To: dms@wplus.net
Cc: gcc-gnats@gcc.gnu.org
Subject: Re: bootstrap/8890: libstdc++ can't be configured
Date: Tue, 10 Dec 2002 15:25:48 -0500

 On Tue, Dec 10, 2002 at 01:51:00PM -0000, dms@wplus.net wrote:
 > root@keyplat:~/gcc-3.2.1#gcc -v
 > Reading specs from /usr/local/lib/gcc-lib/sparc-sun-solaris2.8/3.0.4/specs
 > Configured with: ./configure --with-ld=/usr/local/bin/ld --with-as=/usr/local/bin/as
 > Thread model: posix
 > gcc version 3.0.4
 > 
 > >Description:
 > testsuite_flags.in              ..linked
 > configure: error: can not find sources in .
 > make[1]: *** [configure-target-libstdc++-v3] Error 1
 > make[1]: Leaving directory `/usr/home/dms/gcc-3.2.1'
 > make: *** [bootstrap] Error 2
 > >How-To-Repeat:
 > unpack gcc-3.2.1
 > cd gcc-3.2.1
 > ./configure --with-ld=/usr/local/bin/ld --with-as=/usr/local/bin/as
 > make bootstrap
 
 Try building in a separate directory, as strongly recommended in the
 installation instructions, and let us know whether that fixes it.
 
 
 -- 
 I would therefore like to posit that computing's central challenge, viz. "How
 not to make a mess of it," has /not/ been met.
                                                  - Edsger Dijkstra, 1930-2002


             reply	other threads:[~2002-12-10 20:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-10 12:26 Phil Edwards [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-01-11 22:24 neroden
2002-12-10  5:56 dms

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=20021210202602.2561.qmail@sources.redhat.com \
    --to=phil@jaj.com \
    --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).