[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: hello-2.1.91 build failure on MacOS X

From: Simon Josefsson
Subject: Re: hello-2.1.91 build failure on MacOS X
Date: Thu, 24 Aug 2006 10:26:20 +0200
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.0.50 (gnu/linux)

Ralf Wildenhues <address@hidden> 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

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... ;)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]