Git Inbox Mirror of the ffmpeg-devel mailing list - see https://ffmpeg.org/mailman/listinfo/ffmpeg-devel
 help / color / mirror / Atom feed
From: Dylan Fernando <dylanf123@gmail.com>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] Unable to compile with cuda on WSL2
Date: Sat, 1 Apr 2023 19:41:16 +1100
Message-ID: <CAPa-kAyNPQeVMCciK_Lx8OOpQWL9=gyDnNvBqYKTvSDqZr7hbA@mail.gmail.com> (raw)

I'm trying to compile on WSL2 Ubuntu with cuda enabled. Command:

./configure --enable-nonfree --enable-cuda-nvcc --extra-c
flags=-I/opt/local/cuda/include --nvccflags="-gencode
arch=compute_52,code=sm_52 -O2"

when compiling, I get the error:
NVCC    libavfilter/vf_bilateral_cuda.ptx
/bin/sh: 1: nvcc: not found
make: *** [ffbuild/common.mak:128: libavfilter/vf_bilateral_cuda.ptx] Error
127

The output when I run nvcc -V is:
nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2023 NVIDIA Corporation
Built on Tue_Feb__7_19:32:13_PST_2023
Cuda compilation tools, release 12.1, V12.1.66
Build cuda_12.1.r12.1/compiler.32415258_0

I added this to .bashrc:
export CUDA_HOME=/usr/local/cuda-12.1
export
LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/cuda-12.1/lib64:/usr/local/cuda-12.1/extras/CUPTI/lib64
export PATH=$PATH:$CUDA_HOME/bin

Thanks,
Dylan
_______________________________________________
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:[~2023-04-01  8:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-01  8:41 Dylan Fernando [this message]
2023-04-01  9:28 ` Timo Rothenpieler
2023-04-02  6:12 Dylan Fernando
2023-04-02  9:27 ` Timo Rothenpieler

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='CAPa-kAyNPQeVMCciK_Lx8OOpQWL9=gyDnNvBqYKTvSDqZr7hbA@mail.gmail.com' \
    --to=dylanf123@gmail.com \
    --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