From: Jan Nieuwenhuizen <janneke@gnu.org>
To: 39738@debbugs.gnu.org
Subject: bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux
Date: Sat, 22 Feb 2020 16:47:14 +0100 [thread overview]
Message-ID: <871rqm7hfh.fsf@gnu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 2013 bytes --]
Hi,
When building ffmpeg-4.2.2 (current master, 8d1b22b27fba3d1e4310f02a5897d231b42ca117)
natively on 32bit hardware, the build fails because of two failing tests
(full log attached)
--8<---------------cut here---------------start------------->8---
--- ./tests/ref/fate/filter-pixdesc-grayf32be 2019-12-31 21:35:25.000000000 +0000
+++ tests/data/fate/filter-pixdesc-grayf32be 2020-02-22 15:15:50.209912771 +0000
@@ -1 +1 @@
-pixdesc-grayf32be 9b23c74e8e8ffae5d7c7e82bbf5929da
+pixdesc-grayf32be 01816b882016239d0cf84241818926a4
--- ./tests/ref/fate/filter-pixdesc-grayf32le 2019-12-31 21:35:25.000000000 +0000
+++ tests/data/fate/filter-pixdesc-grayf32le 2020-02-22 15:15:50.253914049 +0000
@@ -1 +1 @@
-pixdesc-grayf32le 291f074a24c44799a1f437d1c55556f1
+pixdesc-grayf32le 1b234318d06d5a76e980c376ad8764e5
Test filter-pixdesc-grayf32be failed. Look at tests/data/fate/filter-pixdesc-grayf32be.err for details.
make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32be] Error 1
make: *** Waiting for unfinished jobs....
Test filter-pixdesc-grayf32le failed. Look at tests/data/fate/filter-pixdesc-grayf32le.err for details.
make: *** [tests/Makefile:238: fate-filter-pixdesc-grayf32le] Error 1
Test suite failed, dumping logs.
command "make" "fate" "-j" "2" failed with status 2
--8<---------------cut here---------------end--------------->8---
How to attempt fixing this?
Building it on 64 bit hardware (much faster!) works for me, i.e. this
guix build --system=i686-linux ffmpeg
works for me and can be used as a substitute...
Together with qemu-minimal-2.10 depending on ffmpeg
(https://bugs.gnu.org/39737) and no available substitutes this made for
a pretty rough "guix system reconfigure"-experience today.
I worked around this by adding a ffmpeg package that ignored the check
phase (#:tests? #f); I am wondering if we could we enable (something
like) that from the command line? WDYT?
Apart from this hiccup I had a smooth upgrade from guix 0.14,
impressive!
Greetings,
janneke
[-- Attachment #2: lbnqlz4ppj0bgckksn7r25p385qawy-ffmpeg-4.2.2.drv.bz2 --]
[-- Type: application/octet-stream, Size: 66001 bytes --]
[-- Attachment #3: Type: text/plain, Size: 152 bytes --]
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond http://lilypond.org
Freelance IT http://JoyofSource.com | Avatar® http://AvatarAcademy.com
next reply other threads:[~2020-02-22 15:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 15:47 Jan Nieuwenhuizen [this message]
2020-03-06 12:04 ` bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux ndre
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=871rqm7hfh.fsf@gnu.org \
--to=janneke@gnu.org \
--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).