RE: Building arm-elf cross under GCC 3.0.4 on HP-UX 11.00

[Jepsen Hans Peter <hans_peter_jepsen at Danfoss dot com>]

Hello Kai

You wrote:

>  Don't ever use PATH for setting search paths for GCC, see 
> the default search
> paths using 'gcc -print-search-dirs' etc., and add more 
> directories there using
> the 'GCC_EXEC_PREFIX'... Consult your GCC-manual about these 
> things : "Environment
> Settings for GCC" or something there...
> 
>  If you can build the 'arm-elf' targeted GCC yourself, there 
> is no reason to not
> use the default '$prefix/$target/bin' for the target 
> binutils, so that the GCC
> and the binutils configured using them will work perfectly 
> together... Then even
> the GCC_EXEC_PREFIX is not necessary.

I tried this on my HP-UX 10.20 machine:

cd build-binutils

../binutils-2.11.2/configure --host=hppa2.0-hp-hpux10.20
--target=powerpc-eabi --prefix=/opt/local/gcc-3.0.4/powerpc-eabi

gmake all install

cd ../build-gcc-core

../gcc-3.0.4-core/configure
--with-gcc-version-trigger=/home/hpj/work/gcc-3.0.4-core/gcc/version.c
--host=hppa2.0-hp-hpux10.20 --target=powerpc-eabi
--prefix=/opt/local/gcc-3.0.4/powerpc-eabi --enable-languages=c
--with-local-prefix=/opt/local/gcc-3.0.4/powerpc-eabi/powerpc-eabi
--without-headers --with-newlib --d
isable-shared

gmake all-gcc install-gcc 

Then I get the error:
powerpc-eabi-ar  rc ./libgcc.a ........
gmake[2]: powerpc-eabi-ar: Command not found

What should I to to avoid this error???


>  I remember the messing with PATH being very common among the 
> HP-UX users, meanwhile
> all the other GCC-users never use it to point to the GNU 
> binutils...  So there must
> be some FAQ or something the HP-UX-users all have read, and 
> it saying that the GNU
> binutils must be pointed with PATH or something... Any clues 
> about where you got
> this idea?

I can not remember, where I got this idea from. But I have experienced
several times, that when I not set the PATH between building binutils and
building gcc, I get an error.

kind regards

Hans Peter

------
Want more information?  See the CrossGCC FAQ, http://www.objsw.com/CrossGCC/
Want to unsubscribe? Send a note to crossgcc-unsubscribe@sources.redhat.com