Dear krishna dwivedi,
In message
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/
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 wrote:
> Dear krishna dwivedi,
>
> please stop top posting / full quoting.
>
> In message agan2ilvqknsojcnchp3qk...@mail.gmail.com>
Dear krishna dwivedi,
please stop top posting / full quoting.
In message
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 alrea
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 ma
Dear krishna dwivedi,
In message
you wrote:
>
> Board Configuration:
>
> TargetArch CPU
> BoardName
> qemu_mipsmipsmips32 qemu-mips
This builds fine for me:
+ MAKEALL_LOGDIR=/work/wd/tmp-mips-LOG
+ BUILD_DIR=/work/wd/tmp-mip
Hi All,
Board Configuration:
TargetArch CPU
BoardName
qemu_mipsmipsmips32 qemu-mips
-
-
Options
qemu-mips
While bitbake u-boot:
Log data follows:
| DEBUG: Executing shell function do_compile
| NOTE: make -j 4 CROSS_COMPILE=mi
6 matches
Mail list logo