OpenEmbedded

openembedded@lists.linaro.org

1 participants
652 discussions

Re: [PATCH] gcc-linaro-5.2: Fix build with gcc6 on host

by Koen Kooi

Added into gerrit: https://review.linaro.org/11998 On 15 May 2016 at 18:28, Khem Raj <raj.khem(a)gmail.com> wrote: > Backport OE-core fix > > Signed-off-by: Khem Raj <raj.khem(a)gmail.com> > --- > .../recipes-devtools/gcc/gcc-linaro-5.2.inc | 1 + > .../0060-remove-prototypes-cfns.patch | 153 +++++++++++++++++++++ > 2 files changed, 154 insertions(+) > create mode 100644 meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2/0060-remove-prototypes-cfns.patch > > diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > index ca44d66..f928e77 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2.inc > @@ -108,6 +108,7 @@ SRC_URI = "https://releases.linaro.org/components/toolchain/gcc-linaro/${BASEPV} > file://0041-handle-target-sysroot-multilib.patch \ > file://0042-cxxflags-for-build.patch \ > file://PR67954.patch \ > + file://0060-remove-prototypes-cfns.patch \ > " > > # file://0038-fix-g++-sysroot.patch > diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2/0060-remove-prototypes-cfns.patch b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2/0060-remove-prototypes-cfns.patch > new file mode 100644 > index 0000000..2452b6f > --- /dev/null > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-linaro-5.2/0060-remove-prototypes-cfns.patch > @@ -0,0 +1,153 @@ > +Upstream-Status: backport > + > +From 1e5f1089dec3af328fd03125d6778f666d0bd4e4 Mon Sep 17 00:00:00 2001 > +From: edlinger <edlinger@138bc75d-0d04-0410-961f-82ee72b054a4> > +Date: Thu, 25 Feb 2016 15:33:50 +0000 > +Subject: [PATCH] 2016-02-25 Bernd Edlinger <bernd.edlinger(a)hotmail.de> > + > + Backported from mainline > + 2016-02-19 Jakub Jelinek <jakub(a)redhat.com> > + Bernd Edlinger <bernd.edlinger(a)hotmail.de> > + > + * Make-lang.in: Invoke gperf with -L C++. > + * cfns.gperf: Remove prototypes for hash and libc_name_p > + inlines. > + * cfns.h: Regenerated. > + * except.c (nothrow_libfn_p): Adjust. > + > + > +--- > + gcc/cp/Make-lang.in | 2 +- > + gcc/cp/cfns.gperf | 10 ++-------- > + gcc/cp/cfns.h | 41 ++++++++++++++--------------------------- > + gcc/cp/except.c | 3 ++- > + 5 files changed, 31 insertions(+), 37 deletions(-) > + > +diff --git a/gcc/cp/Make-lang.in b/gcc/cp/Make-lang.in > +index e98beb1..b09fb02 100644 > +--- a/gcc/cp/Make-lang.in > ++++ b/gcc/cp/Make-lang.in > +@@ -111,7 +111,7 @@ else > + # deleting the $(srcdir)/cp/cfns.h file. > + $(srcdir)/cp/cfns.h: > + endif > +- gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L ANSI-C \ > ++ gperf -o -C -E -k '1-6,$$' -j1 -D -N 'libc_name_p' -L C++ \ > + $(srcdir)/cp/cfns.gperf --output-file $(srcdir)/cp/cfns.h > + > + # > +diff --git a/gcc/cp/cfns.gperf b/gcc/cp/cfns.gperf > +index 68acd3d..214ecf6 100644 > +--- a/gcc/cp/cfns.gperf > ++++ b/gcc/cp/cfns.gperf > +@@ -1,3 +1,5 @@ > ++%language=C++ > ++%define class-name libc_name > + %{ > + /* Copyright (C) 2000-2015 Free Software Foundation, Inc. > + > +@@ -16,14 +18,6 @@ for more details. > + You should have received a copy of the GNU General Public License > + along with GCC; see the file COPYING3. If not see > + <http://www.gnu.org/licenses/>. */ > +-#ifdef __GNUC__ > +-__inline > +-#endif > +-static unsigned int hash (const char *, unsigned int); > +-#ifdef __GNUC__ > +-__inline > +-#endif > +-const char * libc_name_p (const char *, unsigned int); > + %} > + %% > + # The standard C library functions, for feeding to gperf; the result is used > +diff --git a/gcc/cp/cfns.h b/gcc/cp/cfns.h > +index 1c6665d..596f413 100644 > +--- a/gcc/cp/cfns.h > ++++ b/gcc/cp/cfns.h > +@@ -1,5 +1,5 @@ > +-/* ANSI-C code produced by gperf version 3.0.3 */ > +-/* Command-line: gperf -o -C -E -k '1-6,$' -j1 -D -N libc_name_p -L ANSI-C cfns.gperf */ > ++/* C++ code produced by gperf version 3.0.4 */ > ++/* Command-line: gperf -o -C -E -k '1-6,$' -j1 -D -N libc_name_p -L C++ --output-file cfns.h cfns.gperf */ > + > + #if !((' ' == 32) && ('!' == 33) && ('"' == 34) && ('#' == 35) \ > + && ('%' == 37) && ('&' == 38) && ('\'' == 39) && ('(' == 40) \ > +@@ -28,7 +28,7 @@ > + #error "gperf generated tables don't work with this execution character set. Please report a bug to <bug-gnu-gperf(a)gnu.org>." > + #endif > + > +-#line 1 "cfns.gperf" > ++#line 3 "cfns.gperf" > + > + /* Copyright (C) 2000-2015 Free Software Foundation, Inc. > + > +@@ -47,25 +47,18 @@ for more details. > + You should have received a copy of the GNU General Public License > + along with GCC; see the file COPYING3. If not see > + <http://www.gnu.org/licenses/>. */ > +-#ifdef __GNUC__ > +-__inline > +-#endif > +-static unsigned int hash (const char *, unsigned int); > +-#ifdef __GNUC__ > +-__inline > +-#endif > +-const char * libc_name_p (const char *, unsigned int); > + /* maximum key range = 391, duplicates = 0 */ > + > +-#ifdef __GNUC__ > +-__inline > +-#else > +-#ifdef __cplusplus > +-inline > +-#endif > +-#endif > +-static unsigned int > +-hash (register const char *str, register unsigned int len) > ++class libc_name > ++{ > ++private: > ++ static inline unsigned int hash (const char *str, unsigned int len); > ++public: > ++ static const char *libc_name_p (const char *str, unsigned int len); > ++}; > ++ > ++inline unsigned int > ++libc_name::hash (register const char *str, register unsigned int len) > + { > + static const unsigned short asso_values[] = > + { > +@@ -122,14 +115,8 @@ hash (register const char *str, register unsigned int len) > + return hval + asso_values[(unsigned char)str[len - 1]]; > + } > + > +-#ifdef __GNUC__ > +-__inline > +-#ifdef __GNUC_STDC_INLINE__ > +-__attribute__ ((__gnu_inline__)) > +-#endif > +-#endif > + const char * > +-libc_name_p (register const char *str, register unsigned int len) > ++libc_name::libc_name_p (register const char *str, register unsigned int len) > + { > + enum > + { > +diff --git a/gcc/cp/except.c b/gcc/cp/except.c > +index 3ff1ce6..2f2e396 100644 > +--- a/gcc/cp/except.c > ++++ b/gcc/cp/except.c > +@@ -1040,7 +1040,8 @@ nothrow_libfn_p (const_tree fn) > + unless the system headers are playing rename tricks, and if > + they are, we don't want to be confused by them. */ > + id = DECL_NAME (fn); > +- return !!libc_name_p (IDENTIFIER_POINTER (id), IDENTIFIER_LENGTH (id)); > ++ return !!libc_name::libc_name_p (IDENTIFIER_POINTER (id), > ++ IDENTIFIER_LENGTH (id)); > + } > + > + /* Returns nonzero if an exception of type FROM will be caught by a > +-- > +2.8.2 > + > -- > 2.8.2 > -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

10 years, 2 months

instructions for building a simple rootfs?

by Stuart Yoder

Are the instructions here: https://wiki.linaro.org/HowTo/ARMv8/OpenEmbedded ...still accurate? That wiki has not been updated in ~3 years. I'm looking for steps to build a simple openembedded based aarch64 rootfs. Anywhere else I should be looking? Thanks, Stuart Yoder NXP Semiconductor

10 years, 3 months

Re: [meta-linaro-toolchain][jethro][PATCH] gcc-runtime: Fix QA Issues

by Koen Kooi

Fixed commit message and added into gerrit: https://review.linaro.org/11606 On 26 April 2016 at 12:20, <zongchun.yu(a)nxp.com> wrote: > From: Zongchun Yu <zongchun.yu(a)nxp.com> > > Fix following QA Issue: > ERROR: QA Issue: gcc-runtime: Files/directories were installed but not > shipped in any package: > /usr/lib/libstdc++fs.la > /usr/lib/libstdc++fs.a > Please set FILES such that these items are packaged. Alternatively if > they are unneeded, avoid installing them or delete them within > do_install. > gcc-runtime: 2 installed and not shipped files. [installed-vs-shipped] > > Signed-off-by: Zongchun Yu <zongchun.yu(a)nxp.com> > --- > .../recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb | 8 ++++++++ > 1 file changed, 8 insertions(+) > > diff --git a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > index a147ebd..0ae3085 100644 > --- a/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > +++ b/meta-linaro-toolchain/recipes-devtools/gcc/gcc-runtime_linaro-5.2.bb > @@ -5,3 +5,11 @@ require recipes-devtools/gcc/gcc-runtime.inc > FILES_libgomp-dev += "\ > ${libdir}/gcc/${TARGET_SYS}/${BINV}/include/openacc.h \ > " > + > +FILES_libstdc++-dev += "\ > + ${libdir}/libstdc++fs.la \ > +" > + > +FILES_libstdc++-staticdev += "\ > + ${libdir}/libstdc++fs.a \ > +" > -- > 1.8.3.2 > -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

10 years, 3 months

Re: [fido/jethro][PATCH] external-linaro-toolchain: correct path for libgcov.a to package properly

by Koen Kooi

Added into gerrit: https://review.linaro.org/11498 https://review.linaro.org/11499 On 20 April 2016 at 19:53, Denys Dmytriyenko <denis(a)denix.org> wrote: > From: Denys Dmytriyenko <denys(a)ti.com> > > With migration from crosstool-NG to ABE, libgcov.a changed path and is now > available in ${libdir}. So, instead of being packaged into own libgcov-dev > package, it gets picked up by "catchall" libc6-staticdev package. This mostly > works, as long as nothing directly depends on libgcov-dev. Unfortunately, > packagegroup-core-standalone-sdk-target does and is the one being used when > building SDKs with -c populate_sdk. Correct path to generate libgcov-dev pkg. > > Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> > --- > This is required for fido/jethro, but krogoth/master introduces single -dev > package rule, so separate libgcov-dev package can be dropped entirely. > > .../external-linaro-toolchain/external-linaro-toolchain.bb | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > index ea41179..531caf7 100644 > --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > @@ -301,7 +301,7 @@ PKGV_gdbserver = "${ELT_VER_GDBSERVER}" > ALLOW_EMPTY_${PN}-mtrace = "1" > FILES_${PN}-mtrace = "${bindir}/mtrace" > > -FILES_libgcov-dev = "${libdir}/${TARGET_SYS}/${BINV}/libgcov.a" > +FILES_libgcov-dev = "${libdir}/libgcov.a" > > FILES_libsegfault = "${base_libdir}/libSegFault*" > > -- > 2.2.0 > > _______________________________________________ > linaro-dev mailing list > linaro-dev(a)lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

10 years, 3 months

Linaro toolchain PV/PR issue

by Stefan Agner

Hi Koen, I think you mentioned that issue already briefly at ELC, but I stumbled upon it independently again: We have issues with the versioning of the Linaro toolchain in Ångström. While it happens with the Ångström package feed, I think it is actually a problem of how the meta-linaro layer uses PV/PR. It seems that the change to the 2015.11-2 release added yet another hyphen, which gets interpreted wrong by opkg. When we build a new image, and try to download something which just asks for linaro-5.2, we get the following error: Not downgrading libgcc1 from linaro-5.2-r2015.11-2 to linaro-5.2-r2015.11.0 on root. Downgrading? The "2015.11-2" release should be an upgrade... This can be verified when checking the versions using the compare-versions command: $ opkg compare-versions "linaro-5.2-r2015.11-2" '>=' "linaro-5.2-r2015.11"; echo $? 1 Error code is set, hence the comparison is _not_ satisfied. Whether there is another .0 at the end of r2015.11 does not matter (Btw, where is that coming from?) Things after the hyphen are interpreted by opkg as package revision... This leads to the following akward situation (added some debug prints into opkg's source): $ ./src/opkg --offline-root . compare-versions linaro-5.2-r2015.11-2 '>=' linaro-5.2-r2015.11 parse_version, version linaro-5.2-r2015.11, revision 2 parse_version, version linaro-5.2, revision r2015.11 This change introduced the additional hyphen: https://git.linaro.org/openembedded/meta-linaro.git/commitdiff/62333718e8f3… I think everything should work if that additional -2 would be a .2... However, hyphens in the main version number are actually quite frowned upon, also the debian policy does not allow hyphens: https://www.debian.org/doc/debian-policy/ch-binary.html#s-versions So maybe even the hyphen in linaro-5.2 should be something else... -- Stefan

10 years, 3 months

Re: OE recipes for 5.3-2016.02 toolchain?

by Koen Kooi

On 19 April 2016 at 07:30, Koen Kooi <koen.kooi(a)linaro.org> wrote: > On 18 April 2016 at 23:03, Denys Dmytriyenko <denis(a)denix.org> wrote: >> On Fri, Apr 15, 2016 at 08:01:48AM +0200, Koen Kooi wrote: >>> On 14 April 2016 at 18:27, Denys Dmytriyenko <denis(a)denix.org> wrote: >>> > On Thu, Apr 14, 2016 at 10:04:18AM +0200, Koen Kooi wrote: >>> >> On 14 April 2016 at 07:09, Fathi Boudra <fathi.boudra(a)linaro.org> wrote: >>> >> > On 14 April 2016 at 00:05, Denys Dmytriyenko <denis(a)denix.org> wrote: >>> >> >> Koen, et al, >>> >> >> >>> >> >> With the release of 5.3-2016.02 Linaro toolchain it is now possible to use the >>> >> >> binary version with the external-linaro-toolchain recipe. Are there any >>> >> >> immediate plans to provide corresponding recipes to build the same version of >>> >> >> the toolchain from sources? Thanks. >>> >> > >>> >> > Yes, the recipes for 5.3-2016.02 will be added. It's targeted for next cycle. >>> >> >>> >> The test build is still running, but here's the gerrit: >>> >> >>> >> https://review.linaro.org/11376 >>> > >>> > Thanks! >>> >>> It breaks grub, I'll sort that out with the toolchain folks later today. >>> >>> > What about glibc-2.21? >>> >>> Haven't looked at that one yet. >> >> Any updates on the above 2 items? It's not exactly blocking me currently, as I >> have workarounds in place, but it would be nice to get these resolved in >> krogoth/2.1... Thanks! > > For grub we need both a newer toolchain and a newer binutils. Still > haven't looked at glibc 2.21 yet, sorry. An update to the gcc situation: we've decided to move it to the next cycle (2016.06) so we can use a newer gcc release with the fix included. I've retracted https://review.linaro.org/#/c/11376/ to reflect this. -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

10 years, 3 months

Re: [PATCH] external-linaro-toolchain: update to work with Linaro GCC 5.3-2016.02

by Koen Kooi

Added into gerrit: https://review.linaro.org/11146 On 1 April 2016 at 03:04, Denys Dmytriyenko <denis(a)denix.org> wrote: > From: Denys Dmytriyenko <denys(a)ti.com> > > * libasan and libgfortran changed major version number, handle both > * only remove dups of lib*-${ELT_VER_LIBC}.so when they are regular and identical files > preserve them if one is a symlink to another or files are different > > Signed-off-by: Denys Dmytriyenko <denys(a)ti.com> > --- > .../external-linaro-toolchain.bb | 33 ++++++++++++++++++---- > 1 file changed, 28 insertions(+), 5 deletions(-) > > diff --git a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > index 676b7ba..7b29ce5 100644 > --- a/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > +++ b/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb > @@ -89,7 +89,6 @@ do_install() { > cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/* ${D}${includedir} > if [ -d ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS} ]; then > cp -a ${EXTERNAL_TOOLCHAIN}/${ELT_TARGET_SYS}/libc/usr/include/${ELT_TARGET_SYS}/* ${D}${includedir} > - > rm -r ${D}${includedir}/${ELT_TARGET_SYS} > fi > > @@ -115,14 +114,22 @@ do_install() { > ln -sf ../../lib/libnss_nisplus.so.2 ${D}${libdir}/libnss_nisplus.so > ln -sf ../../lib/libnss_db.so.2 ${D}${libdir}/libnss_db.so > ln -sf ../../lib/libm.so.6 ${D}${libdir}/libm.so > - ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so > ln -sf ../../lib/libatomic.so.1 ${D}${libdir}/libatomic.so > ln -sf ../../lib/libgomp.so.1 ${D}${libdir}/libgomp.so > ln -sf ../../lib/libitm.so.1 ${D}${libdir}/libitm.so > ln -sf ../../lib/libssp.so.0 ${D}${libdir}/libssp.so > ln -sf ../../lib/libstdc++.so.6 ${D}${libdir}/libstdc++.so > - ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so > ln -sf ../../lib/libubsan.so.0 ${D}${libdir}/libubsan.so > + if [ -f ${D}${base_libdir}/libasan.so.2 ]; then > + ln -sf ../../lib/libasan.so.2 ${D}${libdir}/libasan.so > + else > + ln -sf ../../lib/libasan.so.1 ${D}${libdir}/libasan.so > + fi > + if [ -f ${D}${base_libdir}/libgfortran.so.6 ]; then > + ln -sf ../../lib/libgfortran.so.6 ${D}${libdir}/libgfortran.so > + else > + ln -sf ../../lib/libgfortran.so.3 ${D}${libdir}/libgfortran.so > + fi > > # remove potential .so duplicates from base_libdir > # for all symlinks created above in libdir > @@ -139,7 +146,6 @@ do_install() { > rm -f ${D}${base_libdir}/libcidn.so > rm -f ${D}${base_libdir}/libBrokenLocale.so > rm -f ${D}${base_libdir}/libthread_db.so > - rm -f ${D}${base_libdir}/libthread_db-1.0.so > rm -f ${D}${base_libdir}/libanl.so > rm -f ${D}${base_libdir}/libdl.so > rm -f ${D}${base_libdir}/libnss_nisplus.so > @@ -155,7 +161,24 @@ do_install() { > rm -f ${D}${base_libdir}/libubsan.so > > # Besides ld-${ELT_VER_LIBC}.so, other libs can have duplicates like lib*-${ELT_VER_LIBC}.so > - rm -rf ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so > + # Only remove them if both are regular files and are identical > + for i in ${D}${base_libdir}/lib*-${ELT_VER_LIBC}.so; do > + f=$(echo $i | sed 's/-${ELT_VER_LIBC}//') > + l=$(ls $f.*) > + if [ $(readlink -f $i ) = $l ]; then > + echo "$i is a symlink of $l, keep it" > + elif [ $(readlink -f $l ) = $i ]; then > + echo "$l is a symlink of $i, keep it" > + else > + cmp -s $i $l > + if [ $? -eq 0 ]; then > + echo "$i is a duplicate of $l, remove it" > + rm $i > + else > + echo "$i and $l are different files, keep them both" > + fi > + fi > + done > > if [ -d ${D}${base_libdir}/arm-linux-gnueabi ]; then > rm -rf ${D}${base_libdir}/arm-linux-gnueabi > -- > 2.2.0 > > _______________________________________________ > linaro-dev mailing list > linaro-dev(a)lists.linaro.org > https://lists.linaro.org/mailman/listinfo/linaro-dev -- Koen Kooi Builds and Baselines | Release Manager Linaro.org | Open source software for ARM SoCs

10 years, 4 months

[RPB] add framework on top of openembedded RPB build

by Christophe Priouzeau

Hi, With RPB environment I can easily add some new layer via a local_manifest way on top of rpb manifest. In this case, I see a potential issue and I would like to open a discussion about it. If I add a layer: - bsp layer: env setup script take into account all the bsp layer available on the source tree. - framework layer (like meta-qt5, meta-browser, ...): in this case there is no automatic way to use this layer on the build, we must manually change the bblayers.conf file before the compilation to take into account the framework layer. Question: Have you some plan to support such request ? The goal are to provide a reproducible build which are as based on RPB which add the support of new frameworks by using the same way to initialize the environment without making manual change on bblayers.conf. Proposal: - if there is bblayers.conf and local.conf files on local_manifest, this files will overwrote the default files available on manifest via the env setup script. Thanks for your feedback. Regards Christophe Priouzeau -- Christophe Priouzeau Software Engineer from STMicroelectronics Group: LHG (Linaro Digital Home Group) STMicroelectronics | 9 Rue Pierre Felix Delarue | 72000 Le mans | France

10 years, 4 months

SD Card Image

by M. Gregory

I am trying to create an image in openembedded similar to the hikey-jessie_developer_20151130-387.img. I created an image with 2 partitions, boot (fat32) and rootfs (ext4). My kernel (Image) and device tree are located in the boot partition. When I put the card in the dev board and turn it on it does not boot. I get a message "Fail to start BootNext". I can boot the kernel using the sd card grub option on the eMMC, but not by default. Are there directions on how to create an sd card image like the hikey-jessie_developer_20151130-387.img? -Machon

10 years, 5 months

Re: [fido][meta-linaro-toolchain] arm-none-eabi-4.8-2014.04

by Jim Wilson

On Fri, Feb 19, 2016 at 1:38 PM, Xi Zhou Zhou <joel.zhou(a)broadcom.com> wrote: > I download the pre-built toolchain for one of our armv6 board. > https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-… This is the embedded toolchain, for systems not running linux. > After plug it into Yocto as an external toolchain, it failed to install it > correctly. Yocto is linux, so there is a contradiction here. It isn't clear why you are trying to do this, as this is not expected to work. > ../meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb, > do_install > | DEBUG: Executing shell function do_install > | cp: cannot stat > `/opt/gcc-linaro-arm-none-eabi-4.8-2014.04_linux/arm-none-eabi/libc/lib/*': > No such file or directory Yocto is looking for the linux toolchain sysroot, but this isn't a linux toolchain, so there is no sysroot. If Yocto is supposed to work with embedded toolchains, then you need to fix the yocto scripts to make the toolchain sysroot optional. Or if you are really trying to download the linux toolchain, then you should instead grab https://releases.linaro.org/14.04/components/toolchain/binaries/gcc-linaro-… Jim

10 years, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

OpenEmbedded