From: "Helmut K. C. Tessarek" <tessarek@evermeet.cx>
To: FFmpeg development discussions and patches
<ffmpeg-devel@ffmpeg.org>, Gyan Doshi <ffmpeg@gyani.pro>
Subject: Re: [FFmpeg-devel] configure error: pkg not found even though it is available
Date: Wed, 26 Jan 2022 15:38:02 -0500
Message-ID: <b9528b8f-6db9-6515-0c11-e0553a2ad458@evermeet.cx> (raw)
In-Reply-To: <a4de8aab-38b5-062f-0972-24c62a889884@gyani.pro>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
On 2022-01-26 03:00, Gyan Doshi wrote:
> Might there be a stale header in an cflags path with earlier precedence?
Argh, why haven't I thought of that. It was way too late for me yesterday
and apparently I couldn't think straight anymore.
Sorry for the noise. Yes, there was an old header file in the folder above.
Sometimes I wish that "make install" would take care of such things.
Once again, I am sorry.
Cheers,
K. C.
- --
regards Helmut K. C. Tessarek KeyID 0x172380A011EF4944
Key fingerprint = 8A55 70C1 BD85 D34E ADBC 386C 1723 80A0 11EF 4944
/*
Thou shalt not follow the NULL pointer for chaos and madness
await thee at its end.
*/
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEE191csiqpm8f5Ln9WvgmFNJ1E3QAFAmHxsSoACgkQvgmFNJ1E
3QDc/Q/+KeXHbDzKEJGPvjSZvKmsnZWHdPYcNdD5N54E79SOeR98memswXTdUYuZ
f1jXNGaJ9BR2RJXahOcOW9XOfOdAZcI+f79RvIuI9lnOpfmt5y6popPMBZuovgzh
3D+h7X6oTFj6J8VtdSGgnc4MQ1Po0KPeqUYwUCsv3/Nef6DDSi3hW5sQIF/K0dyv
gAVwyrcGLW9VQqNxiPLT5CUcqElXMJnBDsRBoY8+BUt/l9CCjRMkdsIxXmP+gjvd
t5COmf7UlYeMyOy5EdFltdl/rBX22320NTLrcK3pbIY9kc16b7yVJiVVviaKQxnT
6zGmQiaxm9e88wH35/DJbI9UK9KNRneG+FOVeLByYIhF9HAltPKdGNNstSAABiIS
9ljQ6W2sz1GWXj6W7FGxt6kEEnoWQ6gQ92B4h6Y4oN/4cY4bSBEX2PHRMPTP2Xto
+FN5pPl2goFjznvZlcyJT0+MHdCSL3YoDqMP6EyiUD/JstqQL7gxWBKckkMoTs+7
PA0jfkGkyE5JZF9oGZi9ghqVfofws0K+mh3uIMulqrQv2thQ4OowyU8alF+yAI98
PKYPQmtb+o3k+iRpySlA/l8Pf5Sz+S03mrrskoPermOCPjagHSJhRjMHLrCFNWy5
pti6Whtx1TqbJQYlBTVV3nvoxtHc5dNCPs4bI9S9rk5bwxdmCUs=
=a5F4
-----END PGP SIGNATURE-----
_______________________________________________
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".
prev parent reply other threads:[~2022-01-26 20:38 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
2022-01-26 20:38 ` Helmut K. C. Tessarek [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=b9528b8f-6db9-6515-0c11-e0553a2ad458@evermeet.cx \
--to=tessarek@evermeet.cx \
--cc=ffmpeg-devel@ffmpeg.org \
--cc=ffmpeg@gyani.pro \
/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