From: Christian Melki <christian.melki@t2data.com>
To: ptxdist@pengutronix.de
Subject: [ptxdist] [PATCH] libunwind: Version bump. 1.70 -> 1.7.1
Date: Mon, 24 Jul 2023 17:58:15 +0200 [thread overview]
Message-ID: <20230724155815.3593684-1-christian.melki@t2data.com> (raw)
Developers fixed the tarball misnomer and released a new version.
No other changes.
* (Re-)fix URL and remove comment.
Signed-off-by: Christian Melki <christian.melki@t2data.com>
---
rules/libunwind.make | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/rules/libunwind.make b/rules/libunwind.make
index 8a28aa505..76f5d763f 100644
--- a/rules/libunwind.make
+++ b/rules/libunwind.make
@@ -14,12 +14,11 @@ PACKAGES-$(PTXCONF_LIBUNWIND) += libunwind
#
# Paths and names
#
-LIBUNWIND_VERSION := 1.7.0
-LIBUNWIND_MD5 := 149e49ae27646e73010df4b76989fbec
+LIBUNWIND_VERSION := 1.7.1
+LIBUNWIND_MD5 := 31c7a97f88cdbe9fe8f6af93b9e4ba9c
LIBUNWIND := libunwind-$(LIBUNWIND_VERSION)
LIBUNWIND_SUFFIX := tar.gz
-# FIXME: Developers broke tarball name for 1.7.0. Revisit when proper tarballs are available and clean this up.
-LIBUNWIND_URL := https://github.com/libunwind/libunwind/releases/download/v1.7.0/libunwind-1.70.$(LIBUNWIND_SUFFIX)
+LIBUNWIND_URL := https://github.com/libunwind/libunwind/releases/download/v$(LIBUNWIND_VERSION)/$(LIBUNWIND).$(LIBUNWIND_SUFFIX)
LIBUNWIND_SOURCE := $(SRCDIR)/$(LIBUNWIND).$(LIBUNWIND_SUFFIX)
LIBUNWIND_DIR := $(BUILDDIR)/$(LIBUNWIND)
LIBUNWIND_LICENSE := MIT
--
2.34.1
next reply other threads:[~2023-07-24 15:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-24 15:58 Christian Melki [this message]
2023-07-24 17:04 ` Ladislav Michl
2023-07-24 18:32 ` Christian Melki
2023-07-25 4:58 ` Ladislav Michl
2023-08-01 7:48 ` [ptxdist] [APPLIED] " Michael Olbrich
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=20230724155815.3593684-1-christian.melki@t2data.com \
--to=christian.melki@t2data.com \
--cc=ptxdist@pengutronix.de \
/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