From: Kevin Wheatley <kevin.j.wheatley@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17.
Date: Fri, 9 Feb 2024 12:04:30 +0000
Message-ID: <CACzQ+ubvJ8Ezb9XEM2VKQy4jMDXYDYj3dWnZQVuXke3KT2fOCg@mail.gmail.com> (raw)
In-Reply-To: <ZcYK8VUq33Aq83Z3@sakura.greysector.net>
On Fri, Feb 9, 2024 at 11:22 AM Dominik 'Rathann' Mierzejewski
<dominik@greysector.net> wrote:
> Even so, a C17-supporting compiler (gcc 11.2.1) is available for CentOS 7
> in the devtoolset-11-gcc package (from
> http://mirror.centos.org/centos/7/sclo/x86_64/rh/).
As a 'User' of the FFmpeg project, we have a lot of CentOS/RHEL 7/etc
based headless machines which run FFmpeg and thus we compile versions
of FFmpeg on this platform. This is currently quite common across the
VFX industry as most of the industry is still in the process of moving
away from this to something more recent see https://vfxplatform.com/.
The availability of "newer" compilers via the devtool set should make
this proposed requirement a relatively small obstacle for building
newer versions. As such I think that communicating the proposed change
and its implications in the next release versions and the FFmpeg
website should be sufficient, if similar notes for other common
platforms could be added to the release notes/changelog then at least
for users of these Fedora/RHEL derivatives should be fine.
I'm assuming anybody able to compile a custom FFmpeg build, is also
able to arrange to install a prebuilt compiler, so as long as the
dependency doesn't bleed through to a runtime one, all should be good.
On the topic of why users may be so far behind the "current" for the
OS is down to several factors, in VFX and animation it is not
uncommon to work upon a project for many years prior to releasing,
this means we tend to lock down software versions in use for long
periods of time (switching out compilers, libraries etc can all change
the results of computation and thus our images). Running multiple
projects at once can make changing the OS a long duration process.
We've recently seen a similar issue with vscode bumping glibc
dependencies https://github.com/microsoft/vscode/issues/203375 though
switching glibc versions is a lot more awkward than a compiler
requirement.
Kevin
_______________________________________________
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:[~2024-02-09 12:06 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-05 19:54 [FFmpeg-devel] [PATCH 1/2] lavc/refstruct: do not use max_align_t on MSVC Anton Khirnov
2024-02-05 19:54 ` [FFmpeg-devel] [PATCH 2/2] Require compilers to support C17 Anton Khirnov
2024-02-05 20:12 ` James Almer
2024-02-05 20:13 ` Anton Khirnov
2024-02-05 20:13 ` Devin Heitmueller
2024-02-05 20:30 ` Anton Khirnov
2024-02-05 20:33 ` James Almer
2024-02-05 20:40 ` Devin Heitmueller
2024-02-07 9:50 ` Anton Khirnov
2024-02-07 16:15 ` Devin Heitmueller
2024-02-07 16:36 ` Anton Khirnov
2024-02-05 20:53 ` Niklas Haas
2024-02-09 11:22 ` Dominik 'Rathann' Mierzejewski
2024-02-09 12:04 ` Kevin Wheatley [this message]
2024-02-05 20:20 ` Lynne
2024-02-05 20:27 ` Michael Niedermayer
2024-02-05 20:31 ` Anton Khirnov
2024-02-05 20:45 ` Michael Niedermayer
2024-02-07 9:55 ` Anton Khirnov
[not found] ` <2E73439B-3AE5-46FC-80FB-2D375FD852C5@cosmin.at>
2024-02-07 18:52 ` Cosmin Stejerean via ffmpeg-devel
2024-02-07 19:27 ` Lynne
[not found] ` <1CBFE199-B1ED-47B5-BD97-7DA715EAB55B@cosmin.at>
2024-02-07 21:10 ` Cosmin Stejerean via ffmpeg-devel
2024-02-07 21:19 ` James Almer
2024-02-08 7:15 ` Rémi Denis-Courmont
2024-02-08 10:42 ` Andreas Rheinhardt
2024-02-07 21:48 ` Lynne
[not found] ` <8C790A7E-A236-4413-A4EB-AFE2F91E96A8@cosmin.at>
2024-02-08 0:36 ` Cosmin Stejerean via ffmpeg-devel
2024-02-08 4:29 ` Jean-Baptiste Kempf
2024-02-08 18:52 ` Sean McGovern
2024-02-08 19:05 ` James Almer
2024-02-08 19:46 ` Lynne
2024-02-05 20:55 ` Niklas Haas
2024-02-05 22:22 ` Stefano Sabatini
2024-02-07 9:53 ` Anton Khirnov
2024-02-06 6:50 ` Diederick C. Niehorster
2024-02-06 12:03 ` Lynne
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=CACzQ+ubvJ8Ezb9XEM2VKQy4jMDXYDYj3dWnZQVuXke3KT2fOCg@mail.gmail.com \
--to=kevin.j.wheatley@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