Hi Alejandro, On 11/12/18 23:00, Alejandro Enedino Hernandez Samaniego wrote: > Hey Luca, > > > On 12/11/2018 07:42 AM, Luca Ceresoli wrote: >> Hi Alejandro, >> >> On 06/12/18 22:56, Alejandro Enedino Hernandez Samaniego wrote: >>> Signed-off-by: Alejandro Enedino Hernandez Samaniego >>> <aleja...@xilinx.com> >>> Signed-off-by: Manjukumar Matha <manjukumar.harthikote-ma...@xilinx.com> >>> --- >>> .../recipes-standalone/gcc/gcc-cross_%.bbappend | 17 >>> +++++++++++++++++ >>> 1 file changed, 17 insertions(+) >>> create mode 100644 >>> meta-xilinx-standalone/recipes-standalone/gcc/gcc-cross_%.bbappend >>> >>> diff --git >>> a/meta-xilinx-standalone/recipes-standalone/gcc/gcc-cross_%.bbappend >>> b/meta-xilinx-standalone/recipes-standalone/gcc/gcc-cross_%.bbappend >>> new file mode 100644 >>> index 0000000..13ae02a >>> --- /dev/null >>> +++ b/meta-xilinx-standalone/recipes-standalone/gcc/gcc-cross_%.bbappend >>> @@ -0,0 +1,17 @@ >>> +# By using tclibc-baremetal we loose sysroot functionality due to >>> some append/override behavior >>> +# We need to get that back , the following append overrides >>> everything on EXTRA_OECONF for gcc cross target >>> +# it avoids overlapping with crt0 because of --enable-linker-id from >>> EXTRA_OECONF > > Since we are cross compiling using Yocto, and it was designed to build a > Linux OS, some assumptions are made by default, with the addition of > TCLIBC=newlib (or baremetal in any case), we get rid of those > assumptions, and in the process we get rid of the default configuration > parameters, the problem is that we only want to get rid of a few, so > basically we want to get the ones that we want back from the defaults.
Thanks, it's much clearer now. You might add part of this explanation as a comment in that file to help future readers. -- Luca -- _______________________________________________ meta-xilinx mailing list meta-xilinx@yoctoproject.org https://lists.yoctoproject.org/listinfo/meta-xilinx
