Re: [RFT PATCH v4 0/8] Sysroot series

[Charles Wilson]

On 8/2/2010 4:51 PM, Paolo Bonzini wrote:
> On Mon, Aug 2, 2010 at 22:13, Ralf Wildenhues <address@hidden> wrote:
>> - is it intended that the = remain in the .la files after these are
>> moved to their final location on the host system?  Or should
>> --mode=finish remove them?
> 
> I thought so, but --mode=finish takes a directory. :/
> 
> Should I do that on all .la files?

Wait, I thought you NEEDED the '=' marker in there, or the .la files
wouldn't give correct behavior when they were used from within a sysroot.

Sure, you might want to strip out the '=' flags if you copied/installed
the built package over onto $host and wanted to do "native" development
over there, but...it seemed cleaner to me to simply require an updated
libtool for clients that want to link against libs built, from a cross
$build, using the new libtool.  And if you want to "clean up" the "="
flags when you deploy on $host -- it seems to me that that is a
packaging/integration task (e.g. not libtool's problem).

>> - should we provide a minimal patch for vendors 2.2.10 (or earlier
>> versions, maybe even 1.5.x) that makes libtool not barf upon = in .la
>> files, for smoother upgrades (given that 2.2.12 could contain other
>> issues not making for a smooth upgrade path)?
> 
> Yes

Good idea.

> , especially if --mode=finish does nothing.

I'm starting to think it really shouldn't strip out the =. So a
compatibility patch for older libtool is probably a good idea.

BTW, does libltdl need to know about these '=' markers, when it tries to
load a module?

--
Chuck