From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Bernd Kuhls <bernd@kuhls.net>
Cc: Eric Le Bihan <eric.le.bihan.dev@free.fr>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] package/pkg-meson.mk: disable staticpic on Coldfire
Date: Mon, 10 Jul 2023 20:39:28 +0200 [thread overview]
Message-ID: <20230710203928.66108038@windsurf> (raw)
In-Reply-To: <20230618183105.2474342-1-bernd@kuhls.net>
On Sun, 18 Jun 2023 20:31:04 +0200
Bernd Kuhls <bernd@kuhls.net> wrote:
> Fixes build error in the upcoming libdisplay-info package:
> "Tried to convert PC relative branch to absolute jump" as described
> here: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=101971#c11
>
> Since this issue not only occurs with this package, see
> https://git.busybox.net/buildroot/commit/?id=2a48a6ee9d6b81c804182ff0ad6e0f7c850f6839
> we add the configure option to pkg-meson.mk.
>
> Signed-off-by: Bernd Kuhls <bernd@kuhls.net>
> ---
> Suggested by Yann:
> https://lists.buildroot.org/pipermail/buildroot/2023-June/669138.html
I've applied both patches. I'm not a huge fan of the conditions on
BR2_m68k_cf. I would prefer to have some better hidden options such as
BR2_ARCH_SUPPORTS_STATIC_PIC or something like that, with a clear
understanding of which platforms support it and don't support it. But
oh well, I don't know if putting too much effort into Coldfire is
really worth the trouble...
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
prev parent reply other threads:[~2023-07-10 18:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-18 18:31 [Buildroot] [PATCH 1/2] package/pkg-meson.mk: disable staticpic on Coldfire Bernd Kuhls
2023-06-18 18:31 ` [Buildroot] [PATCH v2 2/2] package/libdisplay-info: new package Bernd Kuhls
2023-07-10 18:39 ` Thomas Petazzoni via buildroot [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=20230710203928.66108038@windsurf \
--to=buildroot@buildroot.org \
--cc=bernd@kuhls.net \
--cc=eric.le.bihan.dev@free.fr \
--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