[csw-maintainers] libtool rearranges linker arguments and puts -L/opt/csw/lib last

Roger Håkansson hson at opencsw.org
Wed Jan 13 18:03:13 CET 2010


Dagobert Michelsen wrote:
> Hi Roger,
> 
> Am 13.01.2010 um 17:51 schrieb Roger Håkansson:
> 
>> Roger Håkansson wrote:
>>> Dagobert Michelsen wrote:
>>>> Hi Phil,
>>>>
>>>> Am 12.01.2010 um 18:32 schrieb Philip Brown:
>>>>> On Sun, Jan 10, 2010 at 6:42 AM, Ben Walton <bwalton at opencsw.org> 
>>>>> wrote:
>>>>>>
>>>>>> Given the issues we constantly hit with libtool, I always find myself
>>>>>> wondering if it was ever a benefit instead of a burden.  Any
>>>>>> grey-beards care to offer some historical perspective on this?
>>>>>
>>>>> "libtool evil".
>>>>>
>>>>> this is why our official documented guidelines are,
>>>>> "REMOVE .la files from your packages" !!!
>>>>
>>>> He he, and just now I get a bug report for a package that doesn't work
>>>> without the .la-files:
>>>>  <http://www.opencsw.org/mantis/view.php?id=4145>
>>> Same as ImageMagick, they use libtool runtime to load internal modules.
>>> So MERGE_EXCLUDE_LIBTOOL need to be set to
>>> MERGE_EXCLUDE_LIBTOOL ?= $(libdir)/lib.*\.la instead of
>>> MERGE_EXCLUDE_LIBTOOL ?= $(libdir)/.*\.la
>>
>> Note: Thats not a general solution, packages with 64-bit libs or 
>> packages which have libraries in other places need to have 
>> MERGE_EXCLUDE_LIBTOOL properly set.
>>
>> "MERGE_EXCLUDE_LIBTOOL ?= $(libdir).*/lib.*\.la" might be a more 
>> general solution
> 
> I would like to keep the general solution of excluding all libtool-files
> and let the maintainer decide this on a case-by-case basis. Including
> .la-files should be the exception.
> 

Correct, with "general solution", I meant "starting point solution for 
those cases that need to keep some .la-files"
There are only a few cases where .la-files need to be kept in the package.


More information about the maintainers mailing list