From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Ignacy Gawędzki" <ignacy.gawedzki@green-communications.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/elfutils: enable building with musl-based toolchains
Date: Mon, 17 Jul 2023 22:11:55 +0200 [thread overview]
Message-ID: <20230717221155.6f06a5fd@windsurf> (raw)
In-Reply-To: <20230717140932.s3yxrzyqdjf2ljcd@zenon.in.qult.net>
Hello Ignacy,
On Mon, 17 Jul 2023 16:09:32 +0200
Ignacy Gawędzki <ignacy.gawedzki@green-communications.fr> wrote:
> Sure. I started having a look and stumbled upon an issue while
> test-pkg'ing libbpf. Aside from many toolchains just being skipped
> (supposedly because of their lack of the minimum kernel headers
> version), it succeeded with those glibc and musl toolchains that it
> didn't skip, and failed with br-mips64-n64-full. The latter is based
> on uClibc v1.0.36 and it turns out uClibc prior to v1.0.38 has no
> working definition of F_DUPFD_CLOEXEC, required by libbpf.
Please note that this is a separate problem, unrelated to your effort
of making elfutils buildable with musl. Therefore, we will not require
you to fix all other unrelated problems. Of course, if you want to
tackle and solve those unrelated problems: great! But don't feel like
you have to: if they are unrelated, we are not going to make solving
them a requirement of merging your patches related to elfutils/musl.
> Now I have the following problem: how can I determine, from the
> Config.in's point-of-view, that the uClibc used by the toolchain is
> too old? There are variable that are set when the toolchain is
> uclibc-based, but in this case I have
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC=y and no way to know the actual
> version. Forbidding libbpf as soon as
> BR2_TOOLCHAIN_EXTERNAL_CUSTOM_UCLIBC=y seems overkill.
Arnout replied on that, and generally speaking we don't really care
anymore about "too old uClibc", I would probably not bother trying to
support all old uClibc toolchains.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-07-17 20:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-14 9:08 [Buildroot] [PATCH] package/elfutils: enable building with musl-based toolchains Ignacy Gawędzki
2023-07-14 10:18 ` Thomas Petazzoni via buildroot
2023-07-17 14:09 ` Ignacy Gawędzki
2023-07-17 15:31 ` Arnout Vandecappelle via buildroot
2023-07-17 20:09 ` Thomas Petazzoni via buildroot
2023-07-17 20:11 ` 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=20230717221155.6f06a5fd@windsurf \
--to=buildroot@buildroot.org \
--cc=ignacy.gawedzki@green-communications.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