On 11/18/07, Ralf Wildenhues <[EMAIL PROTECTED]> wrote:
> Hello,
>
> This is an Autoconf issue, not an Automake one.
I thought as much.
> GCC has similar issues, too, and they use hacks like GCC_NO_EXECUTABLES
> to work around the issues, see
> gcc/config/no-executables.m4
>
> in the GCC source
* Benoit Sigoure wrote on Mon, Nov 19, 2007 at 12:30:12AM CET:
>
> Typically, I *guess* (untested) adding this before all your
> AC_PROG_CC/CXX/LIBTOOL and everything will trick configure:
But it does not work. Just for example set
ac_cv_prog_ac_ct_CC=blabla
to see why it won't work. I sai
Perhaps I am confused. And I don't have a cross-compile build anywhere
handy.
I thought that the cross-compile setup built and linked a test
executable and scanned for known filenames. It does not try and run the
generated file.
This should work on a cross-compile build just the way it is.
H
On Nov 18, 2007, at 6:42 PM, NightStrike wrote:
On Nov 18, 2007 10:11 AM, Benoit Sigoure <[EMAIL PROTECTED]> wrote:
On Nov 18, 2007, at 9:02 AM, NightStrike wrote:
I hit another snag in my project. I am building a runtime as a
component of a cross compiler. Configure has to determine the
On Nov 18, 2007 10:11 AM, Benoit Sigoure <[EMAIL PROTECTED]> wrote:
>
> On Nov 18, 2007, at 9:02 AM, NightStrike wrote:
>
> > I hit another snag in my project. I am building a runtime as a
> > component of a cross compiler. Configure has to determine the various
> > tools to use (denoted by passi
On Nov 18, 2007, at 9:02 AM, NightStrike wrote:
I hit another snag in my project. I am building a runtime as a
component of a cross compiler. Configure has to determine the various
tools to use (denoted by passing --host=xx to configure), and I use
all of the AC_PROG_XX macros. This may be an
Hello,
This is an Autoconf issue, not an Automake one.
* NightStrike wrote on Sun, Nov 18, 2007 at 09:02:08AM CET:
> I hit another snag in my project. I am building a runtime as a
> component of a cross compiler. Configure has to determine the various
> tools to use (denoted by passing --host=x
I hit another snag in my project. I am building a runtime as a
component of a cross compiler. Configure has to determine the various
tools to use (denoted by passing --host=xx to configure), and I use
all of the AC_PROG_XX macros. This may be an autoconf issue instead
of automake, but what happe
