From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch/arm: VFP and Thumb1 are not compatible
Date: Tue, 3 Nov 2015 23:50:20 +0100 [thread overview]
Message-ID: <20151103235020.20e50c91@free-electrons.com> (raw)
In-Reply-To: <1446507277-26679-1-git-send-email-yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Tue, 3 Nov 2015 00:34:37 +0100, Yann E. MORIN wrote:
> gcc will refuse to build with both --with-mode=thumb and --with-fpu=vfp,
> with error messages during ./configure, like:
>
> checking for suffix of object files... configure: error: in `/home/ymor
> in/dev/buildroot/O/build/host-gcc-initial-4.9.3/build/arm-buildroot-lin
> ux-uclibcgnueabihf/libgcc':
> configure: error: cannot compute suffix of object files: cannot compile
> See `config.log' for more details.
>
> And config.log informatively contains:
>
> sorry, unimplemented: Thumb-1 hard-float VFP ABI
>
> This is an error message that comes deep from gcc source files.
>
> If gcc says it does not support VFP with Thumb1, then let's disable that
> combination in our menuconfig.
>
> Prefer VFP over Thumb1, i.e. hide Thumb1 when we're not soft-float.
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar>
> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
> ---
> arch/Config.in.arm | 6 ++++++
> 1 file changed, 6 insertions(+)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
prev parent reply other threads:[~2015-11-03 22:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-02 23:34 [Buildroot] [PATCH] arch/arm: VFP and Thumb1 are not compatible Yann E. MORIN
2015-11-03 21:45 ` Arnout Vandecappelle
2015-11-03 22:50 ` 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=20151103235020.20e50c91@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