Skip to contentSkip to conversation

newlib: export CC_FOR_TARGET as CC

PATCH New [email protected] 1 participant 1 message Jun 4, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 2/2 newlib: export CC_FOR_TARGET as CC

From: Alejandro Hernandez Samaniego <[email protected]>

Newlibs Makefiles use a variable CC_FOR_TARGET to build libraries for the TARGET machine (as opposed to CC_FOR_BUILD).

We pass CC on our compile function, which is normally use to build, although in this case, the configure script is trimming CC and using simply gcc for the target machine, basically taking out the TUNE variables we pass in CC as well, such as march, mfloat-abi and such. This causes errors when building applications since CC will try to use hard floating point for example whereas the libc.a from newlib will contain libraries built with the defaults which could be soft floating point for example.

e.g.:

$ ${CC} test.c
real-ld: error: test.out uses VFP register arguments,
/usr/lib/libg.a(lib_a-stdio.o) does not.

Analizing the object files we can see that one of them uses soft (library) and the other one uses hard floating point (program):

$ readelf -A test.out | grep VFP
Tag_ABI_VFP_args: VFP registers
$ readelf -A usr/lib/libc.a | grep VFP

Hence why the linker complains.

Pass CC_FOR_TARGET with the contents of CC to override the trimming from the configure script and build newlib with the correct tune.

---
 meta/recipes-core/newlib/newlib_3.1.0.bb | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)
meta/recipes-core/newlib/newlib_3.1.0.bb +2 -1
index db13724..7ab5b2b 100644
@@ -3,7 +3,8 @@ require newlib.inc
 PROVIDES += "virtual/libc virtual/libiconv virtual/libintl"
 
 do_configure() {
-	${S}/configure ${EXTRA_OECONF}
+    export CC_FOR_TARGET="${CC}"
+    ${S}/configure ${EXTRA_OECONF}
 }
 
 do_install_append() {
Signature · 1 line
2.7.4