From: Peter Korsgaard <jacmet@sunsite.dk>
To: buildroot@busybox.net
Subject: [Buildroot] Busybox Mips
Date: Sun, 26 Aug 2012 09:12:30 +0200 [thread overview]
Message-ID: <871uiuqg81.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CAN5RZzLe7V0Fi11tio+780D23P3NgNgoGWgHFjfWEsB_v9F7UA@mail.gmail.com> (Francisco Prado's message of "Sat, 25 Aug 2012 21:22:39 -0300")
>>>>> "Francisco" == Francisco Prado <panchopapadezoe@gmail.com> writes:
Francisco> Thanks Peter Korsgaard!!
Francisco> There's your version of buildroot 8.2011 containing the
Francisco> proper Busybox. Already compiled. In the output folder /
Francisco> build / busybox find two binaries: busybox and
Francisco> busybox_unstripped. Which one should I use?
busybox, but buildroot already copies it to your target /bin/busybox so
you don't have to copy anything manually.
Francisco> Which settings should I select for the binary function
Francisco> properly in a custom Android ROM 4.0.3? Very very thanks.
Wait, you cannot expect to take a (dynamically linked) binary from
buildroot and run it on Android. If you want to build busybox for
Android then I suggest you build it by hand using the Android cross
compiler.
You CAN do it with buildroot as well if you link statically (Build
options->prefer static libraries), but it's not really meant to be used
like that.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2012-08-26 7:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAN5RZzLtbpQ30PAgpuNj_hGF6Eia42ZvxgH3Emh3AESHU-1C=g@mail.gmail.com>
2012-08-22 23:32 ` [Buildroot] Busybox Mips Francisco Prado
2012-08-23 3:16 ` Kelvin Cheung
[not found] ` <CAN5RZzLr+vGuiVw4oRGF40bvvZ33gaxPt_LvSLBvauOmEK7PZw@mail.gmail.com>
2012-08-24 2:36 ` Kelvin Cheung
2012-08-25 19:11 ` Peter Korsgaard
[not found] ` <CAN5RZzLe7V0Fi11tio+780D23P3NgNgoGWgHFjfWEsB_v9F7UA@mail.gmail.com>
2012-08-26 7:12 ` 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=871uiuqg81.fsf@macbook.be.48ers.dk \
--to=jacmet@sunsite.dk \
--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.