Re: Incorrect argument to gcc for building dynamic library from archvies on solaris10

[Frederic Goudal]

Ralf Wildenhues <address@hidden>
> Cc: address@hidden
> Date: Fri, 19 Jan 2007 07:58:41 +0100
> Subject: Re: Incorrect argument to gcc for building dynamic library from arch
vies on solaris10

>* address@hidden wrote on Thu, Jan 18, 2007 at 11:45:51AM CET:
>> I have found a bug on autoconf 2.61 on solaris 10 using gcc 3.4.6
>
>> When building a dynamic library out of archives (.a) files the -z allextract
 
>> -z defaultextract flags are given to gcc.
>> The dynamic library build with theese argument is empty (no code is added).
>> Giving only the -z allextract build the correct library with all the code 
>> inside.
>
>Probably a Libtool bug, as Paul already noted.  Please report to the
>bug-libtool mailing list with the following information:
>./libtool --config

Ok. I don't really understand how autoconf and libtool are working togather.
Effectivelly the ./libtool --config gives a line with  :

# Compiler flag to generate shared objects directly from archives.
whole_archive_flag_spec="-z allextract\$convenience -z defaultextract"

I'm sorry about the error.

Btw it seems that the libtool I have used is not the last one

I have installed the last one (1.5.22) , I have installed again autocame and 
autoconf, but when I build again the configure script
I still have an oldversion of libtool... when making libtool --version
But the libtool script seems to have been updated..  and works (so it's a bug 
in libjasper : configure script is not uptodate)

I think I'm missing something, and turning in round...

f.g.