[ELDK] eldk-5.5.2 issues

Marek Vasut marex at denx.de
Sat Oct 25 16:31:50 CEST 2014


On Saturday, October 25, 2014 at 01:04:08 PM, Pavel Machek wrote:
> Hi!
> 
> On Fri 2014-10-24 12:02:21, Wolfgang Denk wrote:
> > In message <20141023145122.GA10650 at amd> you wrote:
> > > Eldk-5.5 seems to miscompile u-boot on altera socfpga (arm board), so
> > > I tried updating to eldk-5.5.2... but I ran into problems compiling
> > > u-boot-mkimage.
> > 
> > The compilers used in ELDK V5.5 and v5.5.x (and even v5.6) have known
> > issues at least on the PowerPC and ARM architectures;  the ARM kernel
> > might even blacklist it, see [1].
> > 
> > So I doubt your problems will go away when moving from ELDK v5.5 to
> > v5.5.2; if you cannot fall back to ELDK v5.4 (gcc 4.7.2) you will have
> > to wait for ELDk v5.7 (gcc 4.9.1).
> 
> I did not manage to switch to v5.5.2, but it seems that ELDK v5.5
> contains fully working gcc-4.7 toolchain.
> 
> As they are known problems with gcc-4.8, perhaps it makes sense to
> merge something like below for eldk v5.5.3 (and maybe eldk v5.6)?
> 
> Signed-off-by: Pavel Machek <pavel at denx.de>
> 
> Best regards,
> 									Pavel
> 
> 
> diff --git a/meta/conf/distro/include/tcmode-default.inc
> b/meta/conf/distro/include/tcmode-default.inc index fb41d5e..df90219
> 100644
> --- a/meta/conf/distro/include/tcmode-default.inc
> +++ b/meta/conf/distro/include/tcmode-default.inc
> @@ -17,7 +17,7 @@ PREFERRED_PROVIDER_virtual/${TARGET_PREFIX}libc-initial =
> "${TCLIBC}-initial"
> PREFERRED_PROVIDER_virtual/nativesdk-${SDK_PREFIX}libc-initial =
> "nativesdk-${TCLIBC}-initial" PREFERRED_PROVIDER_virtual/gettext ??=
> "gettext"
> 
> -GCCVERSION ?= "4.8%"
> +GCCVERSION ?= "4.7%"
>  SDKGCCVERSION ?= "${GCCVERSION}"
>  BINUVERSION ?= "2.23.2"
>  EGLIBCVERSION ?= "2.18"

You (as a layer provider) should never hack meta/ . If you need to override 
something, then such override should go into the meta-foo/ layer, which you
generated (meta-eldk in this case). Though I disagree that downgrading the
GCC version is a good way to go.

Do we already know what's the stance of the Yocto guys on the GCC 4.8.x problem?

Best regards,
Marek Vasut


More information about the eldk mailing list