From: Emil Velikov <emil.l.velikov@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH v2 0/3] hwcontext_vaapi: dlopen libva-x11 and libva-drm
Date: Wed, 20 Jul 2022 17:41:33 +0100
Message-ID: <CACvgo515p5GDULza9kG+104aMwY+wDbNN95ohY+UY9E9YEyHug@mail.gmail.com> (raw)
In-Reply-To: <Ytb08dVnavbIQtoX@phare.normalesup.org>
On Tue, 19 Jul 2022 at 19:16, Nicolas George <george@nsup.org> wrote:
>
> Emil Velikov (12022-07-19):
> > As you may know the libva* set of libraries share an internal ABI
> > between them. In a resent libva commit, the va_fool API was removed.
> >
> > Thus if one is to mix different versions of libva.so and libva-x11.so
> > they will get an error, leading to a crash of the whole stack.
> >
> > The simple solution is
>
> ... a configure check.
>
> If the person who installs replaces a library with another, it is their
> responsibility to check they are compatible.
>
While I wholeheartedly agree, it's not so easy to enforce compile time
decisions at runtime. In the past, I have debugged and reported issues
where Linux distributions do not enforce the above.
We do have the typical Linux distribution model (where we have dozens
upon distros) and other distribution models. IMHO checking each
instance and combination doesn't scale. We could bring awareness to
the issue in say distribution/workflow X, which sadly may come as
finger-pointing and thus alienating.
Hope that makes sense and the team is willing to consider the extra 90
lines worth of code.
Thanks in advance
Emil
_______________________________________________
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:[~2022-07-20 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-19 17:53 Emil Velikov
2022-07-19 18:16 ` Nicolas George
2022-07-20 16:41 ` Emil Velikov [this message]
2022-07-21 20:47 ` Mark Thompson
2022-07-27 19:51 ` Emil Velikov
2022-07-27 20:00 ` Timo Rothenpieler
2022-07-29 16:43 ` Emil Velikov
2022-08-03 13:16 ` Emil Velikov
2022-07-20 10:56 Emil Velikov
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=CACvgo515p5GDULza9kG+104aMwY+wDbNN95ohY+UY9E9YEyHug@mail.gmail.com \
--to=emil.l.velikov@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