Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Radu Moisan <radu.moisan@intel.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH][RFC] u-boot: Upgrade to upstream stable 2012.07
Date: Mon, 06 Aug 2012 16:40:58 +0300	[thread overview]
Message-ID: <501FC96A.8000400@intel.com> (raw)
In-Reply-To: <20120806074542.A63C0203FD8@gemini.denx.de>

[-- Attachment #1: Type: text/plain, Size: 4315 bytes --]

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@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
>


[-- Attachment #2: Type: text/html, Size: 6181 bytes --]

  reply	other threads:[~2012-08-06 13:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-03 12:38 [PATCH][RFC] u-boot: Upgrade to upstream stable 2012.07 Radu Moisan
2012-08-03 12:46 ` Martin Jansa
2012-08-03 14:45   ` Radu Moisan
2012-08-03 16:19 ` Wolfgang Denk
2012-08-06  6:28   ` Radu Moisan
2012-08-06  7:45     ` Wolfgang Denk
2012-08-06 13:40       ` Radu Moisan [this message]
2012-08-06 13:46         ` Wolfgang Denk
2012-08-06 14:09           ` Radu Moisan
2012-08-06 14:13             ` Wolfgang Denk
2012-08-07  2:58               ` Khem Raj
2012-08-07  5:50               ` Radu Moisan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=501FC96A.8000400@intel.com \
    --to=radu.moisan@intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=wd@denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox