From: Michael Niedermayer <michael@niedermayer.cc>
To: FFmpeg development discussions and patches <ffmpeg-devel@ffmpeg.org>
Subject: [FFmpeg-devel] [ANNOUNCE] new fate clients
Date: Mon, 25 Mar 2024 14:57:29 +0100
Message-ID: <20240325135729.GM6420@pb2> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1868 bytes --]
Hi everyone
many probably already noticed i added new fate clients
there are 2 alpha, 2 parisc, 1 mips, 2 ppc, 1 risvc64, 2 s390, 2 sh4, 2 sparc, 2 x86-32 mingw, 3 x86-64 mingw
risc64 is build only because we already have real riscv64
sparc is build only because it deadlocks
parisc is build only because of:
/home/fate/ffmpeg-try/ffmpeg: error while loading shared libraries: libm.so.6: cannot enable executable stack as shared object requires: Invalid argument
(maybe a newer qemu would help)
the rest should run under qemu or wine
i had to disable iconv (like in previous debian/ubuntu based qemu environments)
because while it builds, these fail at runtime and it seems gconv related files
are missing in libc packages compared to native libc packages
there are remaining fate test failures in some clients like
sh4 (Unhandled trap: 0x180 and others)
alpha some differences in filter-waveform and vc1_ilaced_twomv that is a old failure IIRC
with mips I randomly set some --cpu and --disable combination until it didnt catastrophically fail
(or i hope at least as this didnt run yet)
I think ill take a break from these fateclients now and let others tinker with these
(you should be able to try these all locally, its standard ubuntu packages for cross compilers
and qemu and comand lines shown in the fate web interface)
if anything is configured dumbly then tell me please. Otherwise please
grab the ubuntu packages and fix the fine code yourself ;)
thx
--
Michael GnuPG fingerprint: 9FF2128B147EF6730BADF133611EC787040B0FAB
Awnsering whenever a program halts or runs forever is
On a turing machine, in general impossible (turings halting problem).
On any real computer, always possible as a real computer has a finite number
of states N, and will either halt in less than N cycles or never halt.
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
[-- Attachment #2: Type: text/plain, Size: 251 bytes --]
_______________________________________________
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:[~2024-03-25 13:57 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20240325135729.GM6420@pb2 \
--to=michael@niedermayer.cc \
--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