[Top][All Lists]

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

Re: dll cross-compile, .libs/impgen is a win-exe, not a linux-binary

From: Olly Betts
Subject: Re: dll cross-compile, .libs/impgen is a win-exe, not a linux-binary
Date: Wed, 20 Jun 2001 08:36:09 +0100
User-agent: Mutt/1.2.5i

On Wed, Jun 20, 2001 at 03:23:18AM +0200, Guido Draheim wrote:
> What is HOST_CC ? It has no default, and cross-gcc is the wrong cc.

It's meant to point to a native compiler in precisely this situation to
solve the problem of impgen getting cross-compiled and so being useless.

> Did now try with HOST_CC=/usr/bin/cc to get a working impgen.
> Did not work either - look for the ".libs/.libs" part in the
> output which is clearly wrong. 

The HOST_CC patch was from me, and it worked when applied.  Looks like
something has changed since and stopped it working.

> HOST_CC is only used with impgen, no other reference. IIRC, there
> are plans to have more binary compile-tools, which leasd to the
> question whether there are plans for automatic support of HOST_CC
> (whatever that is anyway)

HOST_CC is also refered to in config.status, and apparently comes from gcc's
bootstrapping process.  The name CC_FOR_BUILD is preferable - see the
discussion stemming from the first url below - perhaps libtool ought to
change to this?

I did also produce an autoconf macro for probing for HOST_CC.  Ideally this
should be triggered automatically by AM_PROG_LIBTOOL when cross-compiling to
windows is detected, but I don't think it got incorporated into libtool or
autoconf (it's actually of general use for compiling build-time tools when

You can find the macro here:

There's also an entirely different macro for testing CC_FOR_BUILD here:

This one sets CFLAGS_FOR_BUILD, etc but seems to rely on the user setting
CC_FOR_BUILD whereas mine actually has a reasonable stab at find a native
compiler by itself.


reply via email to

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