From: Martyn Welch <martyn.welch@ge.com>
To: Yocto Project <yocto@yoctoproject.org>
Subject: Perl build failure
Date: Fri, 17 Feb 2012 09:42:11 +0000 [thread overview]
Message-ID: <4F3E20F3.4060202@ge.com> (raw)
Hi,
I'm attempting to build the head of the master branch, targeting
core-image-minimal on qemux86 with an up to date Ubuntu 10.04 32-bit system.
I am getting the following error from perl:
/home/welchma/Documents/linux/yocto/yocto_head/build/tmp/work/i586-poky-linux/perl-5.14.2-r2/perl-5.14.2/Cross/generate_config_sh
config.sh-x86-linux >
/home/welchma/Documents/linux/yocto/yocto_head/build/tmp/work/i586-poky-linux/perl-5.14.2-r2/perl-5.14.2/Cross/../config.sh
Unable to open config.sh-x86-linux at
/home/welchma/Documents/linux/yocto/yocto_head/build/tmp/work/i586-poky-linux/perl-5.14.2-r2/perl-5.14.2/Cross/generate_config_sh
line 47.
make: *** [perl] Error 2
looking in the "Cross" folder there is no config.sh-x86-linux, there is
however a config.sh-i586-linux.
Looking into the Makefile that seems to be run I see:
$(TOPDIR)/generate_config_sh config.sh-$(SYS) > $(TOPDIR)/../config.sh
where:
export SYS=$(ARCH)-$(OS)
The run.do_compile script has:
export ARCH="x86"
Which I guess explains why it's getting that value. Looking at the perl
recipe, the do_configure stage creates a config file and I can see that this
exists in build dir and that contains what I believe are the required values:
ARCH = i586
OS = linux
However this doesn't seem to be explicitly referenced by do_compile and
doesn't seem to be referenced by generate_config_sh.
Any ideas?
Martyn
--
Martyn Welch (Lead Software Engineer) | Registered in England and Wales
GE Intelligent Platforms | (3828642) at 100 Barbirolli Square
T +44(0)1327322748 | Manchester, M2 3AB
E martyn.welch@ge.com | VAT:GB 927559189
next reply other threads:[~2012-02-17 9:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-17 9:42 Martyn Welch [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-05-24 12:32 perl build failure Phil Blundell
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=4F3E20F3.4060202@ge.com \
--to=martyn.welch@ge.com \
--cc=yocto@yoctoproject.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.