On Jun 20, 2001, Olly Betts <[EMAIL PROTECTED]> wrote:
> The name CC_FOR_BUILD is preferable - see the discussion stemming
> from the first url below - perhaps libtool ought to change to this?
I'd approve any reasonable patch that fixed this :-)
--
Alexandre Oliva Enjoy Guarana', see http://
"Gary V. Vaughan" wrote:
>
> On Wednesday 20 June 2001 10:58 am, Guido Draheim wrote:
> >
> > Anyway, libtool.m4 and libtool-content are out of sync in this case,
> > it is clearly buggy, don't you think Gary? ;-)
>
> The last time I used the impgen code in libtool, it worked fine for me.
> How
On Wednesday 20 June 2001 10:58 am, Guido Draheim wrote:
>
> Anyway, libtool.m4 and libtool-content are out of sync in this case,
> it is clearly buggy, don't you think Gary? ;-)
The last time I used the impgen code in libtool, it worked fine for me.
However, I must admit that I didn't test cyg
moin moin, Olly,
Olly Betts wrote:
>
> 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-
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
What is HOST_CC ? It has no default, and cross-gcc is the wrong cc.
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.
There is no check, if the output is empty - it would atleast
contain the "
