Re: autoconf usage question

[Kai Ruottu <karuottu at mbnet dot fi>]

Povolotsky, Alexander wrote:

> Cross-compiling gnu (autoconfed packages) on the "clean" cygwin host system 
> recently worked well for me, while using the script (adopted from Kai
> Ruottu):
>
> #!/bin/sh
> AR=/usr/local/bin/powerpc-linux-ar \
> CC=/usr/local/bin/powerpc-linux-gcc-3.3.2 \
> CFLAGS=-Os \
> CXXFLAGS=-Os \
> NM=/usr/local/bin/powerpc-linux-nm \
> RANLIB=/usr/local/bin/powerpc-linux-ranlib \
> AR_FOR_BUILD=ar \
> CC_FOR_BUILD=cc \
> GCC_FOR_BUILD=gcc \
> NM_FOR_BUILD=nm \
> RANLIB_FOR_BUILD=ranlib \
> AR_FOR_TARGET=/usr/local/bin/powerpc-linux-ar \
> CC_FOR_TARGET=/usr/local/bin/powerpc-linux-gcc-3.3.2 \
> GCC_FOR_TARGET=/usr/local/bin/powerpc-linux-gcc-3.3.2 \
> CXX_FOR_TARGET=/usr/local/bin/powerpc-linux-g++.exe \
> OLDCC=/usr/local/bin/powerpc-linux-gcc-3.3.2 \

 Not sure if this 'OLDGCC' is used in the 'gcc/Makefile' any more...

> NM_FOR_TARGET=/usr/local/bin/powerpc-linux-nm \
> RANLIB_FOR_TARGET=/usr/local/bin/powerpc-linux-ranlib \
> ../configure --host=ppc-linux-gnu

but of course telling everything here is the assumption. If the
$build and $target are not told, the 'config.guess' or something
will try to 'guess' these systems. Running './config.guess' in
the main GCC source dir will tell what will be get and whether
this is just that 'ppc-linux-gnu'. If not, a case like:

 --host=ppc-linux-gnu --build=powerpc-unknown-linux-gnu \
 --target=powerpc-unknown-linux-gnu

(first given, the two last guessed) will lead to a cross-GCC from
'ppc-linux-gnu' to 'powerpc-unknown-linux-gnu'.  Computers are
stupid creatures when born and the software on them to give some
more intelligency for them is especially stupid. However it usually
is the 'computer' which causes all those crashes, not the software
if one looks at the news. Never agreed, always suspected the SW...

 My opinion is that configure should do just as told after getting
enough information. The $build stuff is in the native places, the
$host stuff where the $host tells it being and similarly with the
$target stuff. If $build = $host = $target, all they are native and
no tries with any '$target-<tool>' or something stuff should happen.
If 'configure' doesn't do what one tells, it is a serious bug then.

 If you have choosed to use the name 'powerpc-linux' for your system,
then maybe using that everywhere would be the best approach, so using
a different name like 'ppc-linux-gnu' can cause the stupid 'configure'
to fail when getting the multitude of system names...





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