From: Ramiro Polla <ramiro.polla@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 1/5] configure: remove build-time check for gzip support in zlib
Date: Tue, 3 Jun 2025 01:22:25 +0200
Message-ID: <CALweWgDL2bA0tFNd-RvLxprbtw0pMBRXqrwsnXG9euNgfXUNKg@mail.gmail.com> (raw)
In-Reply-To: <CF97611A-0559-4FB6-8C80-93CFA267E4BD@gmail.com>
Hi Jacob,
On Fri, May 30, 2025 at 8:19 PM Jacob Lifshay <programmerjake@gmail.com> wrote:
> On May 30, 2025 4:10:45 AM PDT, Ramiro Polla <ramiro.polla@gmail.com> wrote:
> > I'll postpone this part of the patchset (patches 1 to 3) for a while
> > to give more time for people to comment. If anybody can find a system
> > where zlib doesn't support gzip, please let us know.
>
> idk if anyone is using it as the system zlib, but zlib-rs supports zlib's c api but doesn't come with a gzip executable. https://github.com/trifectatechfoundation/zlib-rs/blob/7fafed0d3ed7990349f5863dfba755cbac9ca543/README.md#c-projects
Thank you for sharing this.
The issue we're looking for is not whether a gzip executable exists,
but whether the zlib API supports decoding gzip files or only raw
deflate streams.
Ramiro
_______________________________________________
ffmpeg-devel mailing list
ffmpeg-devel@ffmpeg.org
https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
To unsubscribe, visit link above, or email
ffmpeg-devel-request@ffmpeg.org with subject "unsubscribe".
next prev parent reply other threads:[~2025-06-02 23:22 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 1:33 Ramiro Polla
2025-05-27 1:33 ` [FFmpeg-devel] [PATCH 2/5] configure: move embedded resource checks to dependency tracker Ramiro Polla
2025-05-27 1:33 ` [FFmpeg-devel] [PATCH 3/5] configure: improve gzip check Ramiro Polla
2025-05-27 6:54 ` Jacob Lifshay
2025-05-27 16:12 ` Ramiro Polla
2025-05-27 19:45 ` Jacob Lifshay
2025-05-27 1:33 ` [FFmpeg-devel] [PATCH 4/5] ffbuild/common.mak: clean up and move fftools/resources-specific code its Makefile Ramiro Polla
2025-05-27 1:48 ` softworkz .
2025-05-27 2:04 ` Ramiro Polla
2025-05-27 2:18 ` softworkz .
2025-05-27 1:55 ` softworkz .
2025-05-27 3:29 ` Ramiro Polla
2025-05-27 4:02 ` softworkz .
2025-05-27 12:35 ` Ramiro Polla
2025-05-27 19:20 ` softworkz .
2025-05-27 19:59 ` Ramiro Polla
2025-05-27 20:13 ` softworkz .
2025-05-30 11:00 ` Ramiro Polla
2025-05-27 1:33 ` [FFmpeg-devel] [PATCH 5/5] fftools/Makefile: clean files from fftools/{graph, textformat}/ Ramiro Polla
2025-06-01 21:30 ` Ramiro Polla
2025-06-01 21:46 ` softworkz .
2025-06-01 21:58 ` softworkz .
2025-05-27 1:43 ` [FFmpeg-devel] [PATCH 1/5] configure: remove build-time check for gzip support in zlib softworkz .
2025-05-27 1:52 ` Ramiro Polla
2025-05-27 13:18 ` Timo Rothenpieler
2025-05-27 17:55 ` Ramiro Polla
2025-05-30 11:10 ` Ramiro Polla
2025-05-30 18:18 ` Jacob Lifshay
2025-06-02 23:22 ` Ramiro Polla [this message]
2025-06-02 23:25 ` softworkz .
2025-06-02 23:31 ` softworkz .
2025-06-03 0:19 ` Ramiro Polla
2025-06-03 0:46 ` softworkz .
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=CALweWgDL2bA0tFNd-RvLxprbtw0pMBRXqrwsnXG9euNgfXUNKg@mail.gmail.com \
--to=ramiro.polla@gmail.com \
--cc=ffmpeg-devel@ffmpeg.org \
/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
Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
This inbox may be cloned and mirrored by anyone:
git clone --mirror https://master.gitmailbox.com/ffmpegdev/0 ffmpegdev/git/0.git
# If you have public-inbox 1.1+ installed, you may
# initialize and index your mirror using the following commands:
public-inbox-init -V2 ffmpegdev ffmpegdev/ https://master.gitmailbox.com/ffmpegdev \
ffmpegdev@gitmailbox.com
public-inbox-index ffmpegdev
Example config snippet for mirrors.
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git