From: bifferos <bifferos@yahoo.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] Kernel and buildroot in 1MB
Date: Thu, 01 Mar 2012 00:52:12 +0000 [thread overview]
Message-ID: <4F4EC83C.7090208@yahoo.co.uk> (raw)
Hi,
So far I have been using buildroot only to extract the busybox binary
and use it with my own hand-crafted rootfs, because pretty much any
binaries other than busybox put me over the limit. It would be nice to
use the buildroot filesystem as generated, so my question is this: If I
build a busybox statically linked to uclibc, how can I remove *all* the
other binaries, e.g. uclibc .so? Or does the build system not support that?
I'm sorry if I've missed some obvious option(s) to do this, but I've
been studying the menu system for some time.
thanks,
Biff.
next reply other threads:[~2012-03-01 0:52 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-01 0:52 bifferos [this message]
2012-03-01 7:50 ` [Buildroot] Kernel and buildroot in 1MB Thomas Petazzoni
2012-03-01 11:13 ` bifferos
2012-03-03 15:29 ` Arnout Vandecappelle
2012-03-03 15:35 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-05 9:49 ` Thomas Petazzoni
2012-03-06 7:00 ` Arnout Vandecappelle
2012-03-11 10:58 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
2012-03-12 14:46 ` bifferos
2012-03-12 1:23 ` [Buildroot] [PATCH] " bifferos
2012-03-16 1:58 ` [Buildroot] Debugging /sbin/init startup issues bifferos
2012-03-17 4:03 ` Charles Krinke
2012-03-17 14:10 ` bifferos
2012-03-18 13:50 ` [Buildroot] [PATCH] bifferboard: new board Arnout Vandecappelle
2012-03-18 16:12 ` bifferos
2012-03-18 17:13 ` Arnout Vandecappelle
2012-03-18 19:51 ` Alexandre Pereira da Silva
2012-03-18 20:54 ` bifferos
2012-03-18 21:40 ` Arnout Vandecappelle
2012-03-19 12:36 ` bifferos
[not found] ` <4F525794.5010406@yahoo.co.uk>
2012-03-03 17:00 ` [Buildroot] Kernel and buildroot in 1MB Arnout Vandecappelle
2012-03-01 12:18 ` Peter Korsgaard
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=4F4EC83C.7090208@yahoo.co.uk \
--to=bifferos@yahoo.co.uk \
--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