This is the mail archive of the
gcc-help@gcc.gnu.org
mailing list for the GCC project.
Installation using relative (instead of hard-coded) paths
- To: gcc-help at gcc dot gnu dot org
- Subject: Installation using relative (instead of hard-coded) paths
- From: Srinivas Mantripragada <smprag at yahoo dot com>
- Date: Tue, 22 May 2001 11:30:55 -0700 (PDT)
Hi,
I am trying to build a GCC cross-compiler
(host=linux, target=mips) from the top-level
directory. When building/installing the final
executables, I noticed that it uses fully-expanded
paths, i.e it picks cc1 from
.../usr/lib/gcc-lib/mips-*-ecoff/2.95.2/cc1
and include from
../usr/lib/gcc-lib/mips-*-ecoff/2.95.2/../../../../mips-*-ecoff/include
etc..
The final executables being built in
../usr/mips-*ecoff/bin
etc.
This makes it hard as a general mechanism, since
these fully expanded paths are not easily portable.
Is there any way for GCC, when it's building the
various components, to use relative paths instead,..?
I used the "prefix=../.." mechanism, but it doesn't
seem to work.
host=i686-pc-linux-gnu
GNU_DIR=`pwd`
cd $GNU_DIR
prefix=$GNU_DIR/usr
i=$prefix/bin
HEADERS=$GNU_DIR/../newlib-1.8.2/newlib/libc/include
../../gcc-2.95.2/configure --host=$host
--target=$target --prefix=$prefix -v --with-gnu-as
--with-gnu-ld --with-headers=$HEADERS
Any help will be greatly appreciated..
Thanx,
Sri
__________________________________________________
Do You Yahoo!?
Yahoo! Auctions - buy the things you want at great prices
http://auctions.yahoo.com/