On Fri, Mar 01, 2019 at 06:54:50AM -0800, Khem Raj wrote: > On Fri, Feb 22, 2019 at 12:33 PM Jacob Stiffler <[email protected]> wrote: > > > > Signed-off-by: Jacob Stiffler <[email protected]> > > --- > > v2 changes: > > * Use COMPATIBLE_HOST instead of anonymous python to limit to x86_64-linux > > > > ..._6-2017-q1-update.bb => gcc-arm-none-eabi_6-2017-q1-update.bb} | 8 > > ++++++-- > > 1 file changed, 6 insertions(+), 2 deletions(-) > > rename recipes-ti/devtools/{gcc-arm-none-eabi-native_6-2017-q1-update.bb > > => gcc-arm-none-eabi_6-2017-q1-update.bb} (83%) > > > > diff --git > > a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb > > b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb > > similarity index 83% > > rename from recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb > > rename to recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb > > index 1140f27..ae3d1d7 100644 > > --- a/recipes-ti/devtools/gcc-arm-none-eabi-native_6-2017-q1-update.bb > > +++ b/recipes-ti/devtools/gcc-arm-none-eabi_6-2017-q1-update.bb > > @@ -3,7 +3,6 @@ LICENSE = "GPL-3.0-with-GCC-exception & GPLv3" > > > > LIC_FILES_CHKSUM = > > "file://share/doc/gcc-arm-none-eabi/license.txt;md5=c224e429f53a1a6ce70bf8986ea2990b" > > > > -inherit native > > this means it is also available as target package now.
Yes, hence COMPATIBLE_HOST below. Also see earlier discussion on v1 of the patch for other considered options. > > require recipes-ti/includes/ti-paths.inc > > > > SRC_URI = > > "https://developer.arm.com/-/media/Files/downloads/gnu-rm/6_1-2017q1/gcc-arm-none-eabi-6-2017-q1-update-linux.tar.bz2;name=gcc-arm-none"; > > @@ -13,6 +12,9 @@ SRC_URI[gcc-arm-none.sha256sum] = > > "e7aad2579f02e3b095c6d7899ca5e6a70cfa9b8a8cbd6 > > > > S = "${WORKDIR}/gcc-arm-none-eabi-6-2017-q1-update" > > > > +# only x86_64 is supported > > +COMPATIBLE_HOST = "x86_64.*-linux" > > + > > fails on qemux86-64 > https://errors.yoctoproject.org/Errors/Details/230712/ The errors are from package_qa and seem to be due to binary nature of the package and RDEPENDS between libraries. > you have to limit its availability to native and nativesdk only. While intension of COMPATIBLE_HOST was to limit it to native and nativesdk indirectly, x86-64 target does also match. And theoretically it can be a valid use case for this bare-metal Arm cross-compile toolchain... I wonder if simply skipping "file-rdeps" QA checks would be fine. > > do_install() { > > install -d ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE} > > cp -r ${S}/. ${D}${GCC_ARM_NONE_TOOLCHAIN_RECIPE} > > @@ -20,4 +22,6 @@ do_install() { > > > > FILES_${PN} = "${GCC_ARM_NONE_TOOLCHAIN_RECIPE}/*" > > > > -INSANE_SKIP_${PN} = "already-stripped" > > +INSANE_SKIP_${PN} = "already-stripped libdir staticdev" > > + > > +BBCLASSEXTEND = "native nativesdk" > > -- > > 2.7.4 > > > > -- > > _______________________________________________ > > meta-ti mailing list > > [email protected] > > https://lists.yoctoproject.org/listinfo/meta-ti > -- > _______________________________________________ > meta-ti mailing list > [email protected] > https://lists.yoctoproject.org/listinfo/meta-ti -- _______________________________________________ meta-ti mailing list [email protected] https://lists.yoctoproject.org/listinfo/meta-ti
