<div dir="ltr">It's in my staging branch and works for me, just needs a run through the AB and then a decision on whether it is a bug fix (good for M4) or enhancement (too late for M3)...<div><br></div><div>Ross</div></div><div class="gmail_extra"><br><div class="gmail_quote">On 12 September 2016 at 16:19, Jérémy Rosen <span dir="ltr"><<a href="mailto:jeremy.rosen@smile.fr" target="_blank">jeremy.rosen@smile.fr</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Any news ?<div class="HOEnZb"><div class="h5"><br>
<br>
<br>
On 07/09/2016 11:08, Jérémy Rosen wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
The BUILD_* family of variables allow the user to specify the name of the host<br>
compiler to use at build time. This feature is particularly important for long<br>
term maintainance. Future versions of gcc might not be compatible with old<br>
yocto distributions and we can't assume that "gcc" is the correct name for the<br>
compiler.<br>
<br>
This problem is already an issue with Jethro which can't be compiled on a<br>
machine wher gcc-6 is the default compiler. pkgconfig-native will refuse to<br>
compile because it uses -Werror and gcc-6 has new warnings compared to gcc-5<br>
<br>
This patch serie fixes multiple hard-coded references to gcc in various recipes<br>
and build infrastructure<br>
<br>
This patch was tested by building core-image-minimal for qemu-x86_64 with a<br>
directory with the following content added to the PATH<br>
<br>
g++ -> /bin/false<br>
gcc -> /bin/false<br>
myg++ -> /usr/bin/g++<br>
mygcc -> /usr/bin/gcc<br>
<br>
And the following variables added to local.conf<br>
<br>
export BUILD_CC = "mygcc"<br>
export BUILD_CXX = "myg++"<br>
export BUILD_CPP = "mygcc -E"<br>
export BUILD_CCLD = "mygcc"<br>
<br>
---<br>
V2<br>
* rewording in some commits messages<br>
* no need for a patch to KConfig, use OE_RUNMAKE_FLAGS instead<br>
* change all patch titles to use : in the short commit message<br>
* rpm : manually remove files instead of calling make distclean<br>
* libpcre : explicitely set CCLD_FOR_BUILD in the recipe since it's the only<br>
recipe using it.<br>
* glibc patch has been submited upstream<br>
<br>
It would be interesting to modify yocto's builders to use the BUILD_*<br>
variable in order to have some early warning wrt gcc polution in recipes, but<br>
seeing the various recipes I had to patch, I would expect such a change to<br>
trigger a high number of build failures.<br>
<br>
Jérémy Rosen (8):<br>
cross: export CC family from BUILD_* for cross compilers<br>
linux-yocto: allow overriding compiler name in KConfig<br>
linux-libc-headers: allow overriding compiler name in KConfig<br>
busybox: allow overriding compiler name in KConfig<br>
sanity: fix hardcoded references to gcc<br>
glibc: remove hard-coded reference to gcc -E<br>
rpm: manually cleanup sysck<br>
libpcre: explicitely specify CCLD_FOR_BUILD for this recipe<br>
<br>
meta/classes/cross.bbclass | 12 ++++++++++++<br>
meta/classes/kernel.bbclass | 1 +<br>
meta/classes/sanity.bbclass | 14 +++++++-------<br>
meta/recipes-core/busybox/busy<wbr>box.inc | 2 +-<br>
meta/recipes-core/glibc/glibc/<wbr>0001-locale-fix-hard-coded-ref<wbr>erence-to-gcc-E.patch | 39 ++++++++++++++++++++++++++++++<wbr>+++++++++<br>
meta/recipes-core/glibc/<a href="http://glibc_2.24.bb" rel="noreferrer" target="_blank">glibc_<wbr>2.24.bb</a> | 3 ++-<br>
meta/recipes-devtools/rpm/<a href="http://rpm_5.4.16.bb" rel="noreferrer" target="_blank">rpm_<wbr>5.4.16.bb</a> | 2 +-<br>
meta/recipes-kernel/linux-libc<wbr>-headers/linux-libc-headers.<wbr>inc | 2 ++<br>
meta/recipes-support/libpcre/<a href="http://libpcre_8.39.bb" rel="noreferrer" target="_blank">l<wbr>ibpcre_8.39.bb</a> | 2 ++<br>
9 files changed, 67 insertions(+), 10 deletions(-)<br>
create mode 100644 meta/recipes-core/glibc/glibc/<wbr>0001-locale-fix-hard-coded-ref<wbr>erence-to-gcc-E.patch<br>
<br>
</blockquote>
<br>
-- <br></div></div><div class="HOEnZb"><div class="h5">
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</div></div></blockquote></div><br></div>