From: Saul Wold <saul.wold@intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: libxml-parser-perl failure
Date: Sun, 16 Jan 2011 17:31:28 -0800 [thread overview]
Message-ID: <4D339BF0.5080607@intel.com> (raw)
Nitin, Richard:
I was looking into the libxml failure today, and found a couple of
different items that have changed in the newer version. First is the
addition of an arch_check function in the Extuils/MM_Any.pm and used
MakeMaker.pm. This check seems to use the archlib, which is set to
${STAGING_LIBDIR}/perl/${PV} by poky, but expects the final directory to
be the ARCH, which is why we get 5.12.2 for the Arch!
Why do we set archlib to the ${PV} instead of ${PV}/${target}
The next issue that I saw had to do with Errno.pm and another
architecture check, this time the errors:
ERROR from evaluation of
/vol/1/sgw/builds/ppc/tmp/work/ppc603e-poky-linux/libxml-parser-perl-2.36-r0/XML-Parser-2.36/Expat/Makefile.PL:
Errno architecture (x86_64-linux-thread-multi-2.6.34.7-56.fc13.x86_64)
does not match executable architecture
(powerpc-linux-2.6.37-rc5-yocto-standard+) at
/vol/1/sgw/builds/ppc/tmp/sysroots/x86_64-linux/usr/lib/perl/5.12.2/Errno.pm
line 11.
This looks like another check that will need some work
Sau!
next reply other threads:[~2011-01-17 1:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 1:31 Saul Wold [this message]
2011-01-17 15:24 ` libxml-parser-perl failure 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=4D339BF0.5080607@intel.com \
--to=saul.wold@intel.com \
--cc=poky@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.