cross compiling

[Stepan Kasal]

Hello Alexander.

On Thu, Dec 20, 2007 at 09:16:34PM +0300, Alexander Vasiliev wrote:
> checking for extra flags to get ANSI library prototypes... configure:
> error: cannot run test program while cross compiling
> See `config.log' for more details.
> configure: error: ./configure failed for glib-1.2.8"

This seems to be a bug in pkg-config/glib-1.2.8/configure.in .
I'll look at the details in due time and report here.
Could you plese tell me which version of pkg-config you were
building?

Generally speaking:
This message indicates that configure.ac (or configure.in) called
(directly or indirectly) the macro AC_RUN_IFELSE (or AC_TRY_RUN)
without the fourth parameter, which defines the result for the cross
compile case, which, naturally, does not allow configure to execute
the just-built test program.  This is described in:
http://www.gnu.org/software/autoconf/manual/html_node/Runtime.html

> Dear group.
> --host=arm  --exec-prefix=/home/windhunter/dv/gtk/davinci/pkg
> CC=/opt/mv_pro_4.0/montavista/pro/devkit/arm/v5t_le/bin/arm_v5t_le-gcc"
...
> I especialy confused about what i found in the congfig.log:
>  "WARNING: In the future, Autoconf will not detect cross-tools
> whose name does not start with the host triplet."
> 
> Does it mean, that i cannot use tools with prefix arm_v5t_le- for
> architecture arm?

Definitely not.  In your case, you specify CC explicitely on the
command line, disabling the automatic detection; that functionality
will stay intact.

If you had not specified CC on cthe command line, the configure
script would look for "arm-gcc arm-cc gcc cc". (The list might be
longe but that does not matter.)  With future releases of Autoconf,
only the first half of the list will be used.
That should not cause problems; having a _cross_ compiler without any
prefix is not a good practice anyway.
Hope this clears your worries.

Have a nice Xmass,
	Stepan Kasal