Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: "Jean-Baptiste Kempf" <jb@videolan.org>
To: ffmpeg-devel <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] ABI break in 5.1
Date: Sat, 23 Jul 2022 22:36:36 +0200
Message-ID: <076af8f8-f13a-4812-b820-72a7b7702ac2@beta.fastmail.com> (raw)
In-Reply-To: <o5roo936-3124-4169-12q2-n881n2138np@vanv.qr>

On Sat, 23 Jul 2022, at 16:03, Jan Engelhardt wrote:
> (Or, in today's terms, a program built with 5.1 but which is
> combined with 5.0 at runtime, then this can happen:

FFmpeg 5.1 and 5.0 are two major versions and never ever are guaranteed to be compatible backwardly.

Your tools show that we only added symbols, therefore a program built with 5.0 will run with 5.1 at runtime, which is what .so numbering is about.

We’re not glibc and will never be, because we’re not a libc, nor an OS SDK.

If you build against 5.1, use 5.1 at runtime.

But if you built with 5.0, then 5.1 will run, as expected.

-- 
Jean-Baptiste Kempf -  President
+33 672 704 734
_______________________________________________
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".

      parent reply	other threads:[~2022-07-23 20:37 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-23 13:23 Jan Engelhardt
2022-07-23 13:28 ` Nicolas George
2022-07-23 14:03   ` Jan Engelhardt
2022-07-23 14:32     ` Nicolas George
2022-07-23 17:36       ` Jan Engelhardt
2022-07-23 17:39         ` Nicolas George
2022-07-23 20:36     ` Jean-Baptiste Kempf [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=076af8f8-f13a-4812-b820-72a7b7702ac2@beta.fastmail.com \
    --to=jb@videolan.org \
    --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