[ELDK] compiling u-boot/tools/env

[Marek Vasut]

On Monday, May 18, 2015 at 05:05:39 PM, K Richard Pixley wrote:
> On 5/17/15 16:27 , Anatolij Gustschin wrote:
> > On Sun, 17 May 2015 13:49:42 -0700
> > 
> > K Richard Pixley <rpixley at graphitesystems.com> wrote:
> >> Note the "HOSTCC" here is incorrect.
> >> 
> >> rpixley at victory> cd u-boot-2014.07/
> >> rpixley at victory> .
> >> /opt/eldk-5.6/powerpc-e500v2/environment-setup-ppce500v2-linux
> >> rpixley at victory> echo $CROSS_COMPILE
> >> powerpc-linux-
> >> rpixley at victory> make env CROSS_COMPILE=powerpc-linux-
> >> Makefile:516: *** "System not configured - see README".  Stop.
> >> rpixley at victory> less ../Makefile
> >> rpixley at victory> make EP2020XS_config
> >> Configuring for EP2020XS - Board: EP2020XS, Options: P2020,36BIT
> >> rpixley at victory> make env CROSS_COMPILE=powerpc-linux-
> >> 
> >>     GEN     include/autoconf.mk.dep
> >>     GEN     include/autoconf.mk
> >>     HOSTCC  scripts/basic/fixdep <--- note that HOSTCC is wrong here.
> >>     HOSTCC  tools/env/aes.o
> >> 
> >> In file included from tools/env/aes.c:1:0:
> >> tools/env/../../lib/aes.c:28:20: fatal error: string.h: No such file or
> >> directory
> >> 
> >>    #include <string.h>
> >>    
> >>                       ^
> >> 
> >> compilation terminated.
> >> make[1]: *** [tools/env/aes.o] Error 1
> >> make: *** [env] Error 2
> > 
> > This seems to be the powerpc-e500v2 toolchain issue, the path
> > /opt/eldk-5.6/powerpc-e500v2/sysroots/ppce500v2-linux/usr/include
> > is not used for #include <...> search. The toolchain was configured
> > with
> > "--with-sysroot=/opt/eldk-5.6/powerpc-e500v2/sysroots/ppce500v2-linux"
> > option, but this directory doesn't exist.
> > 
> > Please try to workaround this by creating a symlink as follows:
> >   $ cd /opt/eldk-5.6/powerpc-e500v2/sysroots
> >   $ sudo ln -s ppce500v2-linux-gnuspe ppce500v2-linux
> > 
> > Then "make env" should work.
> 
> That works for me.  Thank you.
> 
> Can we get this fixed for the next release, please?

I will try. Can someone write me a short summary so I can look into
the code please? Or a patch even ? ;-)

Best regards,
Marek Vasut