I'm still trying to get the external-linaro-toolchain going in master after
all the recent changes...
First of all, I'm seeing these:
ERROR: external-linaro-toolchain-2017.02-r0.arago35 do_install: oe_multilib_header: Unable to find header bits/long-double.h.
ERROR: external-linaro-toolchain-2017.02-r0.arago35 do_install: oe_multilib_header: Unable to find header bits/fp-fast.h.
They are coming from these changes:
http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-core/gli…http://cgit.openembedded.org/openembedded-core/commit/meta/recipes-core/gli…
I believe (please correct me) those are due to Linaro toolchain 6.3 still
using glibc 2.23...
But the real problem comes when I try to build gcc (either "linaro-6.3" from
meta-linaro-toolchain, or "6.3" from oe-core) for the target using
external-linaro-toolchain:
| g++: error: gengtype-lex.c: No such file or directory
| g++: fatal error: no input files
It seems to come from oe-core gcc-source.inc, which removes gengtype-lex.c in
order to re-generate it:
http://cgit.openembedded.org/openembedded-core/tree/meta/recipes-devtools/g…
Has anyone looked into fixing these issues? What's the status of
external-linaro-toolchain in master? Will this be looked at for 6.3 version,
or not until 7.x gets integrated? Thanks.
--
Denys
From: Denys Dmytriyenko <denys(a)ti.com>
When OE-Core updated binutils to version 2.28, many of the patches got updated
and renamed:
http://cgit.openembedded.org/openembedded-core/commit/?id=e9f839d5fe70a222c…
Most of those do not affect binutils recipes in meta-linaro-toolchain, as patches
are listed in version-specific .bb and .inc files for 2.25 and 2.27.
But binutils-cross.inc is one of the generic common .inc files in OE-Core, that
includes a patch that got renamed. Sync up this one patch with OE-Core to avoid
these warnings:
WARNING: /OE/master/sources/meta-linaro/meta-linaro-toolchain/recipes-devtools/binutils/binutils-crosssdk_linaro-2.25.bb: Unable to get checksum for binutils-crosssdk-x86_64-arago-linux SRC_URI entry 0002-binutils-cross-Do-not-generate-linker-script-directo.patch: file could not be found
WARNING: /OE/master/sources/meta-linaro/meta-linaro-toolchain/recipes-devtools/binutils/binutils-cross_linaro-2.25.bb: Unable to get checksum for binutils-cross-arm SRC_URI entry 0002-binutils-cross-Do-not-generate-linker-script-directo.patch: file could not be found
Signed-off-by: Denys Dmytriyenko <denys(a)ti.com>
---
...ss-Do-not-generate-linker-script-directo.patch} | 26 +++++++++++++++++-----
1 file changed, 20 insertions(+), 6 deletions(-)
rename meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/{no-tooldirpaths.patch => 0002-binutils-cross-Do-not-generate-linker-script-directo.patch} (75%)
diff --git a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/no-tooldirpaths.patch b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/0002-binutils-cross-Do-not-generate-linker-script-directo.patch
similarity index 75%
rename from meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/no-tooldirpaths.patch
rename to meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/0002-binutils-cross-Do-not-generate-linker-script-directo.patch
index 2bfc8d4..14299fd 100644
--- a/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/no-tooldirpaths.patch
+++ b/meta-linaro-toolchain/recipes-devtools/binutils/binutils-linaro-2.25/0002-binutils-cross-Do-not-generate-linker-script-directo.patch
@@ -1,20 +1,31 @@
+From 7c7de107b4b0a507d2aeca3e3a86d01cb4b51360 Mon Sep 17 00:00:00 2001
+From: Khem Raj <raj.khem(a)gmail.com>
+Date: Mon, 6 Mar 2017 23:37:05 -0800
+Subject: [PATCH 02/15] binutils-cross: Do not generate linker script
+ directories
+
We don't place target libraries within ${exec_prefix}, we'd always place these
within the target sysroot within the standard library directories. Worse, the
append_to_lib_path code prefixes these paths with the sysroot which makes even
less sense.
-These directories therefore don't make sense in our case and mean we have to
-relocate all the linker scripts if they're present. Dropping them
+These directories therefore don't make sense in our case and mean we have to
+relocate all the linker scripts if they're present. Dropping them
gives a reasonable performance improvement/simplification.
Upstream-Status: Inappropriate
RP 2017/01/30
-Index: git/ld/genscripts.sh
-===================================================================
---- git.orig/ld/genscripts.sh
-+++ git/ld/genscripts.sh
+Signed-off-by: Khem Raj <raj.khem(a)gmail.com>
+---
+ ld/genscripts.sh | 23 -----------------------
+ 1 file changed, 23 deletions(-)
+
+diff --git a/ld/genscripts.sh b/ld/genscripts.sh
+index a42c4d7a4b..d727b4d07e 100755
+--- a/ld/genscripts.sh
++++ b/ld/genscripts.sh
@@ -189,29 +189,6 @@ append_to_lib_path()
fi
}
@@ -45,3 +56,6 @@ Index: git/ld/genscripts.sh
if [ "x${LIB_PATH}" = "x" ] && [ "x${USE_LIBPATH}" = xyes ] ; then
libs=${NATIVE_LIB_DIRS}
if [ "x${NATIVE}" = "xyes" ] ; then
+--
+2.12.0
+
--
2.7.4
not sure if this is the right list to point out oddities in the
documentation, but i'm reading this:
https://www.96boards.org/db410c-getting-started/HardwareDocs/HWUserManual.m…
and in the ToC, under "Low Speed Expansion Connector", there is no
mention of I2S, but in the very next section, "Introduction", under
"I/O Interfaces", one reads:
One 40-pin Low Speed (LS) expansion connector
UART, SPI, I2S, I2C x2, GPIO x12, DC power
^^^
should I2S be added to the ToC for consistency? or am i misreading
something?
rday
--
========================================================================
Robert P. J. Day Ottawa, Ontario, CANADA
http://crashcourse.ca
Twitter: http://twitter.com/rpjday
LinkedIn: http://ca.linkedin.com/in/rpjday
========================================================================