Skip to contentSkip to conversation

libtool woes

DISCUSSION Gary Thomas 2 participants 3 messages Jan 9, 2015

lore
Share & tools
lore
#0 lore raw

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

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------
#1 lore raw
Quoted 7 lines · 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

Quoted 7 lines

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

Quoted 2 lines

Thanks

#2 lore raw
Quoted 14 lines · Mark Hatle
Quoted 13 lines · 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.

Quoted 7 lines
Quoted 1 line

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.

Signature · 4 lines
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------