#7924: FFmpeg configure complains about not finding ffnvcodec
-------------------------------------+-------------------------------------
             Reporter:  eero-t       |                     Type:  defect
               Status:  new          |                 Priority:  normal
            Component:  build        |                  Version:  git-
  system                             |  master
             Keywords:               |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------
 Summary of the bug:

 FFmpeg configure complains about missing ffnvcodec, although it's present.

 How to reproduce:
 {{{
 $ git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git
 $ cd nv-codec-headers
 $ make
 $ sudo make install
 $ pkg-config --modversion ffnvcodec
 9.0.18.2
 $ git clone  --depth 1 https://github.com/FFmpeg/FFmpeg
 $ cd FFmpeg
 $ ./configure --enable-cuvid
 }}}

 Gives:
 {{{
 ERROR: cuvid requested, but not all dependencies are satisfied: ffnvcodec

 If you think configure made a mistake, make sure you are using the latest
 version from Git.  If the latest version fails, report the problem to the
 [email protected] mailing list or IRC #ffmpeg on irc.freenode.net.
 Include the log file "ffbuild/config.log" produced by configure as this
 will help
 solve the problem.
 }}}

 There's no error about ffnvcodec in config.log except the above bogus one.
 FFmpeg test including ffnvcodec headers compiles without any issues (both
 according to config.log, and when compiling the same code manually).

 This is on Nvidia Jetson Nano with Nvidia's Ubuntu 18.04 based ARM SDK
 image.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7924>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker
_______________________________________________
FFmpeg-trac mailing list
[email protected]
https://ffmpeg.org/mailman/listinfo/ffmpeg-trac

To unsubscribe, visit link above, or email
[email protected] with subject "unsubscribe".

Reply via email to