From: Tom Rini <tom_rini@mentor.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: invalid removal of rpath from native binaries during installation or staging
Date: Thu, 01 Jul 2010 15:41:18 -0700 [thread overview]
Message-ID: <4C2D198E.6010603@mentor.com> (raw)
In-Reply-To: <1278021938.8213.7.camel@utx.utx.cz>
Stanislav Brabec wrote:
> Hallo.
>
> Packages like perl-native and gettext-native compile correctly, but then
> stage broken binaries, that miss rpath from binaries. Such binaries work
> only if the library of the same name exists in the host system, which is
> not correct.
>
> Example:
> ERROR: log data follows (/OE/build/tmp/work/x86_64-linux/libxml-parser-perl-native-2.36-r2/temp/log.do_configure.27765)
> | perl: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
>
> Now try:
> ben:/OE/build> /OE/build/tmp/sysroots/x86_64-linux/usr/bin/perl
> /OE/build/tmp/sysroots/x86_64-linux/usr/bin/perl: error while loading shared libraries: libperl.so: cannot open shared object file: No such file or directory
> ben:/OE/build> /OE/build/tmp/work/x86_64-linux/perl-native-5.8.8-r19/perl-5.8.8/perl
> (this instance works)
>
> Work around: simply copy binaries from work directly to sysroots and compilation continues correctly.
Can you use readelf -d on your perl? The whole point of the relative
path calculation that relocatable.bbclass does is to fix the hard cases
like perl. Thanks!
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2010-07-01 22:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-01 22:05 invalid removal of rpath from native binaries during installation or staging Stanislav Brabec
2010-07-01 22:41 ` Tom Rini [this message]
2010-07-01 23:19 ` Stanislav Brabec
2010-07-02 12:52 ` Richard Purdie
Reply instructions:
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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C2D198E.6010603@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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.