From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: perl build problem in .dev
Date: Fri, 07 May 2010 17:13:37 +0200 [thread overview]
Message-ID: <hs1an1$a54$1@dough.gmane.org> (raw)
In-Reply-To: <1273241033.457.319.camel@trini-m4400>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 07-05-10 16:03, Tom Rini wrote:
> On Fri, 2010-05-07 at 11:29 +0200, Koen Kooi wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Hi,
>>
>> I'm unable to build perl_5.8.8.bb:
>>
>> | ln -s hostperl miniperl
>> | ./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl lib/Config.pm
>> | ./miniperl: error while loading shared libraries: libperl.so: cannot
>> open shared object file: No such file or directory
>> | make[1]: *** [lib/Config.pod] Error 127
>> | make[1]: Leaving directory
>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/perl-5.8.8-r33/perl-5.8.8'
>> | make[1]: Entering directory
>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/perl-5.8.8-r33/perl-5.8.8'
>> | ./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl lib/Config.pm
>> | ./miniperl: error while loading shared libraries: libperl.so: cannot
>> open shared object file: No such file or directory
>> | make[1]: *** [lib/Config.pod] Error 127
>> | make[1]: Leaving directory
>> `/OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/perl-5.8.8-r33/perl-5.8.8'
>>
>> koen@dominion:/OE/build$ !find
>> find /OE/angstrom-dev/sysroots/ -name "libperl.so*"
>> /OE/angstrom-dev/sysroots/x86_64-linux/usr/lib/perl/5.8.8/CORE/libperl.so
>>
>> I tried doing
>>
>> - -export PERLHOSTLIB = "${STAGING_LIBDIR_NATIVE}/perl/${PV}/"
>> +export PERLHOSTLIB = "${STAGING_LIBDIR_NATIVE}/perl/${PV}/CORE/"
>>
>> which didn't help. Any ideas?
>
> Yeah, when we mangle it for $ORIGIN, we just broke how target perl works
> since (expanding
> $ORIGIN) /OE/angstrom-dev/work/armv7a-angstrom-linux-gnueabi/perl-5.8.8-r33/perl-5.8.8/../lib/perl/5.8.8/CORE/libperl.so
> doesn't exist. Not sure how to solve this with chrpath, but I know when
> we link vs $ORIGIN we 'fix' this by still having a path based link left
> in (as the more common problem we run into is "build a util that's not
> installed, to build the final util that is installed").
Your suggestion on IRC fixed it:
do_configure() {
# Make hostperl in build directory be the native perl
- - cp -f ${HOSTPERL} hostperl
+ ln -sf ${HOSTPERL} hostperl
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
iD8DBQFL5C4hMkyGM64RGpERAocBAKChtijAAMmmAI9JUSK/xKuC+25B2QCgkujg
2ZR+o433TkKBm6E3NKAs2B0=
=LiKy
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2010-05-07 15:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-07 9:29 perl build problem in .dev Koen Kooi
2010-05-07 12:43 ` Graeme Gregory
2010-05-07 14:03 ` Tom Rini
2010-05-07 15:13 ` Koen Kooi [this message]
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='hs1an1$a54$1@dough.gmane.org' \
--to=k.kooi@student.utwente.nl \
--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.