From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: "Sven Püschel" <s.pueschel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libtag: version bump 2.1.1 -> 2.3.2
Date: Fri, 13 Nov 2026 09:39:30 +0100 [thread overview]
Message-ID: <20261113083930.1380723-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20261030165914.3513358-1-s.pueschel@pengutronix.de>
Thanks, applied as dc40657dbdb090b31e90003e23f4b4bae9542efc.
Michael
[sent from post-receive hook]
On Fri, 13 Nov 2026 09:39:30 +0100, Sven Püschel <s.pueschel@pengutronix.de> wrote:
> updated options are based on the configure_helper.py helper script
> output.
>
> Signed-off-by: Sven Püschel <s.pueschel@pengutronix.de>
> Message-Id: <20261030165914.3513358-1-s.pueschel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libtag.make b/rules/libtag.make
> index 1a46b984831a..29e0ab1d159e 100644
> --- a/rules/libtag.make
> +++ b/rules/libtag.make
> @@ -14,8 +14,8 @@ PACKAGES-$(PTXCONF_LIBTAG) += libtag
> #
> # Paths and names
> #
> -LIBTAG_VERSION := 2.1.1
> -LIBTAG_SHA256 := 3716d31f7c83cbf17b67c8cf44dd82b2a2f17e6780472287a16823e70305ddba
> +LIBTAG_VERSION := 2.3.2
> +LIBTAG_SHA256 := 3ca2d8afaa7f1cf7f6ed10e511ebc368bfacd6dcaa3dbfa690b89e502e8963dc
> LIBTAG := taglib-$(LIBTAG_VERSION)
> LIBTAG_SUFFIX := tar.gz
> LIBTAG_URL := https://taglib.org/releases/$(LIBTAG).$(LIBTAG_SUFFIX)
> @@ -39,12 +39,12 @@ LIBTAG_CONF_OPT := \
> -DBUILD_SHARED_LIBS=ON \
> -DBUILD_TESTING=OFF \
> -DTRACE_IN_RELEASE=OFF \
> - -DUTF8_INSTALL=OFF \
> - -DUTF8_SAMPLES=OFF \
> - -DUTF8_TESTS=OFF \
> + -DUTF8CPP_ENABLE_BENCHMARKS=OFF \
> + -DUTF8CPP_ENABLE_TESTS=OFF \
> -DWITH_APE=ON \
> -DWITH_ASF=ON \
> -DWITH_DSF=ON \
> + -DWITH_MATROSKA=ON \
> -DWITH_MOD=ON \
> -DWITH_MP4=ON \
> -DWITH_RIFF=ON \
prev parent reply other threads:[~2026-11-13 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 16:59 [ptxdist] [PATCH] " Sven Püschel
2026-11-13 8:39 ` 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=20261113083930.1380723-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=ptxdist@pengutronix.de \
--cc=s.pueschel@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