According to some of the (printed) documentation I have here, the --target
option should be used when "you want to build a cross compilation
tool" (e.g. a cross-compiler etc.).
However, when you want to build code that should run on the system (even a
library), the --host and --build option appear. Normally, --build can
default to the value obtained by config.guess at run time (unless you do a
Canadia Cross: a triple-cross). Maybe you should try to set --host when
running the LibGGI configure.
However, my documentation is not so clear on this issue: --host should be
set with the value passed to --target, but *only* in the "Cygnus" tree
where the compiler source is part of the overall source tree. As you
probably do not configure gcc in the same run as LibGGI maybe you need to
set --host manually.
A last "note" of this document is to indicate that, for cross libraries,
actual configuration takes place at *make* time and not earlier: because
configure needs to use the cross-compiler output for these libraries and
cannot run checks directly on the build system.
Well, all these "cross" configuration issues are pretty complex indeed,
so, sorry if I did not help you much when telling to play also with the
--host and --build options.
Rodolphe
On Tue, 17 Jul 2001, Brian S. Julin wrote:
>
> Hmm,
>
> Even when given a --target=hppa-linux ./configure still
> tries to use the normally named (and hence native) programs
> (ld, nm, ar, as, gcc) instead of adjusting to cross-compiler
> names (hppa-linux-as, hppa-linux-nm, hppa-linux-ar, hppa-linux-as,
> hppa-linux-gcc).
>
> I *think* this is wrong -- but if it is shouldn't it be affecting
> many more people than just us? This should be rather core-level voodoo
> for autoconf. Must be some other explantion as to why this doesn't work
> in our case...
>
> (At least this is how I *think* cross compile is supposed to
> work, maybe I am wrong; it's how it works for binutils/gcc/etc,
> but that's a special case.)
>
> --
> Brian
>
>
>
