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: Fri, 14 Jul 2023 12:18:34 +0200 [thread overview]
Message-ID: <20230714121834.22742681@windsurf> (raw)
In-Reply-To: <20230714090804.kaid6vdlxiubf632@zenon.in.qult.net>
Hello Ignacy,
On Fri, 14 Jul 2023 11:08:04 +0200
Ignacy Gawędzki <ignacy.gawedzki@green-communications.fr> wrote:
> Select BR2_PACKAGE_ARGP_STANDALONE as soon as the toolchain is not
> glibc-based and add argp-standalone to build dependencies in that
> case.
>
> Signed-off-by: Ignacy Gawędzki <ignacy.gawedzki@green-communications.fr>
> ---
> package/elfutils/Config.in | 9 +++------
> package/elfutils/elfutils.mk | 5 ++++-
> 2 files changed, 7 insertions(+), 7 deletions(-)
This looks very good, and was tested successfully here, but you need to
go through all the reverse dependencies of elfutils, and check if they
can now build with musl. To do that:
$ git grep "select BR2_PACKAGE_ELFUTILS"
package/avrdude/Config.in: select BR2_PACKAGE_ELFUTILS
package/bpftool/Config.in: select BR2_PACKAGE_ELFUTILS
package/falcosecurity-libs/Config.in: select BR2_PACKAGE_ELFUTILS
package/kexec-lite/Config.in: select BR2_PACKAGE_ELFUTILS
package/libbpf/Config.in: select BR2_PACKAGE_ELFUTILS
package/ltrace/Config.in: select BR2_PACKAGE_ELFUTILS
package/makedumpfile/Config.in: select BR2_PACKAGE_ELFUTILS
package/mesa3d/Config.in: select BR2_PACKAGE_ELFUTILS if BR2_PACKAGE_MESA3D_LLVM
package/mesa3d/Config.in: select BR2_PACKAGE_ELFUTILS
package/petitboot/Config.in: select BR2_PACKAGE_ELFUTILS
package/racehound/Config.in: select BR2_PACKAGE_ELFUTILS
For example, avrdude has:
depends on BR2_TOOLCHAIN_USES_UCLIBC || BR2_TOOLCHAIN_USES_GLIBC # elfutils
which is no longer correct, as elfutils no longer has this dependency.
So you need to evaluate if each of those reverse dependencies now
builds fine with musl, in which case the uclibc || glibc dependency can
be dropped, or if the package still doesn't build with musl, in which
case it's no longer elfutils fault, but some other reason (and the
comment on the uclibc || glibc needs to be updated). As an example,
avrdude now builds fine with musl.
And the fun game is that this work needs to be done recursively: once
you have checked if for example libbpf can now build with musl, you
need to look at the reverse dependencies of libbpf (in this case, only
package/kmemd).
Could you have a look at doing this?
Thanks a lot!
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:[~2023-07-14 10:18 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 [this message]
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
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=20230714121834.22742681@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