7765d89009
Compiling on the target using runtime libs from external-arm-toolchain requires libgcc.a, as libgcc_s.so explains: /* GNU ld script Use the shared library, but some functions are only in the static library. */ GROUP ( libgcc_s.so.1 -lgcc ) Otherwise it results in errors like: | /usr/lib/gcc/arm-linux-gnueabi/9.2.1/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgcc | /usr/lib/gcc/arm-linux-gnueabi/9.2.1/../../../../arm-linux-gnueabi/bin/ld: cannot find -lgcc | collect2: error: ld returned 1 exit status This already has been fixed before in this commit: https://git.linaro.org/openembedded/meta-linaro.git/commit/?id=91ea4d017bf0598e49944e76c889e66d58c066ce But then it got broken/undone here w/o due review: https://git.linaro.org/openembedded/meta-linaro.git/commit/?id=b43d5f0ce431ba1e242504641266a63293ded5db Even though it's a static library, we want it to be in libgcc-dev as it's not optional, but rather required for development. Signed-off-by: Denys Dmytriyenko <denys@ti.com> Reviewed-by: Sumit Garg <sumit.garg@linaro.org> Signed-off-by: Jon Mason <jon.mason@arm.com>
Introduction
This repository contains Arm layers for OpenEmbedded
meta-arm: This layer provides support for general recipes for the Arm architecture. Anything that's not needed explicitly for BSPs, the IOTA distribution, or destined to be upstreamed belongs here.
meta-arm-bsp: This layer provides support for Arm reference platforms
meta-arm-iota: This layer provides support for Arm's IOTA Linux Distribution
meta-arm-toolchain: This layer provides support for Arm's GNU-A toolset releases
meta-arm-autonomy: This layer provides a reference stack for autonomous systems.
Contributing
Currently, we only accept patches from the meta-arm mailing list. For general information on how to submit a patch, please read https://www.openembedded.org/wiki/How_to_submit_a_patch_to_OpenEmbedded
E-mail meta-arm@lists.yoctoproject.org with patches created using this process
Reporting bugs
E-mail meta-arm@lists.yoctoproject.org with the error encountered and the steps to reproduce the issue
Maintainer(s)
- Jon Mason jon.mason@arm.com