From: Scott Robert Ladd <coyote@coyotegulch.com>
To: gcc mailing list <gcc@gcc.gnu.org>
Subject: Successful Build, GCC 3.3, Debian unstable, beta Linux kernel
Date: Thu, 15 May 2003 13:54:00 -0000 [thread overview]
Message-ID: <3EC39BDE.9070808@coyotegulch.com> (raw)
I have just successfully built, installed, and tested GCC 3.3 against my
personal code base on a 2.8 GHz, running a beta Linux kernel and Debian
GNU/Linux 'sid' unstable (glibc 2.3.1-17).
Build accomplished with make -j 2 bootstrap.
scott@Tycho:~$ uname -a
Linux Tycho 2.5.66 #2 SMP Thu May 1 10:56:56 EDT 2003 i686 unknown
unknown GNU/Linux
scott@Tycho:~$ /usr/src/gcc-3.3/config.guess
i686-pc-linux-gnu
scott@Tycho:~$ gcc -v
Reading specs from opt/gcc/bin/../lib/gcc-lib/i686-pc-linux-gnu/3.3/specs
Configured with: ../gcc-3.3/configure -prefix=/opt/gcc-3.3
--enable-shared --enable-threads=posix --enable-__cxa_atexit
--enable-java-gc=boehm --with-system-zlib
Thread model: posix
gcc version 3.3
--
Scott Robert Ladd
Coyote Gulch Productions (http://www.coyotegulch.com)
Professional programming for science and engineering;
Interesting and unusual bits of very free code.
reply other threads:[~2003-05-15 13:54 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3EC39BDE.9070808@coyotegulch.com \
--to=coyote@coyotegulch.com \
--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).