libtool woes

libtool woes

[Gary Thomas]

I'm trying to build a recipe which uses libtool.  The problem
I'm having is that the program uses glib-2.0 and one of the
libraries from that package has library dependencies.  This
is giving libtool major troubles.  I get errors like this:
   | sed: can't read =/usr/lib/libffi.la: No such file or directory
   | libtool: link: `=/usr/lib/libffi.la' is not a valid libtool archive

This is coming from libgobject-2.0.la which contains this line:
   dependency_libs=' =/usr/lib/libglib-2.0.la -lpthread -L=/usr/lib =/usr/lib/libffi.la'

The odd thing is that my recipe built the last time I tried,
but admittedly that was in late 2013.

Any ideas what I might be doing wrong or how to fix this?

Thanks

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------

Re: libtool woes

[Mark Hatle]

On 1/9/15 12:26 PM, Gary Thomas wrote:
> I'm trying to build a recipe which uses libtool.  The problem
> I'm having is that the program uses glib-2.0 and one of the
> libraries from that package has library dependencies.  This
> is giving libtool major troubles.  I get errors like this:
>    | sed: can't read =/usr/lib/libffi.la: No such file or directory
>    | libtool: link: `=/usr/lib/libffi.la' is not a valid libtool archive
> 
> This is coming from libgobject-2.0.la which contains this line:
>    dependency_libs=' =/usr/lib/libglib-2.0.la -lpthread -L=/usr/lib =/usr/lib/libffi.la'
> 
> The odd thing is that my recipe built the last time I tried,
> but admittedly that was in late 2013.
> 
> Any ideas what I might be doing wrong or how to fix this?

The version of libtool you are running doesn't understand cross compilation
(sysroot) paths.  (Sysroot paths start w/ the '='.)  You should use "libtoolize"
prior to running to update the libtool configuration to match the changes that
OE/YP have.  This works in almost all cases.. (where it doesn't work usually
means someone had manually hacked on the previous libtool file...)

--Mark

> Thanks
> 

Re: libtool woes

[Gary Thomas]

On 2015-01-09 11:57, Mark Hatle wrote:
> On 1/9/15 12:26 PM, Gary Thomas wrote:
>> I'm trying to build a recipe which uses libtool.  The problem
>> I'm having is that the program uses glib-2.0 and one of the
>> libraries from that package has library dependencies.  This
>> is giving libtool major troubles.  I get errors like this:
>>     | sed: can't read =/usr/lib/libffi.la: No such file or directory
>>     | libtool: link: `=/usr/lib/libffi.la' is not a valid libtool archive
>>
>> This is coming from libgobject-2.0.la which contains this line:
>>     dependency_libs=' =/usr/lib/libglib-2.0.la -lpthread -L=/usr/lib =/usr/lib/libffi.la'
>>
>> The odd thing is that my recipe built the last time I tried,
>> but admittedly that was in late 2013.
>>
>> Any ideas what I might be doing wrong or how to fix this?
>
> The version of libtool you are running doesn't understand cross compilation
> (sysroot) paths.  (Sysroot paths start w/ the '='.)  You should use "libtoolize"
> prior to running to update the libtool configuration to match the changes that
> OE/YP have.  This works in almost all cases.. (where it doesn't work usually
> means someone had manually hacked on the previous libtool file...)

Thanks, that fixed it.

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------