From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3] sh4: fix toolchain creation
Date: Sun, 3 May 2015 16:31:52 +0200 [thread overview]
Message-ID: <20150503163152.68499cac@free-electrons.com> (raw)
In-Reply-To: <20150408085455.GA26812@waldemar-brodkorb.de>
Dear Waldemar Brodkorb,
On Wed, 8 Apr 2015 10:54:55 +0200, Waldemar Brodkorb wrote:
> The Linux kernel does force compile with -m4-nofpu, which is only
> available when building a multilib toolchain.
> The interesting part here is, that buildroot use --disable-multilib for
> gcc configure, but enables --with-multilib-list=m4,m4-nofpu in
> the default configuration for Qemu targeting r2d emulation.
> This results in a toolchain, which can be used for the kernel and
> for userland without creating a multilib toolchain with different
> kinds of libgcc version. In the multilib case there would be
> subdirectories created (!m4 and m4-nofpu). As buildroot uses a
> short version of toolchain creation, a multilib enabled gcc build
> fails when creating libgcc.
>
> So the best solution is to just keep multilib disabled, but always
> add --with-multilib-list when sh4/sh4eb/sh4a/sh4aeb is choosen.
>
> Tested with sh4/sh4a toolchain build and qemu defconfig with
> gcc 4.8.x/4.9.x (with and without C++ enabled), uClibc and glibc.
>
> Disable sh4a/sh4aeb for uClibc, as it does not implemented, yet.
>
> Signed-off-by: Waldemar Brodkorb <wbx@openadk.org>
> ---
> Changes v3:
> - add local variable for complete directory as suggested by Thomas Pettazoni
> - disable sh4a/sh4aeb for uClibc as suggested by Thomas Pettazoni
Applied, thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-05-03 14:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-08 8:54 [Buildroot] [PATCH v3] sh4: fix toolchain creation Waldemar Brodkorb
2015-05-03 14:31 ` Thomas Petazzoni [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=20150503163152.68499cac@free-electrons.com \
--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