This is the mail archive of the
mailing list for the GCC project.
Re: Successful build on debian, but...
- From: Joe Buck <Joe dot Buck at synopsys dot com>
- To: janis187 at us dot ibm dot com (Janis Johnson)
- Cc: zubzet at yahoo dot es (Ayose), gcc at gcc dot gnu dot org
- Date: Fri, 17 May 2002 10:47:00 -0700 (PDT)
- Subject: Re: Successful build on debian, but...
> It would be safest to use the configure options --with-ld= and
> --with-as= to ensure that your new compiler is using the correct linker
> and assembler.
An alternative is to do the following:
1) after running configure, create a symbolic link from the linker and/or
assembler you want to use into the gcc subdirectory of the build
directory, that is, while in the build directory
ln -s /path/to/linker gcc/ld
ln -s /path/to/assembler gcc/as
This works because the bootstrap looks first in the gcc directory for
2) after doing make install, create corresponding symbolic links into
the directory that stores the compiler passes, e.g.
ln -s /path/to/linker $prefix/lib/gcc-lib/TARGET/VERSION/
ln -s /path/to/assembler $prefix/lib/gcc-lib/TARGET/VERSION/
where TARGET is something like i686-pc-linux-gnu, sparc-sun-solaris2.8
or whatever, and VERSION is 3.1 for the 3.1 release.
This works because the installed compiler looks in that directory first
for compiler passes.
This can be advantageous if you anticipate that you might want to switch
assembers or linkers without rebuilding the compiler (for example, to
move to a newer binutils) -- just move the links.