[FFmpeg-trac] #7782(build system:closed): Enabling the option --enable-cuda-nvcc results in a build failure.

[FFmpeg]

#7782: Enabling the option --enable-cuda-nvcc results in a build failure.
-------------------------------------+-------------------------------------
             Reporter:  Brainiarc7   |                    Owner:
                 Type:  defect       |                   Status:  closed
             Priority:  normal       |                Component:  build
                                     |  system
              Version:  git-master   |               Resolution:  invalid
             Keywords:  cuda,nvcc    |               Blocked By:
             Blocking:               |  Reproduced by developer:  0
Analyzed by developer:  0            |
-------------------------------------+-------------------------------------

Comment (by Brainiarc7):

 You are correct.

 I had to delete the entire workspace and begin from scratch.
 For whatever reason (perhaps its' by design), the {{{./configure}}} script
 does not "reset" options passed to it but rather, updates them
 incrementally.

 For these who run into this issue in the future, here's the fix:

 Purge the ffmpeg directory:


 {{{
 cd ~/ffmpeg_sources && rm -fr FFmpeg
 }}}


 Then uninstall any older ffnvcodec header packages you may have in your
 system.
 Mine was in the default prefix. Handled it via:


 {{{
 cd ~/ffmpeg_sources
 git clone https://git.videolan.org/git/ffmpeg/nv-codec-headers.git
 cd nv-codec-headers
 make
 sudo make uninstall
 }}}


 As it turns out, I had an old copy of these headers installed in the
 default prefix. That should purge the older version.

 Then deploy the same to the same prefix where ffmpeg's {{{./configure}}}
 script can pick up the library's pkgconfig:


 {{{
 cd ~/ffmpeg_sources/nv-codec-headers
 make
 make install PREFIX="$HOME/ffmpeg_build"
 }}}


 Then proceed to configure and build ffmpeg as desired.

 Thanks for the assistance, and apologies for the noise.

--
Ticket URL: <https://trac.ffmpeg.org/ticket/7782#comment:2>
FFmpeg <https://ffmpeg.org>
FFmpeg issue tracker