[U-Boot] U-boot-2012.04 compilation for qemu-mips board

Hi All,
Board Configuration:
Target Arch CPU BoardName qemu_mips mips mips32 qemu-mips - - Options qemu-mips
While bitbake u-boot:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 4 CROSS_COMPILE=mips-poky-linux- CC=mips-poky-linux-gcc --sysroot=/home/netlogic/eldk/build/tmp/sysroots/qemumips all | awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend | System not configured - see README | make: *** [all] Error 1 | ERROR: oe_runmake failed
Anyone please let me know what could be issue here.
Regards, Krishna

Dear krishna dwivedi,
In message CAKAK--n326NQLOxERi47i63qeruOAcLr=ifHeoY9Ca=X3C0zJA@mail.gmail.com you wrote:
Board Configuration:
Target Arch CPU BoardName qemu_mips mips mips32 qemu-mips
This builds fine for me:
+ MAKEALL_LOGDIR=/work/wd/tmp-mips-LOG + BUILD_DIR=/work/wd/tmp-mips + ./MAKEALL qemu_mips Configuring for qemu_mips - Board: qemu-mips, Options: SYS_BIG_ENDIAN text data bss dec hex filename 205520 7482 217512 430514 691b2 /work/wd/tmp-mips/u-boot
--------------------- SUMMARY ---------------------------- Boards compiled: 1 ----------------------------------------------------------
While bitbake u-boot:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 4 CROSS_COMPILE=mips-poky-linux- CC=mips-poky-linux-gcc --sysroot=/home/netlogic/eldk/build/tmp/sysroots/qemumips all | awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend | System not configured - see README | make: *** [all] Error 1 | ERROR: oe_runmake failed
Anyone please let me know what could be issue here.
You must run "make qemu_mips_config" before you can run "make all".
Best regards,
Wolfgang Denk

Hi Wolfgang,
I knew i have to run make qemu_mips_config before make allI am using ELDK 5.3 toolchain and compiling u-boot recipe came as a part of ELDK..But in yocto environment,we use bitbake instead of make.I already tried make: [unknown@h229 build]$ make qemu_mips_config make: *** No rule to make target `qemu_mips_config'. Stop.
I guess i need command analogous to make qemu_mips_config to run before bitbake u-boot.
Regards, Krishna
On Mon, Jul 1, 2013 at 3:31 PM, Wolfgang Denk wd@denx.de wrote:
Dear krishna dwivedi,
In message <CAKAK--n326NQLOxERi47i63qeruOAcLr=ifHeoY9Ca= X3C0zJA@mail.gmail.com> you wrote:
Board Configuration:
Target Arch CPU BoardName qemu_mips mips mips32 qemu-mips
This builds fine for me:
- MAKEALL_LOGDIR=/work/wd/tmp-mips-LOG
- BUILD_DIR=/work/wd/tmp-mips
- ./MAKEALL qemu_mips
Configuring for qemu_mips - Board: qemu-mips, Options: SYS_BIG_ENDIAN text data bss dec hex filename 205520 7482 217512 430514 691b2 /work/wd/tmp-mips/u-boot
--------------------- SUMMARY ---------------------------- Boards compiled: 1
While bitbake u-boot:
Log data follows: | DEBUG: Executing shell function do_compile | NOTE: make -j 4 CROSS_COMPILE=mips-poky-linux- CC=mips-poky-linux-gcc --sysroot=/home/netlogic/eldk/build/tmp/sysroots/qemumips all | awk '(NF && $1 !~ /^#/) { print $1 ": " $1 "_config; $(MAKE)" }' boards.cfg > .boards.depend | System not configured - see README | make: *** [all] Error 1 | ERROR: oe_runmake failed
Anyone please let me know what could be issue here.
You must run "make qemu_mips_config" before you can run "make all".
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de "The fundamental principle of science, the definition almost, is this: the sole test of the validity of any idea is experiment."
- Richard P. Feynman

Dear krishna dwivedi,
please stop top posting / full quoting.
In message CAKAK--=kZV0EebqGGmxEkHX5=aGaN2iLvQknSojCNcHP3QkHqA@mail.gmail.com you wrote:
I knew i have to run make qemu_mips_config before make allI am using ELDK 5.3 toolchain and compiling u-boot recipe came as a part of ELDK..But in yocto environment,we use bitbake instead of make.I already tried make: [unknown@h229 build]$ make qemu_mips_config make: *** No rule to make target `qemu_mips_config'. Stop.
I guess i need command analogous to make qemu_mips_config to run before bitbake u-boot.
No. You must make sure that your u-boot recipe contains the correct commands to run make qemu_mips_config first.
But this is actually a bitbake / Yocto issue, and as such off topic here.
Best regards,
Wolfgang Denk

Hi Wolfgang,
Thanks for yours valuable time and support.U-boot got compiled for qemu-mips board.
Regards, Krishna
On Mon, Jul 1, 2013 at 5:19 PM, Wolfgang Denk wd@denx.de wrote:
Dear krishna dwivedi,
please stop top posting / full quoting.
In message <CAKAK--=kZV0EebqGGmxEkHX5= aGaN2iLvQknSojCNcHP3QkHqA@mail.gmail.com> you wrote:
I knew i have to run make qemu_mips_config before make allI am using ELDK 5.3 toolchain and compiling u-boot recipe came as a part of ELDK..But in yocto environment,we use bitbake instead of make.I already tried make: [unknown@h229 build]$ make qemu_mips_config make: *** No rule to make target `qemu_mips_config'. Stop.
I guess i need command analogous to make qemu_mips_config to run before bitbake u-boot.
No. You must make sure that your u-boot recipe contains the correct commands to run make qemu_mips_config first.
But this is actually a bitbake / Yocto issue, and as such off topic here.
Best regards,
Wolfgang Denk
-- DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd@denx.de Quantum Mechanics is God's version of "Trust me."

Dear krishna dwivedi,
In message CAKAK--np_6BVQ5GRcbmvTswwhPDWeD4pb4MquofmM_xjjgjxvw@mail.gmail.com you wrote:
Thanks for yours valuable time and support.U-boot got compiled for qemu-mips board.
You really should read up on Netiquette, like [1] in general, and especially [2]
[1] http://www.catb.org/~esr/faqs/smart-questions.html [2] http://www.catb.org/~esr/faqs/smart-questions.html#followup
So far, you appear to ignore all well-meant advice you were given here as you continue to top post / full quote.
At this point, it would be appropriate if you provided an explanation what the error was, and how you fixed it.
Thanks.
Best regards,
Wolfgang Denk
participants (2)
-
krishna dwivedi
-
Wolfgang Denk