[OE-core] Relocatable SDK Perl issues

[Richard Purdie]

On Mon, 2013-02-18 at 11:50 +0000, Jack Mitchell wrote:
> On 18/02/13 11:48, Jack Mitchell wrote:
> > The relocatable SDK seems to have had it's perl issues slipped back in 
> > somewhere.
> >
> > Running autoreconf -i on my autotools application leads to the following:
> >
> > Can't locate strict.pm in @INC (@INC contains: 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/share/autoconf 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/site_perl/5.14.3/ 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/site_perl/5.14.3 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/vendor_perl/5.14.3/ 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/vendor_perl/5.14.3 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/5.14.3/ 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/5.14.3 
> > /opt/dblinux/1.0-20130213/sysroots/x86_64-oecore-linux/usr/lib/perl/5.14.3 
> > .) at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/share/autoconf/Autom4te/Channels.pm 
> > line 70.
> > BEGIN failed--compilation aborted at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/share/autoconf/Autom4te/Channels.pm 
> > line 70.
> > Compilation failed in require at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/share/autoconf/Autom4te/ChannelDefs.pm 
> > line 19.
> > BEGIN failed--compilation aborted at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/share/autoconf/Autom4te/ChannelDefs.pm 
> > line 19.
> > Compilation failed in require at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/bin/gnu-configize 
> > line 40.
> > BEGIN failed--compilation aborted at 
> > /mnt/SSD/r0005sdk/130213r0/sysroots/x86_64-oecore-linux/usr/bin/gnu-configize 
> > line 40.
> > autoreconf: gnu-configize failed with exit status: 2
> >
> > Any ideas? This was broken a while ago (~6 months), and then was fixed 
> > (~2 months) and it seems to have regressed again somewhere along the way.
> >
> 
> I see a bug that may be along the same lines here: 
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=3338
> 
> Could anyone confirm it's the same issue, if so; I'll sit quiet :)

Its probably related, hard to tell for sure. It would be good if we
could get this resolved.

Cheers,

Richard