AC_NO_EXECUTABLES

[Samuel Thibault]

Hello,

Today we started working on making Debian GNU/Hurd rebootstrappable.
Thanks to Manolis' work, we have very clear ideas how to do it :)

We however stumbled on an issue: when cross-compiling, configure.ac
calls AC_NO_EXECUTABLES, and then 

AC_CHECK_FUNCS(file_exec_file_name exec_exec_file_name _hurd_exec_file_name)

would shout (this is a patch in Debian not yet in upstream).

I wonder why AC_NO_EXECUTABLES would be called when cross-compiling:
when one doesn't have a libc yet, we can't link executables of course,
but AIUI, we (Manolis and thus I) explicit which targets we want to
see built, so we don't care that automake cleans up targets for us;
conversely, once one *has* a libc, one wants to link executables (and
BTW run the above test).

So should we perhaps revert dc7e6a136e9baf98a2323758765aeab7ebae336c?

Samuel

Re: AC_NO_EXECUTABLES

[Manolis Ragkousis]

On 19 August 2015 at 20:06, Samuel Thibault  wrote:
> I'll see around that, but it'd be more convenient that ac_no_link makes
> link test fail only, not abort...

That sounds great. :)

Manolis

Re: AC_NO_EXECUTABLES

[Samuel Thibault]

Samuel Thibault, le Tue 18 Aug 2015 23:05:40 +0200, a écrit :
> I wonder why AC_NO_EXECUTABLES would be called when cross-compiling:
> when one doesn't have a libc yet,

Ok, apparently it's not completely forbidding executables, only if
linking doesn't work :)

I'll see around that, but it'd be more convenient that ac_no_link makes
link test fail only, not abort...

Samuel