From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Thomas Petazzoni via buildroot <buildroot@buildroot.org>,
Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
Subject: Re: [Buildroot] [PATCH 1/1] package/ltrace: fix musl build
Date: Sat, 26 Oct 2024 19:05:41 +0200 [thread overview]
Message-ID: <20241026190541.6be5629c@windsurf> (raw)
In-Reply-To: <20231104184142.24723c2d@windsurf>
Hello Fabrice,
On Sat, 4 Nov 2023 18:41:42 +0100
Thomas Petazzoni via buildroot <buildroot@buildroot.org> wrote:
> Doesn't that defeat the purpose of the Upstream: flag entirely? Isn't
> the idea precisely to strongly encourage (not to say "require") that
> patches be sent upstream?
There has still been no feedback from you on this, so I looked into
this a bit more, and it's messy.
ltrace.org points to https://gitlab.com/cespedes/ltrace as being the
Git repo, and this Git repo has changes from a year ago, but absolutely
no tags.
On the other side, Buildroot uses https://github.com/dkogan/ltrace/tree/master
as the upstream... which hasn't seen any commit for the last 8 years.
Though this one has tags, including a 0.7.3 tag, which it the latest
version according to ltrace.org.
And when trying to figure if one if a fork from the other... it's not
clear.
Regarding your patch, you made the inclusion of <error.h> conditional
on __GLIBC__, but what if the code is using functions from <error.h>?
If it builds without <error.h>, then presumably it means the code is no
longer using any function from <error.h>, and those includes can be
dropped?
Alpine had a different patch, that adds a configure.ac check for
<error.h>: https://git.alpinelinux.org/aports/plain/main/ltrace/musl.patch
However, their patch is for 0.7.3, while we use the "latest" commit
from master.
So overall, quite messy stuff, so I decided to mark ltrace as
unavailable for musl:
https://gitlab.com/buildroot.org/buildroot/-/commit/859bd545821a838454577c4c1c9106837cda51cb
Best regards,
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:[~2024-10-26 17:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 15:58 [Buildroot] [PATCH 1/1] package/ltrace: fix musl build Fabrice Fontaine
2023-11-04 17:41 ` Thomas Petazzoni via buildroot
2024-10-26 17:05 ` 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=20241026190541.6be5629c@windsurf \
--to=buildroot@buildroot.org \
--cc=fontaine.fabrice@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox