Re: unlink-busy does not support cross-compilation

2019-03-23 Thread Bruno Haible
Jim Meyering wrote: > What do you think about using the existing run-test code when possible, > but to resort to using that hard-coded list when cross-compiling? > That way, the code adapts well (at least in some cases) when it finds > a new type of system for which this is applicable. Possible.

Re: unlink-busy does not support cross-compilation

2019-03-23 Thread Jim Meyering
On Sat, Mar 23, 2019 at 10:26 AM Bruno Haible wrote: > Hi Jim, > > The module 'unlink-busy' does not support cross-compilation: It uses > AC_RUN_IFELSE, thus calling the compiler for the host, and then sets > INSTALL, which is meant to point to a command to execute on

unlink-busy does not support cross-compilation

2019-03-23 Thread Bruno Haible
Hi Jim, The module 'unlink-busy' does not support cross-compilation: It uses AC_RUN_IFELSE, thus calling the compiler for the host, and then sets INSTALL, which is meant to point to a command to execute on the build machine. It should IMO better use the compiler for the build machine