unofficial mirror of bug-guix@gnu.org 
 help / color / mirror / code / Atom feed
From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: 39738@debbugs.gnu.org, Jan Nieuwenhuizen <janneke@gnu.org>
Subject: bug#39738: ffmpeg-4.2.2 fails to build on native i686-linux
Date: Tue, 17 Oct 2023 10:31:33 -0400	[thread overview]
Message-ID: <87mswhuxq2.fsf@gmail.com> (raw)
In-Reply-To: <86zg0ip5bs.fsf@gmail.com> (Simon Tournier's message of "Tue, 17 Oct 2023 00:31:35 +0200")

Hi Simon,

Simon Tournier <zimon.toutoune@gmail.com> writes:

[...]

>> Is ffmpeg still an issue an real 32 bits hardware?
>
> I do not have real 32 bits hardware to test on, but
>
>     guix build --system=i686-linux ffmpeg
>
> works for me with Guix 6113e05.  It outputs:
>
> /gnu/store/wprpm76xy3b0312579dgv0akzy6k9llh-ffmpeg-6.0-debug
> /gnu/store/y2mvpk6bna381ldskfmh6rzy1j34xnms-ffmpeg-6.0
>
> Moreover, CI reports the failures for:
>
>   v3.4.11 https://ci.guix.gnu.org/build/1836841/details
>
> and passes for:
>
>   v2.1.3 https://ci.guix.gnu.org/build/2041193/details
>   v2.8.20 https://ci.guix.gnu.org/build/1836825/details
>   v4.4.2 https://ci.guix.gnu.org/build/1836824/details
>   v5.1.3 https://ci.guix.gnu.org/build/1836833/details
>   v6.0   https://ci.guix.gnu.org/build/1836842/details
>
> Therefore, I am in favor to close it.
>
> WDYT?

Sounds reasonable, thanks for the verifications!

-- 
Thanks,
Maxim




      reply	other threads:[~2023-10-17 14:33 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
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 [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

  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=87mswhuxq2.fsf@gmail.com \
    --to=maxim.cournoyer@gmail.com \
    --cc=39738@debbugs.gnu.org \
    --cc=janneke@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).