From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Raphael Pavlidis <raphael.pavlidis@gmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] [PATCH v1 1/2] package/xwayland: add nettle and libmd as sha1 libraries
Date: Mon, 8 Dec 2025 17:20:39 +0100 [thread overview]
Message-ID: <20251208172039.7c07673b@windsurf> (raw)
In-Reply-To: <1d599696-da61-443c-87c1-3405c24808a7@gmail.com>
Hello Raphael,
Please keep the mailing list in Cc when replying.
On Sun, 7 Dec 2025 18:00:36 +0100
Raphael Pavlidis <raphael.pavlidis@gmail.com> wrote:
> > Could you clarify why libmd is becoming the default instead of libsha1 ?
>
> In the meson files, libmd is checked first, so I assumed it would be the
> preferred choice. The detection order is as follows:
> https://gitlab.freedesktop.org/xorg/xserver/-/blob/master/meson.build?ref_type=heads#L415-419
Seems relevant. Could you include this explanation in the commit
message?
Thanks a lot!
Thomas Petazzoni
--
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
next prev parent reply other threads:[~2025-12-08 16:20 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-05 17:18 [Buildroot] [PATCH v1 1/2] package/xwayland: add nettle and libmd as sha1 libraries Raphael Pavlidis
2025-12-05 17:18 ` [Buildroot] [PATCH v1 2/2] package/xwayland: bump to version 24.1.9 Raphael Pavlidis
2025-12-05 21:01 ` Peter Korsgaard
2025-12-11 19:30 ` Arnout Vandecappelle via buildroot
2025-12-07 14:32 ` [Buildroot] [PATCH v1 1/2] package/xwayland: add nettle and libmd as sha1 libraries Thomas Petazzoni via buildroot
[not found] ` <1d599696-da61-443c-87c1-3405c24808a7@gmail.com>
2025-12-08 16:20 ` Thomas Petazzoni via buildroot [this message]
2025-12-13 15:37 ` Raphael Pavlidis
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=20251208172039.7c07673b@windsurf \
--to=buildroot@buildroot.org \
--cc=raphael.pavlidis@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