From: Janis Johnson <janis187@us.ibm.com>
To: Eli Kane <elikane@qwest.net>
Cc: gcc@gcc.gnu.org
Subject: Re: successful build info
Date: Mon, 21 Oct 2002 12:02:00 -0000 [thread overview]
Message-ID: <20021021090830.A1447@us.ibm.com> (raw)
In-Reply-To: <02101900495901.01366@mars.nodomain.nowhere>; from elikane@qwest.net on Sat, Oct 19, 2002 at 12:42:22AM -0600
On Sat, Oct 19, 2002 at 12:42:22AM -0600, Eli Kane wrote:
> Greetings,
>
> Here are the particulars for a successful build not listed on the buildstat
> sheet for gcc 3.2:
>
> [eli@mars gcc]# ../gcc-3.2/config.guess
> i686-pc-linux-gnu
> [eli@mars gcc]# gcc -v
> Reading specs from /usr/local/lib/gcc-lib/i686-pc-linux-gnu/3.2/specs
> Configured with: ../gcc-3.2/configure -with-cpp-install-dir=/usr/bin -enable-languages=c,c++,f77,java,objc
> Thread model: posix
> gcc version 3.2
> [eli@mars gcc]# uname -a
> Linux mars.mynetwork.myhouse 2.2.14 #1 SMP Thu Feb 17 11:49:42 MST 2000 i686
> unknown
> [eli@mars gcc]# rpm -q glibc
> glibc-2.1.2-3
>
> Caldera OpenLinux eDesktop 2.4
Thanks! Your message is linked from the GCC 3.2 build status list at
http://gcc.gnu.org/gcc-3.2/buildstat.html.
Janis
prev parent reply other threads:[~2002-10-21 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-19 5:44 Eli Kane
2002-10-21 12:02 ` 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=20021021090830.A1447@us.ibm.com \
--to=janis187@us.ibm.com \
--cc=elikane@qwest.net \
--cc=gcc@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).