From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Christian Melki <christian.melki@t2data.com>
Subject: Re: [ptxdist] [APPLIED] libunwind: Version bump. 1.6.2 -> 1.7.0 (-ish).
Date: Sat, 8 Jul 2023 09:02:53 +0200 [thread overview]
Message-ID: <20230708070253.2205802-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230703074653.2527647-1-christian.melki@t2data.com>
Thanks, applied as 89da9178a5c54ba6417fe4be67308a67cc13899b.
Michael
[sent from post-receive hook]
On Sat, 08 Jul 2023 09:02:52 +0200, Christian Melki <christian.melki@t2data.com> wrote:
> Yes. This looks funky.
> Apparently the developers misnamed the tarball.
> They've been made aware about the misnormer, but done nothing about it.
>
> * Change URL. The project doesn't seem to update in the old url.
> * Misnormer handling in the URL. Intentional.
> * Set a configure option.
>
> Signed-off-by: Christian Melki <christian.melki@t2data.com>
> Message-Id: <20230703074653.2527647-1-christian.melki@t2data.com>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libunwind.make b/rules/libunwind.make
> index 71286acd94f1..8a28aa505d16 100644
> --- a/rules/libunwind.make
> +++ b/rules/libunwind.make
> @@ -14,11 +14,12 @@ PACKAGES-$(PTXCONF_LIBUNWIND) += libunwind
> #
> # Paths and names
> #
> -LIBUNWIND_VERSION := 1.6.2
> -LIBUNWIND_MD5 := f625b6a98ac1976116c71708a73dc44a
> +LIBUNWIND_VERSION := 1.7.0
> +LIBUNWIND_MD5 := 149e49ae27646e73010df4b76989fbec
> LIBUNWIND := libunwind-$(LIBUNWIND_VERSION)
> LIBUNWIND_SUFFIX := tar.gz
> -LIBUNWIND_URL := http://download.savannah.gnu.org/releases/libunwind/$(LIBUNWIND).$(LIBUNWIND_SUFFIX)
> +# 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_SOURCE := $(SRCDIR)/$(LIBUNWIND).$(LIBUNWIND_SUFFIX)
> LIBUNWIND_DIR := $(BUILDDIR)/$(LIBUNWIND)
> LIBUNWIND_LICENSE := MIT
> @@ -42,6 +43,7 @@ LIBUNWIND_CONF_OPT := \
> --disable-documentation \
> --disable-tests \
> --enable-weak-backtrace \
> + --enable-unwind-header \
> --disable-debug \
> --disable-cxx-exceptions \
> --enable-debug-frame \
> @@ -50,7 +52,8 @@ LIBUNWIND_CONF_OPT := \
> --disable-msabi-support \
> --disable-minidebuginfo \
> --enable-zlibdebuginfo \
> - --disable-per-thread-cache
> + --disable-per-thread-cache \
> + --without-testdriver
>
> # ----------------------------------------------------------------------------
> # Target-Install
prev parent reply other threads:[~2023-07-08 7:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 7:46 [ptxdist] [PATCH v2] " Christian Melki
2023-07-08 7:02 ` Michael Olbrich [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=20230708070253.2205802-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=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