From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/3] busybox: set/unset CONFIG_NOMMU
Date: Sat, 10 Aug 2013 08:12:43 -0300 [thread overview]
Message-ID: <5206202B.5000603@zacarias.com.ar> (raw)
In-Reply-To: <CAFRkauBPLBDR+7m7WHA0wo_NkJjN4VRQp1Jzp2tL8q6hTqC+tQ@mail.gmail.com>
On 08/09/2013 11:08 PM, Axel Lin wrote:
> Hi Gustavo,
>
> I try to build for noMMU with below patches:
> [PATCH 1/3] busybox: set/unset CONFIG_NOMMU
> [PATCH 2/3] uclibc: set MMU usage accordingly
>
> However, I still got ELF executable:
> $ file output/target/bin/busybox
> output/target/bin/busybox: setuid ELF 32-bit LSB executable, ARM,
> version 1 (SYSV), statically linked, stripped
Hi Axel.
It's not ready, these are patches just to fix obvious problems.
More will possibly follow unless unless i get pissed off by your
continuous one bit comments.
I already know it's still doing ELF binaries - the toolchain isn't
configured appropiately and without hardware finding the exact way of
doing so isn't easy (seems very likely that it'll require gcc patching).
Thanks and regards.
next prev parent reply other threads:[~2013-08-10 11:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-09 19:23 [Buildroot] [PATCH 1/3] busybox: set/unset CONFIG_NOMMU Gustavo Zacarias
2013-08-09 19:23 ` [Buildroot] [PATCH 2/3] uclibc: set MMU usage accordingly Gustavo Zacarias
2013-08-09 19:23 ` [Buildroot] [PATCH 3/3] eglibc: needs MMU Gustavo Zacarias
2013-08-10 2:08 ` [Buildroot] [PATCH 1/3] busybox: set/unset CONFIG_NOMMU Axel Lin
2013-08-10 11:12 ` Gustavo Zacarias [this message]
2013-08-10 19:26 ` Thomas Petazzoni
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=5206202B.5000603@zacarias.com.ar \
--to=gustavo@zacarias.com.ar \
--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