From: Janis Johnson <janis187@us.ibm.com>
To: Jack Cummings <jack@ice.mudshark.org>
Cc: Janis Johnson <janis187@us.ibm.com>, gcc@gcc.gnu.org
Subject: Re: Successful build
Date: Mon, 24 Sep 2001 11:45:00 -0000 [thread overview]
Message-ID: <20010924114732.A2185@us.ibm.com> (raw)
In-Reply-To: <20010924113205.J2786@ice.mudshark.org>
On Mon, Sep 24, 2001 at 11:32:05AM -0700, Jack Cummings wrote:
> On Mon, Sep 24, 2001 at 11:29:21AM -0700, Janis Johnson wrote:
>
> > > gcc 3.0.1 successfully built on
>
> > > i686-pc-linux-gnu Successful (Mandrake 8.0, glibc 2.2.4)
>
> > Thanks! This is now included in the GCC 3.0 build status list at
> > http://gcc.gnu.org/gcc-3.0/buildstat.html .
>
> Another couple, although building them isn't as straightforward..
>
> sparcv9-sun-solaris2.7 ( 64 bit )
> hppa64-hp-hpux11.00 ( 64 bit )
If these aren't straightforward then I'd rather not include them in the
build status list unless there is good documentation about all specific
problems for them in the section of install.texi about "Host/target
specific installation notes for GCC".
Do these work for 3.0.1? I though that 64-bit sparc support wouldn't
be available until 3.1.
Janis
next prev parent reply other threads:[~2001-09-24 11:45 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-23 10:02 John Warriner
2001-09-24 11:26 ` Janis Johnson
2001-09-24 11:32 ` Jack Cummings
2001-09-24 11:45 ` Janis Johnson [this message]
2001-09-24 11:55 ` Jack Cummings
2001-09-24 16:47 ` Janis Johnson
2001-09-24 16:51 ` Jack Cummings
2001-09-25 10:17 ` Janis Johnson
-- strict thread matches above, loose matches on Subject: below --
2010-06-08 15:27 Maynard, William L. (GSFC-5540)
2008-03-15 4:10 successful build Christian Schüler
2007-12-24 7:53 Successful Build Aran Clauson
2006-02-03 10:12 Dinosaur
2006-01-31 22:43 Dinosaur
2003-07-01 15:06 Successful build Dan Schult
2003-07-01 15:12 ` Andrew Pinski
2003-03-11 20:15 Willard Myers
2003-02-13 21:38 'David Scott Urban
2002-11-26 6:33 successful build Alexander Darovsky
2002-09-03 15:27 Successful build Miguel Bazdresch
2002-09-03 16:08 ` Janis Johnson
2002-08-26 6:35 successful build John Griessen
2002-08-26 16:36 ` Janis Johnson
2002-05-16 12:22 Daniel Wesslén
2002-05-16 12:15 Marek Tilk Materzok
2002-05-16 13:16 ` Florian Weimer
2002-05-16 17:35 ` Janis Johnson
2002-04-09 1:55 Successful Build Bob
2002-03-14 14:20 Don Allen
2002-03-14 16:36 ` Janis Johnson
2002-01-20 11:37 successful build Kevin Franden
2002-01-21 9:37 ` Janis Johnson
2001-12-16 17:52 Juan Jose Martin
2001-12-17 9:15 ` Janis Johnson
2001-12-07 16:00 Successful Build platter
2001-12-11 16:20 ` Janis Johnson
2001-10-30 7:56 Successful build Marc Soda
2001-10-30 8:48 ` Janis Johnson
2001-10-03 17:07 successful build Matt Kraai
2001-10-04 10:44 ` Janis Johnson
2001-09-14 3:23 Successful build Bert De Knuydt
2001-09-14 9:41 ` Janis Johnson
2001-08-01 6:15 successful build Amy
1999-08-02 5:49 David J. Dooling
1999-08-31 23:20 ` David J. Dooling
1999-07-31 12:41 David J. Dooling
1999-07-31 23:33 ` David J. Dooling
1999-05-06 13:22 Successful Build David A. Deal
1999-05-31 21:36 ` David A. Deal
1998-11-21 7:09 Successful build aaron schmiedel 214.924.8225
1998-09-06 15:12 successful build David Long
1998-08-25 19:31 Successful build furio ercolessi
1998-06-19 23:47 J Scott Berg
1998-06-16 5:45 Christopher Minekime
1998-02-06 6:19 Michael Remski
1997-12-05 6:20 Lars Hecking
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=20010924114732.A2185@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=jack@ice.mudshark.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).