From: ndre <nandre@riseup.net>
To: 39738@debbugs.gnu.org
Subject: bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux
Date: Fri, 6 Mar 2020 09:04:42 -0300 [thread overview]
Message-ID: <20200306120442.GA7207@andel> (raw)
In-Reply-To: <871rqm7hfh.fsf@gnu.org>
[-- Attachment #1.1: Type: text/plain, Size: 917 bytes --]
I'm also hitting this bug, though the failing tests are
different. Here, audiodsp fails. Current commit is
aac148a87b9a79b9992b8b1a9d76c217175d4a88.
Test checkasm-audiodsp failed. Look at tests/data/fate/checkasm-audiodsp.err for details.
make: *** [tests/Makefile:237: fate-checkasm-audiodsp] Error 1
make: *** Waiting for unfinished jobs....
TEST checkasm-bswapdsp
Test suite failed, dumping logs.
command "make" "fate" "-j" "2" failed with status 2
----------------------------------------------------
tests/data/fate/checkasm-audiodsp.err:
checkasm: using random seed 854121083
MMX:
- audiodsp.audiodsp [OK]
MMXEXT:
- audiodsp.audiodsp [OK]
SSE:
- audiodsp.audiodsp [OK]
SSE2:
- audiodsp.audiodsp [OK]
SSSE3:
audiodsp.vector_clip_int32_ssse3 (audiodsp.c:111)
- audiodsp.audiodsp [FAILED]
checkasm: 1 of 6 tests have failed
---------------------------------------------------
Full log attached.
[-- Attachment #1.2: nihy0hya21wm4dpqv7iq2z8q80qq92-ffmpeg-4.2.2.drv.bz2 --]
[-- Type: application/octet-stream, Size: 62892 bytes --]
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 841 bytes --]
next prev parent reply other threads:[~2020-03-06 15:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 15:47 bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux Jan Nieuwenhuizen
2020-03-06 12:04 ` ndre [this message]
2020-03-08 20:49 ` Ludovic Courtès
2021-08-08 3:53 ` Maxim Cournoyer
2022-10-18 15:50 ` zimoun
2023-10-16 22:31 ` Simon Tournier
2023-10-17 14:31 ` Maxim Cournoyer
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200306120442.GA7207@andel \
--to=nandre@riseup.net \
--cc=39738@debbugs.gnu.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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).