From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: Scott Fan <fancp2007@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] package/chrony: bump to version 4.7
Date: Sun, 13 Jul 2025 11:40:10 +0200 [thread overview]
Message-ID: <5b83e70659b9312b93bde3b1610620fe@free.fr> (raw)
In-Reply-To: <20250713040046.105851-1-fancp2007@gmail.com>
Hi Scott,
Thanks for the patch.
On 13/07/2025 06:00, Scott Fan wrote:
> Release notes: https://chrony-project.org/news.html
We can read in this release note:
"Drop support for building without POSIX threads".
Indeed, pthread was made a hard requirement in upstream commit:
https://gitlab.com/chrony/chrony/-/commit/75bbccf518c617150ffaee30c7f229172b28353f
included in this new version.
For that reason, this bump fail to build with toolchains without
threads. See:
https://gitlab.com/jolivain/buildroot/-/pipelines/1923986229
Could you send an updated version of this patch taking into
account this new dependency please?
> Signed-off-by: Scott Fan <fancp2007@gmail.com>
> ---
> package/chrony/chrony.hash | 4 ++--
> package/chrony/chrony.mk | 2 +-
> 2 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/package/chrony/chrony.hash b/package/chrony/chrony.hash
> index 25535e723e..75555fed9e 100644
> --- a/package/chrony/chrony.hash
> +++ b/package/chrony/chrony.hash
> @@ -1,5 +1,5 @@
> # Locally calculated after checking pgp signature
> -# https://chrony-project.org/releases/chrony-4.6.1-tar-gz-asc.txt
> -sha256
> 571ff73fbf0ae3097f0604eca2e00b1d8bb2e91affe1a3494785ff21d6199c5c
> chrony-4.6.1.tar.gz
> +# https://chrony-project.org/releases/chrony-4.7-tar-gz-asc.txt
> +sha256
> c0de41a8c051e5d32b101b5f7014b98ca978b18e592f30ce6840b6d4602d947b
> chrony-4.7.tar.gz
> # Locally calculated
> sha256
> ab15fd526bd8dd18a9e77ebc139656bf4d33e97fc7238cd11bf60e2b9b8666c6
> COPYING
> diff --git a/package/chrony/chrony.mk b/package/chrony/chrony.mk
> index 642e1d8fd6..f2aca81d60 100644
> --- a/package/chrony/chrony.mk
> +++ b/package/chrony/chrony.mk
> @@ -4,7 +4,7 @@
> #
>
> ################################################################################
>
> -CHRONY_VERSION = 4.6.1
> +CHRONY_VERSION = 4.7
> CHRONY_SITE = https://chrony-project.org/releases
> CHRONY_LICENSE = GPL-2.0
> CHRONY_LICENSE_FILES = COPYING
> --
> 2.43.0
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-07-13 9:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-13 4:00 [Buildroot] [PATCH] package/chrony: bump to version 4.7 Scott Fan
2025-07-13 9:40 ` Julien Olivain via buildroot [this message]
2025-07-14 11:37 ` [Buildroot] [PATCH v2] " Scott Fan
2025-07-14 13:28 ` Julien Olivain 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=5b83e70659b9312b93bde3b1610620fe@free.fr \
--to=buildroot@buildroot.org \
--cc=fancp2007@gmail.com \
--cc=ju.o@free.fr \
/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