Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Gyan Doshi <ffmpeg@gyani.pro>
To: "Helmut K. C. Tessarek" <tessarek@evermeet.cx>,
	FFmpeg development discussions and patches
	<ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] configure error: pkg not found even though it is available
Date: Wed, 26 Jan 2022 13:30:06 +0530
Message-ID: <a4de8aab-38b5-062f-0972-24c62a889884@gyani.pro> (raw)
In-Reply-To: <74b0b621-0c2d-d017-bff0-321a33914d70@evermeet.cx>



On 2022-01-26 01:27 pm, Helmut K. C. Tessarek wrote:
>
> On 2022-01-26 02:36, Gyan Doshi wrote:
> > Confirm that /Users/Shared/ffmpeg/sw/include/libvmaf  has current header
> > which declares vmaf_init()
>
> Yes, the header file exists in the directory and the function 
> vmaf_init() is
> declared.
>
> The vmaf version commit hash is aa1dd0b3. I compiled this version right
> before ffmpeg and all libvmaf files have the correct timestamp (todays).

Might there be a stale header in an cflags path with earlier precedence?

Regards,
Gyan
_______________________________________________
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".

  reply	other threads:[~2022-01-26  8:00 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  7:25 Helmut K. C. Tessarek
2022-01-26  7:36 ` Gyan Doshi
2022-01-26  7:57   ` Helmut K. C. Tessarek
2022-01-26  8:00     ` Gyan Doshi [this message]
2022-01-26 20:38       ` Helmut K. C. Tessarek

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=a4de8aab-38b5-062f-0972-24c62a889884@gyani.pro \
    --to=ffmpeg@gyani.pro \
    --cc=ffmpeg-devel@ffmpeg.org \
    --cc=tessarek@evermeet.cx \
    /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