Does this mean that a fix for this issue was pushed to mainline?
> -----Original Message----- > From: [email protected] [mailto:meta-arago- > [email protected]] On Behalf Of Denys Dmytriyenko > Sent: Friday, June 20, 2014 12:57 PM > To: [email protected] > Subject: [meta-arago] [PATCH 17/19] arago.conf: with unification on mainline, > remove PACKAGE_ARCH logic > > From: Denys Dmytriyenko <[email protected]> > > Signed-off-by: Denys Dmytriyenko <[email protected]> > --- > meta-arago-distro/conf/distro/arago.conf | 9 --------- > 1 file changed, 9 deletions(-) > > diff --git a/meta-arago-distro/conf/distro/arago.conf b/meta-arago- > distro/conf/distro/arago.conf > index 7bd1de2..b652fda 100644 > --- a/meta-arago-distro/conf/distro/arago.conf > +++ b/meta-arago-distro/conf/distro/arago.conf > @@ -72,12 +72,3 @@ ENTERPRISE_DISTRO = "1" > # Arago based SDK. No need to prevent gst-ffmpeg from being used since we > # disable troublesome software. > LICENSE_FLAGS_WHITELIST = "commercial_gst-ffmpeg" > - > -# Some machines with the same architecture use different kernel versions. > -# Set PACKAGE_ARCH to allow packages to be seperated by both architecture > and -# linux-libc-headers version. > -PACKAGE_ARCH := "${TUNE_PKGARCH}-${PREFERRED_VERSION_linux-libc- > headers}" > -# Need to include the new PACKAGE_ARCH to the PACKAGE_ARCHS variable - > PACKAGE_ARCHS += "${TUNE_PKGARCH}-${PREFERRED_VERSION_linux-libc- > headers}" > -# Adjust some vars accordingly > -STAGING_BINDIR_TOOLCHAIN = > "${STAGING_DIR_NATIVE}${bindir_native}/${TUNE_PKGARCH}- > ${PREFERRED_VERSION_linux-libc-headers}${TARGET_VENDOR}- > ${TARGET_OS}" > -- > 2.0.0 > > _______________________________________________ > meta-arago mailing list > [email protected] > http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago _______________________________________________ meta-arago mailing list [email protected] http://arago-project.org/cgi-bin/mailman/listinfo/meta-arago
