From: Gyan Doshi <ffmpeg@gyani.pro>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] [PATCH] configure: correct lensfun header function check
Date: Mon, 1 Jan 2024 09:33:30 +0530
Message-ID: <7a324672-fcf0-446e-9274-6b32ef215064@gyani.pro> (raw)
In-Reply-To: <20231231073308.191-1-ffmpeg@gyani.pro>
On 2023-12-31 01:03 pm, Gyan Doshi wrote:
> The function lf_db_new was deprecated in lensfun 09dcd3e7ad in 2017
> in favour of lf_db_create. The AVfilter was adjusted in 8b78eb312d
> but the configure check wasn't changed.
>
> lensfun removed lf_db_new declaration in lf 35c0017593 so configure
> fails to find lensfun.
> ---
This unbreaks use of the lib so plan to push in a few hours.
Regards,
Gyan
> configure | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/configure b/configure
> index cd66e42850..9262c1b650 100755
> --- a/configure
> +++ b/configure
> @@ -6776,7 +6776,7 @@ enabled libjxl && require_pkg_config libjxl "libjxl >= 0.7.0" jxl/dec
> require_pkg_config libjxl_threads "libjxl_threads >= 0.7.0" jxl/thread_parallel_runner.h JxlThreadParallelRunner
> enabled libklvanc && require libklvanc libklvanc/vanc.h klvanc_context_create -lklvanc
> enabled libkvazaar && require_pkg_config libkvazaar "kvazaar >= 2.0.0" kvazaar.h kvz_api_get
> -enabled liblensfun && require_pkg_config liblensfun lensfun lensfun.h lf_db_new
> +enabled liblensfun && require_pkg_config liblensfun lensfun lensfun.h lf_db_create
>
> if enabled libmfx && enabled libvpl; then
> die "ERROR: can not use libmfx and libvpl together"
_______________________________________________
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-01-01 4:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-31 7:33 Gyan Doshi
2024-01-01 4:03 ` Gyan Doshi [this message]
2024-01-01 10:02 ` Gyan Doshi
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=7a324672-fcf0-446e-9274-6b32ef215064@gyani.pro \
--to=ffmpeg@gyani.pro \
--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