Ralf Wildenhues <[EMAIL PROTECTED]> writes: > Hello Simon, > > * Simon Josefsson wrote on Thu, Aug 24, 2006 at 10:06:28AM CEST: >> >> Perhaps autoconf should de-couple "can i execute this binary" from >> "cross-compilation". Autoconf could test if it is possible to run >> programs by compiling a small program and run it, and see if the >> output is correct. So even if it is cross-compiling, it would be able >> to run tests that need to run a binary. > > Definitely. On the TODO list, together with this: > http://lists.gnu.org/archive/html/autoconf/2005-04/msg00072.html > http://lists.gnu.org/archive/html/autoconf/2006-03/msg00131.html
Ah, so it seems to be a common problem, and might be solved eventually. On the other hand, for GNU/Linux systems, I wonder whether it isn't easier to modify the kernel to run non-native binaries. Similar to how Windows binaries can be run like native binaries, through wine, and the details are hidden by the system. Instead of running wine, you could use ssh to copy and log in on the remote machine. This won't solve the problem for proprietary platforms, but if someone cares about that, they could sponsor a better solution... ;) /Simon
