From: Janis Johnson <janis187@us.ibm.com>
To: Kathy Gerber <kath@skatha.net>
Cc: gcc@gcc.gnu.org
Subject: Re: Compile Results
Date: Mon, 29 Apr 2002 10:01:00 -0000 [thread overview]
Message-ID: <20020429095957.C1573@us.ibm.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0204280007370.2156-100000@skatha.net>; from kath@skatha.net on Sun, Apr 28, 2002 at 12:15:47AM -0400
On Sun, Apr 28, 2002 at 12:15:47AM -0400, Kathy Gerber wrote:
> -- Output of config.guess: i686-pc-linux-gnu
>
> -- Output of gcc -v :
>
> Reading specs from ./../lib/gcc-lib/i686-pc-linux-gnu/3.0.4/specs
> Configured with: ../gcc-3.0.4/configure --prefix=/opt
> -program-suffix=-3.0.4
> Thread model: single
> gcc version 3.0.4
>
> -- GNU/Linux info:
> /etc/issue output:
> Red Hat Linux release 7.2.92 (Skipjack)
>
> uname -a output:
> Linux skatha.net 2.4.18-0.4 #1 Wed Mar 13 10:36:06 EST 2002 i686 unknown
>
> rpm -q glibc output:
> glibc-2.2.5-27
>
>
Thanks! I've added this to the GCC 3.0 build status list at
http://gcc.gnu.org/gcc-3.0/buildstat.html.
Janis
prev parent reply other threads:[~2002-04-29 16:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 23:17 Kathy Gerber
2002-04-29 10:01 ` Janis Johnson [this message]
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=20020429095957.C1573@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=gcc@gcc.gnu.org \
--cc=kath@skatha.net \
/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).