From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Missing binaries
Date: Tue, 16 Sep 2008 22:42:30 +0200 [thread overview]
Message-ID: <8763ov6cw9.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1221137619.9222.1.camel@tim-desktop> (maleadt@gmail.com's message of "Thu\, 11 Sep 2008 14\:53\:39 +0200")
>>>>> "MALEADt" == MALEADt <maleadt@gmail.com> writes:
MALEADt> Hi,
MALEADt> I have been working with buildroot lately, and every time I created a
MALEADt> toolchain, several binaries seemed to be missing. These binaries
MALEADt> included: tar, xargs, sed, mount & umount.
MALEADt> As it seems, these binaries all get properly compiled, but just not
MALEADt> included in the final filesystem. I only needed to copy them from the
MALEADt> somewhere in the build_xxx folder, to the toolchain.
MALEADt> Is this a problem of mine, or is anybody else experiencing
MALEADt> this problem?
I cannot seem to reproduce this - Are you by any chance using Ubuntu
and/or using dash as shell? Maybe it has issues with the shell tests
(E.G. findutils.mk:58)
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2008-09-16 20:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-11 12:53 [Buildroot] Missing binaries MALEADt
2008-09-16 20:42 ` Peter Korsgaard [this message]
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=8763ov6cw9.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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