[OE-core] [PATCH] cross-canadian: Fix SHLIBSDIR when using multilib

[Richard Purdie]

On Tue, 2013-10-15 at 07:45 -0700, Khem Raj wrote:
> On Tue, Oct 15, 2013 at 6:40 AM, Richard Purdie
> <richard.purdie at linuxfoundation.org> wrote:
> > Both nativesdk and multilib use MLPREFIX for their partciular purposes. When
> > we have both set, cross-canadian can confuse SHLIBSDIR. This forces the
> > variable to the correct value for cross-canadian, fixing toolchains in
> > multilib builds.
> >
> > [YOCTO #5333]
> >
> > Signed-off-by: Richard Purdie <richard.purdie at linuxfoundation.org>
> > ---
> > diff --git a/meta/classes/cross-canadian.bbclass b/meta/classes/cross-canadian.bbclass
> > index 4387d05..7181c60 100644
> > --- a/meta/classes/cross-canadian.bbclass
> > +++ b/meta/classes/cross-canadian.bbclass
> > @@ -95,3 +95,8 @@ USE_NLS = "${SDKUSE_NLS}"
> >  # We have to us TARGET_ARCH but we care about the absolute value
> >  # and not any particular tune that is enabled.
> >  TARGET_ARCH[vardepsexclude] = "TUNE_ARCH"
> > +
> > +# If MLPREFIX is set by multilib code, shlibs
> > +# points to the wrong place so force it
> > +SHLIBSDIRS = "${PKGDATA_DIR}/nativesdk-shlibs"
> > +SHLIBSWORKDIR = "${PKGDATA_DIR}/nativesdk-shlibs"
> 
> in the patch that did not work for me
> I was using ${SDKPKGSUFFIX} instead of hardcoding 'nativesdk'
> and += instead of =

Well, one of the fields only takes a single value and there is only one
correct value here so = is more correct. I also needed my preceding
patch but I tested this and it did work afterwards...

You could try this (and the other patch) and see if it helps?

Cheers,

Richard