Install of binutils is different that what is expected

[James Damon]

The problems I have experienced have nothing to do with the software,
but instead are focused on the
Installation makefile.

I am having problems specifying explicitly where the binaries should be
placed.  The two problems are:


1.  make install   automatically creates a named directory (in my case
sparc-sun-solaris2.8 )  when I use the --exec-prefix option.

    I ran,  ./configure --exec-prefix=/net/CAD/SunOS  ,   and after
'make install'   I had a
    "sparc-sun-solaris2.8" directory in my /net/CAD directory

    I added a hack my linking sparc-sun-solaris2.8 to SunOS,... but
still that is klugey


2.  'make install'  installs the binaries into two places.

    In my case it was     /net/CAD/bin ,
&&  /net/CAD/bin/sparc-sun-solaris2.8/bin





I was doing a comparison to some of the other Unix installation scripts,
and the behavior is different:


Example 1
--------

%> ./configure --prefix=/net/CAD  --exec-prefix=/net/CAD/SunOS
...
%> make
...
%> make install


%> cd  /net/CAD
%> ls
SunOS/  bin/  include/  info/  lib/  man/  share/
sparc-sun-solaris2.8@  var/


Now, the bin/ directory was created by the   'make install' command when
I was installing
the 'binutils' package.

This is not that consistent with the majority of other GNU utilities


Secondly,   I had to create the symlink sparc-sun-solaris2.8,   and link
it to SunOS OR the 'make install' command was going to create that
directory as well

Please let me know if I have done something incorrectly, but the other
GNU utilities install as follows:

--prefix:  is the location of architecture non-specific files
--exec-prefix:  is the location of architecture specific files (bins,
libs..etc)


Is a modified configuration file in the works... or do you need a
developer with spare time to write it, as I have some time to add the
fix.   The more standardized these things are easier it is to automate
installations

-Jimi Damon