all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Dariqq <dariqq@posteo.net>
To: 72917@debbugs.gnu.org
Subject: bug#72917: ffmpeg@{3,4,5} build failures on i686-linux
Date: Sat, 31 Aug 2024 15:46:01 +0000	[thread overview]
Message-ID: <d381c49b-69bd-4b17-a76f-3676bdac09a1@posteo.net> (raw)

Hi,

Upgraded my old i686 machine to after core updates merge 
(b8327cb31199fb9f4ebed6c53a59601d41def5a1) and now earlier versions of 
ffmpeg fail to build.


phase `patch-source-shebangs' succeeded after 0.6 seconds
starting phase `bypass-openal-check'
phase `bypass-openal-check' succeeded after 0.0 seconds
starting phase `configure'
ERROR: openal not found



I can't find the "alGetError ||" string in the configure script which is 
used to bypass the check on ffmepg@6 in the earlier versions (#72838).




             reply	other threads:[~2024-08-31 15:47 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-31 15:46 Dariqq [this message]
2024-09-01 12:15 ` bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Dariqq
2024-09-03 14:44   ` André Batista
2024-09-03 14:24 ` André Batista
2024-09-03 14:30   ` bug#72917: [PATCH] gnu: ffmpeg-{5, 4, 3}: Fix build on i686 with binutils 2.41 André Batista
2024-09-04 17:10     ` Ludovic Courtès
2024-09-05  7:25     ` bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Ludovic Courtès
2024-09-05 19:43       ` Dariqq
2024-09-05 23:47       ` André Batista
2024-09-11 20:10         ` André Batista
2024-09-11 21:14           ` bug#67308: bug#72917: ffmpeg-3 build failures is duplicate of bug#67308 André Batista
2024-09-12 21:16             ` bug#67308: ffmpeg-3 build failures on i686 André Batista
2024-09-03 17:39   ` bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Dariqq

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=d381c49b-69bd-4b17-a76f-3676bdac09a1@posteo.net \
    --to=dariqq@posteo.net \
    --cc=72917@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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.