Nicolas Williams wrote:
> On Tue, Feb 26, 2008 at 08:25:25PM -0800, Danek Duvall wrote:
>   
>> On Tue, Feb 26, 2008 at 05:47:06PM -0600, Nicolas Williams wrote:
>>
>>     
>>>>                       What ends up in the runpath here by default, anyway?
>>>>         
>>> /usr/lib -- yeah, no runpath should be needed then, right?
>>>
>>> BTW, I needed fix_elf_runpath() because libtool was somehow adding
>>> $SRC/lib/libsqlite3/... to the runpath of libtclsqlite3 (but not to
>>> libsqlite3).  Don't ask me why; I don't know why.
>>>       
>> Because libtool is a pile.  But you also say that /usr/lib ends up there
>> by default, so I'm a bit confused.
>>     
>
> You're not kidding.  And I'm confused also.  I think /usr/lib showed up
> because it was in LD_OPTIONS (but that didn't override whatever libtool
> wanted -- it merged with it).  Libtool is turning out to be a nightmare.
>   
I'll be generous and simply say that my experience with it hasn't been 
particularly favorable.
>   
>> You might want to ping Stefan Teleman, as he wrestled against libtool for
>> many weeks in some of the SFW components.  I think he managed to win, but I
>> can't remember now how he did it.  It'd be nice if we didn't have to resort
>> to elfedit to make these changes, since we *are* building from source,
>> however uncooperative.
>>     
>
> OK.  And if we could put together a guide for others who might follow,
> then that'd be even better.
>   
That is something that I am hoping to break free some time for.  I have 
been slowly building tools to ease the pain and suffering of integrating 
a component and getting the bits right.  A while back, I added proto-fix 
and install-proto to make it more likely that you could use "cd $(VER) ; 
make DESTDIR=$(ROOT) ... install" to install in the proto area instead 
of generating an install-sfw script.  Unfortunately, generating an 
install-sfw script is tedious and error prone.  Package generation is 
another place that it potentially tedious and error prone.  I have a 
tool that I have been working on thats not quite ready to integrate, but 
generates a reasonable first stab at a package prototype with fairly 
sane defaults for attributes of entries.  I was hoping to fix a couple 
of things in it, like depend file generation, and make it available in 
the gate tools directory when I integrate my next wad.  And yes, all of 
this belongs in a guide to ease everyone's pain and suffering.

    -Norm




Reply via email to