From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] Building for Raspberry Pi on Pi (in Ubuntu WSL same is working)
Date: Tue, 25 Aug 2020 10:17:09 +0200 [thread overview]
Message-ID: <20200825101709.770f2520@windsurf.home> (raw)
In-Reply-To: <VI1PR03MB45286F7ECB71FC95DB6A282798570@VI1PR03MB4528.eurprd03.prod.outlook.com>
Hello,
On Tue, 25 Aug 2020 07:56:18 +0000
Marie Maurer <marie.maurer@pixida.de> wrote:
> Perhaps this parameter:
>
> --with-arch=armv6
Yes, the problem is that the compiler provided in your Raspbian
distribution generates ARMv6 code by default, I guess to be compatible
with all RaspberryPi. But you're running on an ARMv7 RaspberryPi, so
GMP believes it can enable some ARMv6T2 optimizations... which are then
not recognized by your compiler.
I am not sure what is the correct way to fix this:
- Should we consider it a bug that the host compiler you have
installed does not by default generate binaries that match your host
CPU architecture ?
- Should we consider it a bug that GMP assumes without testing the
compiler that the host CPU architecture detected at runtime is
really supported by the compiler ?
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2020-08-25 8:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 14:09 [Buildroot] Building for Raspberry Pi on Pi (in Ubuntu WSL same is working) Marie Maurer
2020-08-24 17:40 ` Aaron Dewes
2020-08-24 20:19 ` Thomas Petazzoni
2020-08-25 7:18 ` Marie Maurer
2020-08-25 7:26 ` Marie Maurer
2020-08-25 7:33 ` Thomas Petazzoni
2020-08-25 7:43 ` Marie Maurer
2020-08-25 7:49 ` Thomas Petazzoni
2020-08-25 7:53 ` Marie Maurer
2020-08-25 7:56 ` Marie Maurer
2020-08-25 8:17 ` 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=20200825101709.770f2520@windsurf.home \
--to=thomas.petazzoni@bootlin.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