public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: bkoz@gcc.gnu.org
Cc: gcc-prs@gcc.gnu.org
Subject: Re: libstdc++/2568
Date: Fri, 25 May 2001 12:46:00 -0000	[thread overview]
Message-ID: <20010525194604.29736.qmail@sourceware.cygnus.com> (raw)

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

From: Rainer Orth <ro@TechFak.Uni-Bielefeld.DE>
To: Brad Lucier <lucier@math.purdue.edu>
Cc: bkoz@gcc.gnu.org, gcc-gnats@gcc.gnu.org, David.Billinghurst@riotinto.com,
        neil@gcc.gnu.org, amacleod@cygnus.com (Andrew Macleod)
Subject: Re: libstdc++/2568
Date: Fri, 25 May 2001 21:42:44 +0200 (MEST)

 Brad Lucier writes:
 
 > > * a sparc-sun-solaris2.8 configuration (sparcv7),
 > 
 > I just did one of these today, and I started a sparcv9-sun-solaris2.8
 > with (I believe) multilib support that should finish in a few
 
 sparc-sun-solaris2.8 is bootstrap and check are finished,
 sparcv9-sun-solaris2.8 bootstrap is done, check is well along, I'm waiting
 for this to finish before I start the -m32 check.
 
 > hours.  (The bootstrap is fairly fast, it's the make check
 > that kills me.)
 
 Bootstrap is generally ok on an 2 x 400 MHz E250, although the bootstrap
 takes considerably longer for sparcv9 (even up to the make compare), It's
 obvious that building all libraries twice takes longer :-)
 
 	Rainer
 
 -----------------------------------------------------------------------------
 Rainer Orth, Faculty of Technology, Bielefeld University
 
 Email: ro@TechFak.Uni-Bielefeld.DE


             reply	other threads:[~2001-05-25 12:46 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-05-25 12:46 Rainer Orth [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-05-25 14:46 libstdc++/2568 Rainer Orth
2001-05-25 14:26 libstdc++/2568 Brad Lucier
2001-05-25 12:46 libstdc++/2568 Brad Lucier
2001-05-25 12:36 libstdc++/2568 Rainer Orth
2001-05-25 12:26 libstdc++/2568 Brad Lucier
2001-05-25 12:06 libstdc++/2568 Rainer Orth
2001-05-09  0:46 libstdc++/2568 Brad Lucier
2001-05-08 23:56 libstdc++/2568 bkoz

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=20010525194604.29736.qmail@sourceware.cygnus.com \
    --to=ro@techfak.uni-bielefeld.de \
    --cc=bkoz@gcc.gnu.org \
    --cc=gcc-prs@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).