This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
merge-with-binutils documentation is wrong/incomplete
- To: gcc-bugs at gcc dot gnu dot org
- Subject: merge-with-binutils documentation is wrong/incomplete
- From: Markus Werle <markus at lufmech dot rwth-aachen dot de>
- Date: Tue, 20 Mar 2001 11:36:40 +0100
On http://gcc.gnu.org/install/download.html
it is said:
"If you also intend to build binutils (either to upgrade an existing
installation or for use in place of the corresponding tools of your OS),
unpack the binutils distribution either in the same directory or a
separate
one. In the latter case, add symbolic links to any components of the
binutils
you intend to build alongside the compiler (bfd, binutils, gas, gprof,
ld,
opcodes,...) to the directory containing the GCC sources."
In the first case, using e.g. binutils-2.10.1
one ends up with destroying files coming with the gcc distribution:
[markus@computer] gcc-2.95.3/ > for file in `ls ../binutils-2.10.1/`;
do if [ -f $file ]; then diff -q ../binutils-2.10.1/$file ./$file; fi;
done
Files ../binutils-2.10.1/Makefile.in and ./Makefile.in differ
Files ../binutils-2.10.1/README and ./README differ
Files ../binutils-2.10.1/config-ml.in and ./config-ml.in differ
Files ../binutils-2.10.1/config.guess and ./config.guess differ
Files ../binutils-2.10.1/config.sub and ./config.sub differ
Files ../binutils-2.10.1/configure and ./configure differ
Files ../binutils-2.10.1/configure.in and ./configure.in differ
Files ../binutils-2.10.1/ltconfig and ./ltconfig differ
Files ../binutils-2.10.1/ltmain.sh and ./ltmain.sh differ
Files ../binutils-2.10.1/missing and ./missing differ
=> unpacking into the same directory is the wrong way for sure.
So now I come to the latter case:
Do I still have to configure --with-gnu-as --with-gnu-ld as before?
Or will this be detected automagically?
I would prefer a detailed description of what is set when and how
and how I can manipulate it.
Markus