From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: Re: [ptxdist] [APPLIED] libjpeg: version bump 2.1.5.1 -> 3.0.0
Date: Sat, 8 Jul 2023 09:03:02 +0200 [thread overview]
Message-ID: <20230708070302.2206281-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20230704084701.2050588-1-p.zabel@pengutronix.de>
Thanks, applied as 052d53680c520fa3e21700101913314fd0c5bea0.
Michael
[sent from post-receive hook]
On Sat, 08 Jul 2023 09:03:02 +0200, Philipp Zabel <p.zabel@pengutronix.de> wrote:
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/2.1.90
> https://github.com/libjpeg-turbo/libjpeg-turbo/releases/tag/3.0.0
>
> Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
> Message-Id: <20230704084701.2050588-1-p.zabel@pengutronix.de>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/libjpeg.make b/rules/libjpeg.make
> index ca0b7735c4f0..0c7a412912d9 100644
> --- a/rules/libjpeg.make
> +++ b/rules/libjpeg.make
> @@ -16,8 +16,8 @@ PACKAGES-$(PTXCONF_LIBJPEG) += libjpeg
> #
> # Paths and names
> #
> -LIBJPEG_VERSION := 2.1.5.1
> -LIBJPEG_MD5 := aed60d4d776dd5cf00b5a01c609d50f7
> +LIBJPEG_VERSION := 3.0.0
> +LIBJPEG_MD5 := aa1f0a1c72cb6772e34d9d5136267f56
> LIBJPEG_SUFFIX := tar.gz
> LIBJPEG := libjpeg-turbo-$(LIBJPEG_VERSION)
> LIBJPEG_TARBALL := $(LIBJPEG).$(LIBJPEG_SUFFIX)
> @@ -53,14 +53,12 @@ LIBJPEG_CONF_OPT := \
> -DENABLE_STATIC=OFF \
> -DFORCE_INLINE=ON \
> -DREQUIRE_SIMD=OFF \
> - -DWITH_12BIT=OFF \
> -DWITH_ARITH_DEC=ON \
> -DWITH_ARITH_ENC=ON \
> -DWITH_FUZZ=OFF \
> -DWITH_JAVA=OFF \
> -DWITH_JPEG7=ON \
> -DWITH_JPEG8=ON \
> - -DWITH_MEM_SRCDST=ON \
> -DWITH_SIMD=$(call ptx/onoff,LIBJPEG_SIMD) \
> -DWITH_TURBOJPEG=$(call ptx/onoff,PTXCONF_LIBJPEG_TURBO)
>
prev parent reply other threads:[~2023-07-08 7:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 8:47 [ptxdist] [PATCH] " Philipp Zabel
2023-07-08 7:03 ` 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=20230708070302.2206281-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=p.zabel@pengutronix.de \
--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