From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 757] New: U-Boot: mkimage cannot be installed using external toolchain
Date: Wed, 2 Dec 2009 12:42:12 +0000 (UTC) [thread overview]
Message-ID: <bug-757-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=757
Host: Debian Sid
Build: 2009-12-02
Summary: U-Boot: mkimage cannot be installed using external
toolchain
Product: buildroot
Version: 2009.11
Platform: PC
OS/Version: Linux
Status: NEW
Severity: normal
Priority: P5
Component: Other
AssignedTo: unassigned at buildroot.uclibc.org
ReportedBy: anders.darander at gmail.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Created an attachment (id=789)
--> (https://bugs.busybox.net/attachment.cgi?id=789)
Patch to make sure that staging_dir/usr/bin exists before copying mkimage
When compiling buildroot using an external toolchain, the mkimage tool from
u-boot, cannot be installed into the staging area. This happens, as
$(STAGING_DIR)/usr/bin has not been created.
Attached is a patch that creates $(STAGING_DIR)/usr/bin if necessary.
Regards,
Anders Darander
--
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-12-02 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-02 12:42 bugzilla at busybox.net [this message]
2009-12-09 10:28 ` [Buildroot] [Bug 757] U-Boot: mkimage cannot be installed using external toolchain bugzilla at busybox.net
2009-12-18 7:32 ` Anders Darander
2009-12-18 7:53 ` Thomas Petazzoni
2009-12-18 8:12 ` Peter Korsgaard
2009-12-18 8:49 ` Anders Darander
2009-12-18 7:51 ` 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-757-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.