From mboxrd@z Thu Jan  1 00:00:00 1970
From: Janis Johnson <janis187@us.ibm.com>
To: "Michael S. Zick" <mszick@goquest.com>
Cc: spyffe@mail.goo.ne.jp, gcc@gcc.gnu.org
Subject: Re: Installation Directions
Date: Fri, 16 Aug 2002 09:18:00 -0000
Message-id: <20020816092013.A1257@us.ibm.com>
References: <20020816041139.81371.qmail@mail.goo.ne.jp> <02081609524301.00732@localhost.localdomain>
X-SW-Source: 2002-08/msg00972.html

On Fri, Aug 16, 2002 at 09:52:43AM -0500, Michael S. Zick wrote:
> On Thursday 15 August 2002 11:11 pm, spyffe@mail.goo.ne.jp wrote:
> > I have with no problems built gcc-3.2 on the Alpha EV56 architecture.
> >
> > Please find detailed information below:
> >
> > < Output of config.guess >--------------------------
> > alphaev56-unknown-linux-gnu
> >
> > < Output of gcc-3.2 -v >----------------------------
> > Reading specs from
> > /usr/local/lib/gcc-lib/alphaev56-unknown-linux-gnu/3.2/specs Configured
> > with: ../gcc-3.2/configure --prefix=/usr/local --program-suffix=-3.2
> > --enable-shared --enable-threads --enable-languages=c,c++,objc Thread
> > model: posix
> > gcc version 3.2
> >
> > < Enabled languages >-------------------------------
> > C, C++, Objective-C
> >
> > < Output of cat /etc/issue >------------------------
> > Red Hat Linux release 7.1 (Seawolf)
> > Kernel 2.4.3-12 on an alpha
> >
> > < Output of uname -a >------------------------------
> > Linux xxx.xxx.xxx 2.4.3-12 #1 Fri Aug 15 00:06:52 xxxT 2002 alpha unknown
> >
> > (I erased all personal information)
> >
> > < Output of rpm -q glibc >--------------------------
> > gcc-2.2.3-11
> >
> > < Host compiler >-----------------------------------
> > gcc version 2.96 20000731 (Red Hat Linux 7.1 2.96-87)
> >
> > < Compilation method >------------------------------
> > tar xzvf gcc-3.2.tar.gz
> > mkdir build-gcc
> > cd build-gcc
> > ../gcc-3.2/configure (options same as above)
> > make bootstrap
> > su
> > make install
> >
> > Thank you to the GCC 3.2 developers!
> 
> Folks,
> As mentioned in an earlier mail, I am working on a revision of the "install" 
> directions.
> I really like the format of this "build report" - anyone have comments or 
> objections to making it the "recommended" format?
> Mike

As someone who reads all of the build reports carefully, I like this
one.  In your recommended format you should, however, include
"make -k check" after "make bootstrap", with a link to the archived
test results.  You can mention that running the tests is optional but
is a very good idea.  Sending in the test results allows other people
to notice problems with your build, and it provides a comparison for
other people building on the same platform.

Building GCC the first time can be difficult, but we get used to it
very quickly and forget that it can be confusing.  Thanks for making
the effort to improve the documentation for first-timers.

Janis