From: Peter Faasse <p.faase1@chello.nl>
To: buildroot@busybox.net
Subject: [Buildroot] Smallish rootfs for wm8505 netbook
Date: Thu, 02 May 2013 09:00:49 +0200 [thread overview]
Message-ID: <3759295.eBGGfacrkH@nc10> (raw)
In-Reply-To: <82bbf577-2fa7-4161-aa47-e18b223fc7be@CO9EHSMHS011.ehs.local>
Hi,
With varying degrees of success, i've been building buildroot based rootfs-s,
toolchains and kernel images. All part of a hacking project with a few wm8505
(armv5) based netbooks.
I'm attempting to use buildroot to build a rootfs & kernel that i can use to
do some native development on the machines. The first set of bugs where no
doubt caused by my own incompetence and learning curve, but there are one or
two issues that i think are relevent for a wider audience.
For reference, the target architecture is arm926t; Host is a Slackware-13.37
x86_64 machine; I'been using both the 2013.02 release of buildroot and the
git-version as extracted yesterday. I let buildroot itself generate the
toolchain (no croostool-ng etc..). I did manage to generate a few working
toolchains, kernel uImages and rootfs.tar images, and i'm in the process of
generating a fully satisfactory set of target files. But:
1) If i enable c++ support the toolchain, the build of the rootfs will fail
because of a lack of UCLIBC_HAS_FENV (fenv.h not found). This can easily be
remedied using make uclibc-menuconfig after configuring buildroot ('Target
Architecture Features and Options'-->'Enable C99 Floating-point environment'),
but i think it would make sense if that option is -if possible- automatically
enabled by activating this uclibc option when c++ support is enabled in
buildroot itself.
2) I do include the obsolete 'toolchain on the target'. The resulting gcc on-
target is by default not usable because glibc.so (a linker script it seems) is
not copied to the on-target directory. This can be remedied by adding *.so to
the support/scripts/copy.sh, but i'm not quite sure if that has any side-
effects.
All-in-all i'm having lots of fun with buildroot... :-)
greetings,
Peter Faasse
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20130502/ff2ac27c/attachment.asc>
next prev parent reply other threads:[~2013-05-02 7:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-01 22:03 [Buildroot] Buildroot + CoudeSourcery 2012.09 Sören Brinkmann
2013-05-02 7:00 ` Peter Faasse [this message]
2013-05-02 9:57 ` [Buildroot] Smallish rootfs for wm8505 netbook Thomas Petazzoni
2013-05-02 9:53 ` [Buildroot] Buildroot + CoudeSourcery 2012.09 Thomas Petazzoni
2013-05-02 16:02 ` Sören Brinkmann
2013-05-02 16:39 ` 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=3759295.eBGGfacrkH@nc10 \
--to=p.faase1@chello.nl \
--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