From: Adam Nielsen <a.nielsen@shikadi.net>
To: buildroot@busybox.net
Subject: [Buildroot] initramfs doesn't get linked into kernel
Date: Sat, 04 May 2013 21:35:09 +1000 [thread overview]
Message-ID: <km2rp9$jgd$1@ger.gmane.org> (raw)
In-Reply-To: <20130504102552.03b360ae@skate>
> I think the elf2flt stuff hasn't been used in a while, so it isn't very
> surprising that it is broken. Your patches are definitely welcome to
> fix it, and once it's fixed, I'll add a new toolchain configuration in
> our autobuilders to test this configuration on a regular basis.
I'm happy to do my best to try to fix this, but I'm afraid I might need a
little help as I'm not too familiar with buildroot.
I have worked out this so far:
- In order to enable FLAT binaries, you need to disable MMU support in
uClibc. Deselecting the buildroot option BR2_USE_MMU does not change the
uClibc option. I am guessing this should happen automatically, but not quite
sure how to achieve it.
- Disabling MMU support in uClibc stops the thread components from
compiling. Apparently this is a bug in uClibc? (something about fork() being
called vfork() instead)
- Disabling threads entirely in both uClibc and buildroot gets past that
previous problem, but gcc-final then does not compile as some components
(libitm and libatomic) need thread support. I am not sure how to tell
buildroot to ask GCC to skip compiling libitm and libatomic when thread
support has been disabled.
Any tips on this would be much appreciated!
Many thanks,
Adam.
next prev parent reply other threads:[~2013-05-04 11:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-26 23:37 [Buildroot] initramfs doesn't get linked into kernel Adam Nielsen
2013-04-27 1:17 ` Thomas Petazzoni
2013-04-27 9:53 ` Adam Nielsen
2013-04-27 17:34 ` Thomas Petazzoni
2013-04-27 22:50 ` Adam Nielsen
2013-05-04 0:29 ` Adam Nielsen
2013-05-04 8:25 ` Thomas Petazzoni
2013-05-04 11:35 ` Adam Nielsen [this message]
2013-05-04 17:36 ` Thomas Petazzoni
2013-05-05 1:47 ` Adam Nielsen
2013-05-05 2:11 ` Adam Nielsen
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='km2rp9$jgd$1@ger.gmane.org' \
--to=a.nielsen@shikadi.net \
--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