From: bugzilla at busybox.net <bugzilla@busybox.net>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 267] New: The make target: cross fails because toolchain_build_<arch>/bin/sed not found
Date: Mon, 6 Apr 2009 15:39:13 +0000 (UTC) [thread overview]
Message-ID: <bug-267-163@https.bugs.busybox.net/> (raw)
https://bugs.busybox.net/show_bug.cgi?id=267
Host: x86
Build: 2009.02
Summary: The make target: cross fails because
toolchain_build_<arch>/bin/sed not found
Product: buildroot
Version: unspecified
Platform: PC
OS/Version: Linux
Status: NEW
Severity: enhancement
Priority: P5
Component: Other
AssignedTo: dwatkins at tranzeo.com
ReportedBy: dwatkins at tranzeo.com
CC: buildroot at uclibc.org
Estimated Hours: 0.0
Note: This is from email sent to the list earlier...
http://lists.busybox.net/pipermail/buildroot/2009-April/026913.html
In the toplevel Makefile is a target 'cross' that appears to be intended
to allow you to build the cross toolchain without building everything
else. Unfortunately it doesn't work from a clean extract of the
tarball.
If you invoke 'make cross' an error happens because sed is missing.
--
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-04-06 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:39 bugzilla at busybox.net [this message]
2009-04-06 15:43 ` [Buildroot] [Bug 267] The make target: cross fails because toolchain_build_<arch>/bin/sed not found bugzilla at busybox.net
2010-02-21 22:32 ` bugzilla at busybox.net
2011-02-02 20:02 ` 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-267-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox