[yocto] SSTATE_MIRRORS problems, libpthread.so.0 not found ...

[Jonas Jonsson L]

Hi, sorry for late answer, but yes, the libpthread-files exists in my customized sandbox sysroot (as well as in the ‘clean’ sandbox sysroot).  The (autotooled) project that I’m build is trying to link an application and it uses CXXLD (which is CXX => arm-poky-linux-gnuabi-g++).
LD has the –sysroot flag appended in the command, CXXLD doesn’t have it (according to the generated Makefile).  Am I or autotools doing something wrong here?

/Jonas


From: Khem Raj [mailto:raj.khem at gmail.com]
Sent: den 14 april 2013 23:48
To: Jonas Jonsson L
Cc: Yocto Mailinglist (yocto at yoctoproject.org)
Subject: Re: [yocto] SSTATE_MIRRORS problems, libpthread.so.0 not found ...



On Thursday, April 11, 2013, Jonas Jonsson L <jonas.l.jonsson at ericsson.com<mailto:jonas.l.jonsson at ericsson.com>> wrote:
> Hi!
>
>
>
> I’m building several different Raspberry Pi images that are almost the same, some configuration issues (ip-address, hostnames etc) differs on those different images.  My solution was to simply build a ‘clean’ image without any tweaking, then use all the packages from the ‘clean’ image via SSTATE_MIRRORS and build my images with their own peculiarities.  The ‘clean’ image is basically a ‘core-image-minimal’ image (rpi-hwup-image for Raspberry Pi).
>
>
>
> So in ‘clean’ I have the sstate-cache, and in the other configurations, I set up
>
> SSTATE_MIRRORS ?= “file://.* file:///home/foobar/clean/sstate-cache/PATH<file:///\\.*%20file:\home\foobar\clean\sstate-cache\PATH>”
>
> in my local.conf ….  It works like a charm with regards to speed and disk-space.
>
>
>
> The package that I’ve built builds clean without any warnings in the ‘clean’ build.  However, if I don’t build my package in the clean image, but in one of my ‘configured’ images, it fails.  All of a sudden, the linker can’t find neither /lib/libpthread.so.0 nor /usr/lib/libpthread_nonshared.a L
>

It seems you have totally different workspaces per image which share same state is that right ?

Do you have these files populated in one of customised sandboxes

Linker should look into the customised Sandbox's sysroot not clean sandbox one
>
>
> buildfolder/tmp/sysroots/raspberrypi > ls -ll lib/libpthread.so.0 usr/lib/libpthread_nonshared.a lib/libpthread-2.17.so<http://libpthread-2.17.so>
>
> -rwxr-xr-x 1 foobar bitbakers 960802 Apr 11 12:47 lib/libpthread-2.17.so<http://libpthread-2.17.so>
>
> lrwxrwxrwx 1 foobar bitbakers     18 Apr 11 12:47 lib/libpthread.so.0 -> libpthread-2.17.so<http://libpthread-2.17.so>
>
> -rw-r--r-- 1 foobar bitbakers   3376 Apr 11 12:47 usr/lib/libpthread_nonshared.a
>
>
>
> What’s going on here?  The sysroot (for the GNU tools) points to the correct folder, and the project is a standard autotools project, thus no magic involved.  Is there any particular dependency that I must set up in order to use pthreads?
>
>
>
> Any ideas?  By the way, I’m on poky/master (march 7:th), ‘git log –n 1’ shows ‘6d9a3ac0515380d0789ee3d316c08212592a6f9a’ (if that’s interesting…)
>
>
>
> Best regards,
>
> Jonas Jonsson
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20130422/0b797795/attachment.html>