From: Michael S. Zick <mszick@goquest.com>
To: spyffe@mail.goo.ne.jp, gcc@gcc.gnu.org
Subject: Installation Directions
Date: Fri, 16 Aug 2002 07:52:00 -0000 [thread overview]
Message-ID: <02081609524301.00732@localhost.localdomain> (raw)
In-Reply-To: <20020816041139.81371.qmail@mail.goo.ne.jp>
On Thursday 15 August 2002 11:11 pm, spyffe@mail.goo.ne.jp wrote:
^[(B> I have with no problems built gcc-3.2 on the Alpha EV56 architecture.
^[(B>
^[(B> Please find detailed information below:
^[(B>
^[(B> < Output of config.guess >--------------------------
^[(B> alphaev56-unknown-linux-gnu
^[(B>
^[(B> < Output of gcc-3.2 -v >----------------------------
^[(B> Reading specs from
^[(B> /usr/local/lib/gcc-lib/alphaev56-unknown-linux-gnu/3.2/specs Configured
^[(B> with: ../gcc-3.2/configure --prefix=/usr/local --program-suffix=-3.2
^[(B> --enable-shared --enable-threads --enable-languages=c,c++,objc Thread
^[(B> model: posix
^[(B> gcc version 3.2
^[(B>
^[(B> < Enabled languages >-------------------------------
^[(B> C, C++, Objective-C
^[(B>
^[(B> < Output of cat /etc/issue >------------------------
^[(B> Red Hat Linux release 7.1 (Seawolf)
^[(B> Kernel 2.4.3-12 on an alpha
^[(B>
^[(B> < Output of uname -a >------------------------------
^[(B> Linux xxx.xxx.xxx 2.4.3-12 #1 Fri Aug 15 00:06:52 xxxT 2002 alpha unknown
^[(B>
^[(B> (I erased all personal information)
^[(B>
^[(B> < Output of rpm -q glibc >--------------------------
^[(B> gcc-2.2.3-11
^[(B>
^[(B> < Host compiler >-----------------------------------
^[(B> gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-87)
^[(B>
^[(B> < Compilation method >------------------------------
^[(B> tar xzvf gcc-3.2.tar.gz
^[(B> mkdir build-gcc
^[(B> cd build-gcc
^[(B> ../gcc-3.2/configure (options same as above)
^[(B> make bootstrap
^[(B> su
^[(B> make install
^[(B>
^[(B> Thank you to the GCC 3.2 developers!
^[(B
^[(BFolks,
^[(BAs mentioned in an earlier mail, I am working on a revision of the "install"
^[(Bdirections.
^[(BI really like the format of this "build report" - anyone have comments or
^[(Bobjections to making it the "recommended" format?
^[(BMike
next prev parent reply other threads:[~2002-08-16 7:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-15 21:11 SUCCESS alpha-ev56 gcc-3.2 spyffe
2002-08-16 7:52 ` Michael S. Zick [this message]
2002-08-16 9:18 ` Installation Directions Janis Johnson
2002-08-17 7:52 ` Warren W. Gay VE3WWG
2002-08-17 11:17 ` Michael S. Zick
2002-08-16 10:37 ` SUCCESS alpha-ev56 gcc-3.2 Janis Johnson
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=02081609524301.00732@localhost.localdomain \
--to=mszick@goquest.com \
--cc=gcc@gcc.gnu.org \
--cc=spyffe@mail.goo.ne.jp \
/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).