Hi,
Wnen I compile some gnulib modules for a glibc systems in cross-compilation
mode (by specifing both --host and --build at configure time, with a different
value), I'm seeing results such as
checking for putenv compatible with GNU and SVID... no
whereas for the hosted build I get
checking for putenv compatible with GNU and SVID... yes
Likewise for some other functions (malloc, realloc, utimes, dup2, getgroups,
...).
Two things are wrong here:
1) Cross-compilation guesses, that is, the third branch of AC_RUN_IFELSE,
should better be marked as "guessing no", rather than "no", for clarity.
2) On glibc systems, which are often used as cross-compilation targets
(think of embedded systems (routers, map navigation devices, etc.)),
the cross-compilation guesses should better be correct. I.e. when
no problem is known on glibc systems or Linux, the result should be
"guessing yes".
I'm going to propose some patches to improve this.
Bruno
