From: Jamie Lenehan <lenehan@twibble.org>
To: Koen Kooi <koen@dominion.kabel.utwente.nl>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: perl tries to run './miniperl' on cross builds
Date: Fri, 17 Nov 2006 00:36:34 +1100 [thread overview]
Message-ID: <20061116133633.GA7740@twibble.org> (raw)
In-Reply-To: <455C6643.1020607@dominion.kabel.utwente.nl>
On Thu, Nov 16, 2006 at 02:23:15PM +0100, Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi,
>
> Since (approx.) yesterday the perl build fails with:
>
> |
> LD_LIBRARY_PATH=/data/build/koen/OE/build/tmp/angstrom/work/armv4t-angstrom-linux-gnueabi/perl-5.8.7-r21/perl-5.8.7
> ./miniperl -Ilib configpm --heavy=lib/Config_heavy.pl configpm.tmp
> | /bin/sh: ./miniperl: cannot execute binary file
That miniperl is meant to be renamed to miniperl-arm and then
symlinked to hostperl, so you end up with something like this:
[nynaeve][12:28AM]~/devel/oe/build/titan-glibc-24/tmp/work/perl-5.8.7-r21/perl-5.8.7%> file miniperl miniperl-arm hostperl
miniperl: symbolic link to `hostperl'
miniperl-arm: ELF 32-bit LSB executable, Hitachi SH, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped
hostperl: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for GNU/Linux 2.4.0, dynamically linked (uses shared libs), for GNU/Linux 2.4.0, not stripped
I can't think of any reason why that would have broken. I've done
full rebuilds targeting sh4 and i486 in the past few hours with no
problems.
Probably need to see the full log to see why the Makefile failed to
do this when it was meant to.
--
Jamie Lenehan <lenehan@twibble.org>
prev parent reply other threads:[~2006-11-16 13:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-16 13:23 perl tries to run './miniperl' on cross builds Koen Kooi
2006-11-16 13:33 ` Koen Kooi
2006-11-16 13:36 ` Jamie Lenehan [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=20061116133633.GA7740@twibble.org \
--to=lenehan@twibble.org \
--cc=koen@dominion.kabel.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.