[OE-core] [PATCH][RFC] u-boot: Upgrade to upstream stable 2012.07

Radu Moisan radu.moisan at intel.com
Mon Aug 6 13:40:58 UTC 2012


I may be recipe configuration, however, here are my steps:

 >bitbake u-boot -c cleanall
 >bitbake u-boot -c fetch
 >bitbake -c devshell u-boot

in the new shell

 >make coreboot-x86 (without _config)

The output I got is as follows:

Configuring for coreboot-x86 - Board: coreboot, Options: 
SYS_TEXT_BASE=0xFC0000
make
/bin/bash: i386-linux-gcc: command not found
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
make[1]: Entering directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/qemux86-poky-linux/u-boot-2012.07-r0/git'
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
Generating include/autoconf.mk
/bin/bash: line 3: i386-linux-gcc: command not found
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
Generating include/autoconf.mk.dep
/bin/bash: line 3: i386-linux-gcc: command not found
make[1]: Leaving directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/qemux86-poky-linux/u-boot-2012.07-r0/git'
/bin/bash: i386-linux-gcc: command not found
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
make[1]: Entering directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/qemux86-poky-linux/u-boot-2012.07-r0/git'
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
/bin/bash: i386-linux-ld: command not found
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
/bin/bash: i386-linux-gcc: command not found
basename: missing operand
Try `basename --help' for more information.
i386-linux-gcc -DDO_DEPS_ONLY \
         -g  -Os   -ffunction-sections -fvisibility=hidden -D__KERNEL__ 
-I/home/radu/Documents/Development/yocto/build/tmp/work/qemux86-poky-linux/u-boot-2012.07-r0/git/include 
-fno-builtin -ffreestanding -nostdinc -isystem  -pipe 
-fno-strict-aliasing -Wstrict-prototypes -mregparm=3 
-fomit-frame-pointer -ffreestanding -fno-toplevel-reorder 
-fno-stack-protector  -fno-dwarf2-cfi-asm -DREALMODE_BASE=0x7c0 
-DCONFIG_X86 -D__I386__ -march=i386 -Werror -Wall -Wstrict-prototypes 
-fno-stack-protector      \
         -o lib/asm-offsets.s lib/asm-offsets.c -c -S
/bin/bash: i386-linux-gcc: command not found
make[1]: *** [lib/asm-offsets.s] Error 127
make[1]: Leaving directory 
`/home/radu/Documents/Development/yocto/build/tmp/work/qemux86-poky-linux/u-boot-2012.07-r0/git'
make: *** [coreboot-x86] Error 2

However this is the same out as when I do

 >make coreboot-x86_config
 >make all

This happens only when I'm trying to build inside the devshell, which 
lead me to believe that maybe the environment is not set completely,  
until at do_compile.

radu


On 08/06/2012 10:45 AM, Wolfgang Denk wrote:
> Dear Radu,
>
> In message <501F63FF.1070401 at intel.com> you wrote:
>>> Actually a plain
>>>
>>> 	make NAME
>>>
>>> does the same as "make NAME_config && make all".
>>>
>>> You might also consider running "./MAKEALL NAME" instead, which
>>> aut-adjusts to te number of available cores on the build host, so you
>>> get somewhat reduced build times.
>> I've tried to build this way but got into some errors and did not
>> pursued further in debugging them. However, because UBOOT_MACHINE is
> Could you please tell me exactly what these errors were?  Log files
> etc. highly appreciated...
>
> Best regards,
>
> Wolfgang Denk
>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openembedded.org/pipermail/openembedded-core/attachments/20120806/0cc256f1/attachment-0002.html>


More information about the Openembedded-core mailing list