From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Smallish rootfs for wm8505 netbook
Date: Thu, 2 May 2013 11:57:32 +0200 [thread overview]
Message-ID: <20130502115732.547b8eb2@skate> (raw)
In-Reply-To: <3759295.eBGGfacrkH@nc10>
Dear Peter Faasse,
Please do not reply to an e-mail on the list to start a new thread.
Just send a new mail to buildroot at uclibc.org. Thanks.
On Thu, 02 May 2013 09:00:49 +0200, Peter Faasse wrote:
> 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.
We decided to no longer support native development on the target
platform. If you're looking at a full-featured distribution that
provides development tools, installing a Debian armel distribution is
probably a wiser choice.
> 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.
Strange. Did you do a 'make clean; make' cycle? Can you share a
Buildroot .config that exhibits the problem?
> 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.
Yes, we know the support for toolchain on the target is broken, and
since no-one every sent patches to fix this, and because we think it's
a bit outside of the scope of the Buildroot project, we decided to
deprecate it.
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-02 9:57 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 ` [Buildroot] Smallish rootfs for wm8505 netbook Peter Faasse
2013-05-02 9:57 ` Thomas Petazzoni [this message]
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=20130502115732.547b8eb2@skate \
--to=thomas.petazzoni@free-electrons.com \
--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