From: Bernhard Fischer <rep.dot.nop@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Error with Busybox
Date: Wed, 28 Mar 2007 23:07:31 +0200 [thread overview]
Message-ID: <20070328210731.GE24135@aon.at> (raw)
In-Reply-To: <460A9989.6030108@mbdsys.com>
On Wed, Mar 28, 2007 at 06:36:25PM +0200, kimtuan wrote:
>Hello,
>
>I'm trying to build with Busybox but I can't find out why I got this
>building error :
>
>/home/kimtuan/work/buildroot/build_arm/staging_dir/bin/arm-linux-uclibc-strip:
>'busybox_unstripped': No such file
>install: cannot stat `busybox': No such file or directory
>make[1]: *** [install] Error 1
>make[1]: Leaving directory
>`/home/kimtuan/work/buildroot/build_arm/busybox-1.5.0'
>make: *** [/home/kimtuan/work/buildroot/build_arm/root/bin/busybox] Error 2
$ make busybox-clean
$ make
or, for more verbose output
$ make V=1
and show us the first error you are getting
next prev parent reply other threads:[~2007-03-28 21:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-28 16:36 [Buildroot] Error with Busybox kimtuan
2007-03-28 21:07 ` Bernhard Fischer [this message]
[not found] ` <460B80C7.5040804@mbdsys.com>
2007-03-29 10:34 ` Bernhard Fischer
2007-03-31 3:17 ` David Lambert
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=20070328210731.GE24135@aon.at \
--to=rep.dot.nop@gmail.com \
--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