From: "Martin Storsjö" <martin@martin.st>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: Re: [FFmpeg-devel] [PATCH] riscv: Use the correct path for including asm.S
Date: Wed, 28 Sep 2022 11:02:27 +0300 (EEST)
Message-ID: <cbb1366c-f437-a5cf-c2c1-88f48636a8e9@martin.st> (raw)
In-Reply-To: <8034E16E-32AA-4D36-9044-70D8CDD777C6@remlab.net>
On Wed, 28 Sep 2022, Rémi Denis-Courmont wrote:
> Le 28 septembre 2022 10:13:57 GMT+03:00, "Martin Storsjö" <martin@martin.st> a écrit :
>> Signed-off-by: Martin Storsjö <martin@martin.st>
>> ---
>> This should hopefully fix the compile failures on fate,
>> http://fate.ffmpeg.org/report.cgi?time=20220927222508&slot=riscv64-linux-gnu-gcc-12
>> and
>> http://fate.ffmpeg.org/report.cgi?time=20220927225014&slot=riscv64-linux-gnu-clang-14.
>> ---
>> libavcodec/riscv/fmtconvert_rvv.S | 2 +-
>> libavcodec/riscv/pixblockdsp_rvi.S | 2 +-
>> libavcodec/riscv/vorbisdsp_rvv.S | 2 +-
>> 3 files changed, 3 insertions(+), 3 deletions(-)
>>
>
> Why does this affect FATE only? Is it building in the source directory?
> (My local builds are in a subdirectory.)
It's building in a sibling directory next to the source directory; not
sure if that is what's making a difference here, or what it is though.
> LGTM though
Thanks, will push.
// Martin
_______________________________________________
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-09-28 8:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-28 7:13 Martin Storsjö
2022-09-28 7:59 ` Rémi Denis-Courmont
2022-09-28 8:02 ` Martin Storsjö [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=cbb1366c-f437-a5cf-c2c1-88f48636a8e9@martin.st \
--to=martin@martin.st \
--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