From: "Евгений Астафьев" <email@example.com>
To: "Martin Jansa" <firstname.lastname@example.org>
Subject: Re: Different *.so content in recipe and rootfs
Date: Fri, 18 Dec 2015 16:46:59 +0300 [thread overview]
Message-ID: <email@example.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1711 bytes --]
Yes, I have buildstats, image-mklibs, image-prelink
>Пятница, 18 декабря 2015, 14:07 +01:00 от Martin Jansa <firstname.lastname@example.org>:
>On Fri, Dec 18, 2015 at 01:35:24PM +0300, Евгений Астафьев wrote:
>> Yocto 2.0
>> I have a recipe qtbase.
>> RECIPE SIDE:
>> File /packages-split/qtbase/usr/lib/libQt5Core.so.5.5.1
>> Size: 5186760
>> Time: 01:21
>> ROOTFS SIDE:
>> File /usr/lib/libQt5Core.so.5.5.1
>> Size: 5206080
>> Time: 01:21
>Do you happen to have prelink enabled for your image?
>> The SDK constructed by -c populate_sdk has same version of file as a recipe side has.
>> Actually I have no file with size 5200680 anywhere in my /tmp dir. The only place it exists - rootfs image.
>> I have many such differencies, including libc.
>> The image works. Qt works. Local debugging in a device console works.
>> Remote debugging fails. The debugger says I have different versions of libs in my SDK's sysroot and the device.
>> If I view the files in MC's viewer - it shows the same function names, but different addresses.
>> If I put the file libQt5Core.so.5.5.1 from the recipe to rootfs manually - image still works. Remote debugger reports no errors.
>> But I still want to clear out what's going on and how to make debuggable image w.o. hand manipulations.
>> BTW I did a full rebuild of the image. No success, libs are still different
>> Any help is appreciated.
>> yocto mailing list
>Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Type: text/html, Size: 3856 bytes --]
next prev parent reply other threads:[~2015-12-18 13:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-18 10:35 Different *.so content in recipe and rootfs Евгений Астафьев
2015-12-18 13:07 ` Martin Jansa
2015-12-18 13:46 ` Евгений Астафьев [this message]
2015-12-18 14:12 ` Евгений Астафьев
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.