what we had observed is that the Linaro gcc toolchain generated from OE (with meta-linaro) has different builtin options from the "official" binary release of gcc linaro.
e.g. if you built the OE gcc-linaro toolchain (either 4.7 with meta-linaro/dylan, or 4.8 with meta-linaro/dora), the following builtin are missing compared to the binary release:
Granted that OE is expected to have some control about CFLAGS and typically adds the right option based on the DEFAULTUNE, however it is possible for 'corner case' recipe to unset these variables, and we ended up in such a corner case.
so can we make sure that OE toolchain default to the same 'builtin configuration' as the binary gcc linaro release?
what we had observed is that the Linaro gcc toolchain generated from OE (with meta-linaro) has different builtin options from the "official" binary release of gcc linaro.
e.g. if you built the OE gcc-linaro toolchain (either 4.7 with meta-linaro/dylan, or 4.8 with meta-linaro/dora), the following builtin are missing compared to the binary release:
$ /data/gcc- linaro/ gcc-linaro- arm-linux- gnueabihf- 4.8-2013. 10_linux/ bin/arm- linux-gnueabihf -gcc -v 2>&1 | tr ' ' '\n' | grep -e arch -e fpu fpu=vfpv3- d16
--with-arch=armv7-a
--with-
Granted that OE is expected to have some control about CFLAGS and typically adds the right option based on the DEFAULTUNE, however it is possible for 'corner case' recipe to unset these variables, and we ended up in such a corner case.
so can we make sure that OE toolchain default to the same 'builtin configuration' as the binary gcc linaro release?
thanks.