From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Giulio Benetti <giulio.benetti@benettiengineering.com>
Cc: "Jérôme Pouiller" <jezz@sysmic.org>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/apitrace: fix build failure on m68k architecture
Date: Sun, 30 Jan 2022 22:55:57 +0100 [thread overview]
Message-ID: <20220130225557.00733a9b@windsurf> (raw)
In-Reply-To: <20220129183426.152177-1-giulio.benetti@benettiengineering.com>
On Sat, 29 Jan 2022 19:34:26 +0100
Giulio Benetti <giulio.benetti@benettiengineering.com> wrote:
> apitrace uses very big switch statements, which causes the build to fail
> on m68k, because the offsets there are only 16-bit.
>
> We fix that by using -mlong-jump-table-offsets on m68k, to use 32-bit
> offsets for switch statements. That flag is available on gcc version >= 7
> but apitrace package already depends on BR2_TOOLCHAIN_GCC_AT_LEAST_7, so
> we can use it with no problem.
>
> Fixes:
> http://autobuild.buildroot.net/results/7306bf05962fec30fbe98b1eb8ee09b3162b8080/
>
> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com>
> ---
> package/apitrace/apitrace.mk | 5 +++++
> 1 file changed, 5 insertions(+)
Applied to master, thanks.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-01-30 21:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 18:34 [Buildroot] [PATCH] package/apitrace: fix build failure on m68k architecture Giulio Benetti
2022-01-30 21:55 ` Thomas Petazzoni via buildroot [this message]
2022-02-06 15:21 ` Peter Korsgaard
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=20220130225557.00733a9b@windsurf \
--to=buildroot@buildroot.org \
--cc=giulio.benetti@benettiengineering.com \
--cc=jezz@sysmic.org \
--cc=thomas.petazzoni@bootlin.com \
/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