From: Timo Rothenpieler <timo@rothenpieler.org>
To: ffmpeg-devel@ffmpeg.org
Subject: Re: [FFmpeg-devel] Unable to compile with cuda on WSL2
Date: Sun, 2 Apr 2023 11:27:07 +0200
Message-ID: <9350f63c-a0a7-026d-ff67-df8bac0f991e@rothenpieler.org> (raw)
In-Reply-To: <CAPa-kAwNHCa94MJ5euPExBCDWX4+-ebmZd05PSGp60JpFLLBcQ@mail.gmail.com>
On 02.04.2023 08:12, Dylan Fernando wrote:
> My PATH has /usr/local/cuda-12.1/bin, is this correct?
I don't know. All ffmpeg needs is a working nvcc on PATH.
> I installed clang with sudo apt install clang. When I run:
> ./configure --enable-cuda-llvm --extra-cflags=-I/opt/local/cuda/include
> --nvccflags="-gencode arch=compute_52,code=sm_52 -O2"
>
> I get the error:
> ERROR: cuda_llvm requested but not found
>
> 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
> ffmpeg-user@ffmpeg.org mailing list or IRC #ffmpeg on irc.libera.chat.
> Include the log file "ffbuild/config.log" produced by configure as this
> will help
> solve the problem.
>
> attached full log
>
"clang: error: unknown argument: '-gencode'"
The arguments for clang to control the target cuda arch are different.
I don't know how exactly they look, but you can probably easily find
examples.
_______________________________________________
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".
next prev parent reply other threads:[~2023-04-02 9:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-02 6:12 Dylan Fernando
2023-04-02 9:27 ` Timo Rothenpieler [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-04-01 8:41 Dylan Fernando
2023-04-01 9:28 ` 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=9350f63c-a0a7-026d-ff67-df8bac0f991e@rothenpieler.org \
--to=timo@rothenpieler.org \
--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