Re: static lib with libtool 1.5

[Ralf Wildenhues]

[ sorry, forgot one part ]

* Ralf Wildenhues wrote on Fri, Jul 01, 2005 at 05:10:22AM CEST:
> * Jeremie LE HEN wrote on Wed, Jun 29, 2005 at 11:20:18AM CEST:
> > 
> > I think I got my problem resolved by using the lastest version of
> > libtool (1.5.18) : with exactly the same command sequence, I get
> > a static library with libtool-1.5.18 in the .libs/ directory, while
> > libtool-1.5.6 doesn't produce it.  Is it a known behaviour ?  Are there
*snip*
> 
> Fortunately, your problem is not related to 1.5.6 vs 1.5.18 at all (at
> least not a lot).  If you had configured and compiled 1.5.6 yourself
> with "cc" as C compiler, it would have worked fine.  Or used "gcc"
> instead of "cc" as compiler name.  Or -- and this is the real solution
> to your problem -- add "--tag=CC" to your command line.  I actually
> forgot to mention this the first time around:
> 
>   libtool --tag=CC --mode=link cc -o ...

Erm, surely the fact that 1.5.18 does not create a static library but
also does not warn nor fail with unguessed tag still looks like a bug to
me.

Regards,
Ralf