* libxml-parser-perl failure
@ 2011-01-17 1:31 Saul Wold
2011-01-17 15:24 ` Richard Purdie
0 siblings, 1 reply; 2+ messages in thread
From: Saul Wold @ 2011-01-17 1:31 UTC (permalink / raw)
To: poky@yoctoproject.org
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!
^ permalink raw reply [flat|nested] 2+ messages in thread* Re: libxml-parser-perl failure
2011-01-17 1:31 libxml-parser-perl failure Saul Wold
@ 2011-01-17 15:24 ` Richard Purdie
0 siblings, 0 replies; 2+ messages in thread
From: Richard Purdie @ 2011-01-17 15:24 UTC (permalink / raw)
To: Saul Wold; +Cc: poky@yoctoproject.org
Hi,
On Sun, 2011-01-16 at 17:31 -0800, Saul Wold wrote:
> 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
This seemed to be introduced by my change to wrap the perl binary with a
wrapper script. I've updated the wrapper to append to PERL5LIB rather
than overwrite it which I think is why these failures were appearing.
They change the lib search path to pass data around, ugly but we can
work around it.
We still need to check the perl binary does work ok with sstate
relocation after this.
Cheers,
Richard
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2011-01-17 15:24 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-01-17 1:31 libxml-parser-perl failure Saul Wold
2011-01-17 15:24 ` Richard Purdie
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.