build success: alphaev67-unknown-linux-gnu

[Edward Welbourne <eddy at zeus dot com>]

I've built gcc-2-95.2 in conjunction with binutils-2.10 using GNU 
make-3.79.1 on a platform which gcc's config.guess describes as:
  alpha-unknown-linux-gnu
but glibc's configure described it as 
  alphaev67-unknown-linux-gnu
I don't know whether this means it's new to gcc ...

On the way, I noticed an irritant in the install instructions:
http://gcc.gnu.org/install/build.html
tells me, when Building a native compiler, make bootstrap, that
this will (2nd step):
> Build target tools for use by the compiler such as binutils
> (bfd, binutils, gas, gprof, ld, and opcodes) if they have been 
> individually linked or moved into the top level GCC source tree
> before configuring.

Unfortunately, the download and configure pages don't mention that
one may wish to do this, or how to; and the above is not the clearest
statement of *how* to do so (I seem to have interpreted it right:
in the top level gcc dir, I did
 ln -s ../binutils-2.10/{bfd,binutils,gas,gprof,ld,opcodes} .
which worked fine - but depended on my ability to guess that this
was where the relevant directories needed to go, and that the gcc
distribution wouldn't need any other fragments from the binutils
one to make use of them).

Albeit the main page recommends reading to the end before starting
to do the job, it would be nicer to have been told about this before
configure; and, in any case, I would recommend introducing the
binutils during unpacking (download): then the build phase can simply
say `Build target tools, if any have been added (see <A>download</A>).'
The download page can afford to devote a paragraph to explaining what
the binutils are, why one might wish to involve them and that the gcc
build process will handle them if needed.

	Eddy.
-- 
Due to circumstances beyond your control, you are master of your fate
and captain of your soul.