From: Alexander Manakov <mnk@mma.ru>
To: gcc@gcc.gnu.org
Subject: GCC v3.2.1 build report
Date: Tue, 24 Dec 2002 09:12:00 -0000 [thread overview]
Message-ID: <200212240839.gBO8diFZ023093@mma.ru> (raw)
GCC was successfully built on my system. W/o any problem.
Output from config.guess:
i686-pc-linux-gnu
System:
i686-pc-linux-gnu (Athlon)
Output from gcc -v:
Reading specs from ./../lib/gcc-lib/i686-pc-linux-gnu/3.2.1/specs
Configured with: /gcc/gcc-3.2.1/configure --prefix=/gcc/objdir
i686-pc-linux-gnu
Thread model: posix
gcc version 3.2.1
GCC version:
3.2.1 (full dustribution)
OS distribution name and version:
ALT Linux Master 2.0 (http://www.altlinux.org)
Output from uname --version:
uname (GNU sh-utils) 2.0.11
Output from uname -a:
Linux mnk 2.4.18-alt6master-up #1 Tue Apr 16 14:50:56 MSD 2002 i686 unknown
Kernel version:
2.4.18
Output from rpm -q glibc:
glibc-2.2.5-alt4
Thanks for new version!
reply other threads:[~2002-12-24 8:40 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=200212240839.gBO8diFZ023093@mma.ru \
--to=mnk@mma.ru \
--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).