On Friday, January 06, 2012 04:35:11 AM Scott Garman wrote: > On 01/05/2012 03:29 PM, Andreas Müller wrote: > > Hi > > > > currently some libs are moving from $libdir (/usr/lib) -> $base_libdir > > (/lib). I have the following questions: > > > > * can sombody explain a bit more what is it for and how the decision is > > made to transit libs? I read the commit messages but still have no idea > > what this enhances / fixes. What is 'not safe' or - I guess the > > insane.bbclass modification deals same issue - 'system recovery'. Is > > that something I (should) have? :) > > > > * can somebody please take care what I see with meta-oe / obexd: > > > > | arm-angstrom-linux-gnueabi-libtool: link: cannot find the library > > > > `/home/Superandy/tmp/oe-core-eglibc/sysroots/overo/lib/libusb-1.0.la' or > > unhandled argument `=/lib/libusb-1.0.la' > > > > | make[1]: *** [src/obexd] Error 1 > > > > libusb-1.0.la still resides in .../sysroots/overo/usr/lib. Maybe it needs > > transition too? If yes: Are there also others which need libtool-lib > > transition? > > > > Thanks > > > > Andreas > > Hi Andreas, > > I think you mentioned in another thread that the "why" part of your > question has been addressed. Yes. > As for the location of libusb-1.0.la - it > looks like Richard previously missed one of my commits moving > libusb-compat, and just merged it to oe-core master: > > http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=198f2ac06e6024575 > 0a2c6561b8c8e2eaa93f6be > > Does this fix the issue? > > I may be hard to reach tomorrow, so I hope RP or Mark Hatle can field > any further questions for me. > I think the problem I reported was that *.la is in /usr/lib while all others are now in /lib. I tried moving libusb-1.0.la to /lib manually and rebuild udev and obexd without issues.
So why are your patches moving *.la back to /usr/lib? Andreas _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
