From: "H. J. Lu" <hjl@lucon.org>
To: Jan Hubicka <jh@suse.cz>
Cc: Andreas Tobler <toa@pop.agri.ch>,
hubicka@ucw.cz, "Kaveh R. Ghazi" <ghazi@caip.rutgers.edu>,
gcc@gcc.gnu.org
Subject: Re: Gcc mainline failed to bootstrap on Linux/ia64
Date: Mon, 08 Sep 2003 23:37:00 -0000 [thread overview]
Message-ID: <20030908222103.GB30268@lucon.org> (raw)
In-Reply-To: <20030907201916.GL14387@kam.mff.cuni.cz>
On Sun, Sep 07, 2003 at 10:19:16PM +0200, Jan Hubicka wrote:
> > Andreas Tobler wrote:
> >
> > >>Hm, ok, ppclinux build in progress. Sol 2.9 syncing. Let you know asap.
> > >
> > >
> > >For the record, solaris in stage 3 now. Was hanging before in stage 2.
> > >
> > >Further info coming.
> >
> > Here it is:
> >
> > ppc linux now in stage of building the libs (libgcj at the moment).
> > Solaris 2.9 died in libstdc++ with the filed (12126) bug.
> > Darwin building, but I had a hanger in libgcj.
>
> Excellent.
FYI, Sun Sep 7 19:28:11 UTC 2003 mainline is still broken on ia64.
H.J.
next prev parent reply other threads:[~2003-09-08 22:21 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-06 23:30 H. J. Lu
2003-09-06 23:39 ` Jan Hubicka
2003-09-07 10:38 ` H. J. Lu
2003-09-07 13:52 ` Jan Hubicka
2003-09-07 15:44 ` H. J. Lu
2003-09-07 15:54 ` Andreas Tobler
2003-09-07 16:35 ` Jan Hubicka
2003-09-07 16:39 ` Gabriel Dos Reis
2003-09-07 16:57 ` Kaveh R. Ghazi
2003-09-07 17:12 ` Andreas Tobler
2003-09-07 18:49 ` Andreas Tobler
2003-09-07 20:21 ` Andreas Tobler
2003-09-07 20:22 ` Jan Hubicka
2003-09-08 23:37 ` H. J. Lu [this message]
2003-09-09 0:05 ` Jan Hubicka
2003-09-08 23:35 ` H. J. Lu
2003-09-08 14:09 ` Andreas Schwab
2003-09-09 0:20 ` Jan Hubicka
2003-09-09 6:28 ` H. J. Lu
2003-09-09 10:36 ` Eric Christopher
2003-09-09 13:44 ` Jan Hubicka
2003-09-09 13:41 ` Jan Hubicka
2003-09-09 16:40 ` David Edelsohn
2003-09-09 16:43 ` 20011119-1.c failure (Re: Gcc mainline failed to bootstrap on Linux/ia64) Jan Hubicka
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=20030908222103.GB30268@lucon.org \
--to=hjl@lucon.org \
--cc=gcc@gcc.gnu.org \
--cc=ghazi@caip.rutgers.edu \
--cc=hubicka@ucw.cz \
--cc=jh@suse.cz \
--cc=toa@pop.agri.ch \
/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).