From: Fiona Klute via buildroot <buildroot@buildroot.org>
To: Arnout Vandecappelle <arnout@mind.be>, yann.morin@orange.com
Cc: buildroot@buildroot.org, Thomas Perale <thomas.perale@mind.be>,
Christian Stewart <christian@aperture.us>
Subject: Re: [Buildroot] [PATCH 1/1] package/go/go-src: stop forcing binutils-gold dependency on aarch64
Date: Tue, 4 Feb 2025 15:46:49 +0100 [thread overview]
Message-ID: <07211c56-9048-4ed6-9aae-deec6587eef6@gmx.de> (raw)
In-Reply-To: <ee3662e1-3fbf-4a96-addd-b9d748e2a1c8@mind.be>
Hi Arnout!
Am 04.02.25 um 12:27 schrieb Arnout Vandecappelle:
[... snip ...]
>> One question though: Is there an existing way to check the Binutils
>> version of an external toolchain? For people with Binutils < 2.41 with
>
> The commit message of Yann's patch says "This is supposedly fixed in
> binutils 2.36". 2.36 is plenty old that we can afford to unconditionally
> use ld.bfd.
>
> However, if it's only _really_ fixed in 2.41: that one only became the
> default for Buildroot in 2024.05. So I don't really think we can count
> on it if it's really only fixed in 2.41.
>
>> ld.gold forcing BFD might actually break things, so ideally I'd want to
>> make the flag conditional on Binutils >= 2.41 (all Buildroot-built
>> toolchains meet that anyway). Or would it be acceptable to simply say
>> that people with old external toolchains are on their own?
>
> Using ld.gold only if it is available sounds like a good approach, but
> I don't know how easy it is to discover whether or not it is
> available... Maybe this works:
>
> $(wildcard $(shell $(TARGET_CC) -print-prog-name=ld.gold))
>
>
> BTW regarding Yann's patch: I would give the use-ld flag
> unconditionally, not on a per-package basis. That way, if there really
> is a problem with bfd, we have a higher chance of running in to it and
> therefore fixing it.
I'm happy to do that instead of in package/containerd if that's consensus.
Which makes me wonder: Would it make sense to provide a *global* config
for EXTLDFLAGS (BR2_GO_EXTLDFLAGS or something), which would default to
"-fuse-ld=bfd" (plus maybe "-Wl,--no-pie" with musl)? That way people
who e.g. use an external toolchain with old Binutils and Gold linker
available could adjust it.
Best regards,
Fiona
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2025-02-04 14:46 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 12:01 [Buildroot] [PATCH 1/1] package/go/go-src: stop forcing binutils-gold dependency on aarch64 Fiona Klute via buildroot
2025-02-03 12:48 ` Arnout Vandecappelle via buildroot
2025-02-03 13:04 ` Fiona Klute via buildroot
2025-02-03 14:13 ` Arnout Vandecappelle via buildroot
2025-02-03 15:17 ` Fiona Klute via buildroot
2025-02-03 20:08 ` Christian Stewart via buildroot
2025-02-04 3:41 ` Christian Stewart via buildroot
2025-02-04 6:27 ` yann.morin
2025-02-04 14:50 ` Fiona Klute via buildroot
2025-02-04 6:26 ` yann.morin
2025-02-04 10:52 ` Fiona Klute via buildroot
2025-02-04 11:13 ` yann.morin
2025-02-04 11:37 ` Fiona Klute via buildroot
2025-02-04 12:13 ` yann.morin
2025-02-04 14:37 ` Fiona Klute via buildroot
2025-02-04 11:27 ` Arnout Vandecappelle via buildroot
2025-02-04 14:46 ` Fiona Klute 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=07211c56-9048-4ed6-9aae-deec6587eef6@gmx.de \
--to=buildroot@buildroot.org \
--cc=arnout@mind.be \
--cc=christian@aperture.us \
--cc=fiona.klute@gmx.de \
--cc=thomas.perale@mind.be \
--cc=yann.morin@orange.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.