RE: The Linux binutils 2.11.90.0.15 is released.

["Ken Whaley" <ken at believe dot com>]

> > I suspect binutils because I noticed that when using the older 
> > binutils 2.10.90, the config.guess part of autoconfigure correctly
> > detected an alphaev6-unknown-linux-gnu (this is true for gcc as well
> > as binutils configure).  With binutils 2.11.90.0.15 installed,
> > config.guess incorrectly detects the system as alpha-unknown-linux-gnu.
> 
> I don't know if it should make a difference. You need to find out
> why config.guess doesn't report alphaev6. There are several changes
> in config.guess.
> 
> 
> H.J.
> 

The point here is that one given config.guess reports 
alphaev6 with binutils 2.10.90 installed and alpha with 2.11.90.0.15
installed.  So, given a particular distribution (both binutils and
gcc 2.95.3), their config.guess will give a different answer based
on which version of binutils is installed.  Using binutils 2.11.90.0.15
gives the wrong answer.  This leads me to believe that the glibc 2.2.3
make check failures could be a binutils problem.  I'm going to bootstrap
with binutils 2.11.0 and then 2.10.90 and see if all the same problems
happen, and report back, but wanted to give a heads up on this in the
meantime.

E.g.,

% cd objdir
% as --version
GNU assembler 2.10.90
% ../binutils-2.11.90.0.15/configure
Configuring for a alphaev6-unknown-linux-gnu host.
...

% rm -rf objdir
% mkdir objdir
% cd objdir
% [switch to new binutils]
% as --version
GNU assembler 2.11.90.0.15
% ../binutils-2.11.90.0.15/configure
Configuring for a alpha-unknown-linux-gnu host.

Ken