From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 475] New: uImage target for U-boot failed generating
Date: Tue, 21 Jul 2009 11:02:58 +0000 (UTC) [thread overview]
Message-ID: <bug-475-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=475
Host: i386-pc-linux-gnu
Target: powerpc-unknown-linux-gnu
Build: i386-pc-linux-gnu
Summary: uImage target for U-boot failed generating
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Windows
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: etienne_lorrain at yahoo.fr
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=487)
--> (https://bugs.busybox.net/attachment.cgi?id=487)
all config leading to the error
BOOTCC arch/powerpc/boot/fdt_rw.o
BOOTCC arch/powerpc/boot/fdt_strerror.o
BOOTAR arch/powerpc/boot/wrapper.a
WRAP arch/powerpc/boot/uImage
/home/elorrain/buildroot/project_build_powerpc/Eqam4G/linux-2.6.30.2/arch/powerpc/boot/wrapper:
line 261: mkimage: command not found
make[2]: *** [arch/powerpc/boot/uImage] Error 127
make[1]: *** [uImage] Error 2
make[1]: Leaving directory
`/home/elorrain/buildroot/project_build_powerpc/Eqam4G/linux-2.6.30.2'
make: *** [/home/elorrain/buildroot/binaries/Eqam4G/uImage] Error 2
--
Configure bugmail: https://bugs.busybox.net/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
next reply other threads:[~2009-07-21 11:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-21 11:02 bugzilla at busybox.net [this message]
2010-02-21 22:32 ` [Buildroot] [Bug 475] uImage target for U-boot failed generating bugzilla at busybox.net
2010-06-07 20:40 ` bugzilla at busybox.net
2010-07-15 9:23 ` bugzilla at busybox.net
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=bug-475-163@https.bugs.busybox.net/ \
--to=bugzilla@busybox.net \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.