From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be>
Cc: Raul Cabello <raul.cabello@suse.com>, buildroot@buildroot.org
Subject: Re: [Buildroot] [RFC 1/2] toolchain: invert glibc <-> !static dependency
Date: Wed, 27 Jul 2022 11:24:45 +0200 [thread overview]
Message-ID: <20220727112445.07bf1a77@windsurf> (raw)
In-Reply-To: <20211006204133.465875-1-arnout@mind.be>
On Wed, 6 Oct 2021 22:41:32 +0200
"Arnout Vandecappelle (Essensium/Mind)" <arnout@mind.be> wrote:
> Currently, glibc depends on !BR2_STATIC_LIBS in all the toolchain
> variants.
>
> However, for some architectures, glibc is the only supported libc.
> Therefore, for these, it's possible to select static libs, at which
> point no libc is selectable any more.
>
> To overcome this situation, invert the dependency between glibc and
> static libs: BR2_STATIC_LIBS depends on !BR2_TOOLCHAIN_USES_GLIBC, and
> all the dependencies on !BR2_STATIC_LIBS are removed from the glibc
> variants of all toolchains.
>
> Fixes: https://bugs.busybox.net/show_bug.cgi?id=14256
>
> An alternative (simpler) fix would be to let BR2_STATIC_LIBS depend on
> !BR2_s390x. However, that doesn't solve the problem for the myriad of
> other architectures that only support glibc. In addition, there are some
> architecture variants that only support glibc, etc. etc., which really
> complicates stuff.
>
> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
I have applied this, after making sure it applies on master, since
there were conflicting changes. I rewrote most of the commit log,
because the situation in master was different than what it was when you
wrote this patch: we had already changed BR2_STATIC_LIBS to not be
selectable when the internal backend uses glibc. Your patch generalizes
this to the external toolchain backend as well.
Also, you had forgotten to adjust the gen-bootlin-toolchains script, so
I did that. And I added a Config.in comment inside the static/shared
choice that explains why static is not available.
Thanks for this!
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:[~2022-07-27 9:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-06 20:41 [Buildroot] [RFC 1/2] toolchain: invert glibc <-> !static dependency Arnout Vandecappelle (Essensium/Mind)
2021-10-06 20:41 ` [Buildroot] [RFC 2/2] Config.in: move toolchain menu before build options Arnout Vandecappelle (Essensium/Mind)
2021-11-04 20:46 ` Yann E. MORIN
2021-11-08 18:17 ` Arnout Vandecappelle
2021-10-09 20:27 ` [Buildroot] [RFC 1/2] toolchain: invert glibc <-> !static dependency Thomas Petazzoni
2022-07-27 9:24 ` 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=20220727112445.07bf1a77@windsurf \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=raul.cabello@suse.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.