From: Dariqq <dariqq@posteo.net>
To: "André Batista" <nandre@riseup.net>
Cc: ludo@gnu.org, 72917@debbugs.gnu.org
Subject: bug#72917: ffmpeg@{3,4,5} build failures on i686-linux
Date: Tue, 3 Sep 2024 17:39:54 +0000 [thread overview]
Message-ID: <e2ef4ecd-3775-4f1b-8c5d-ddf452f067a9@posteo.net> (raw)
In-Reply-To: <ZtccDScq0qAQwkhG@andel>
Hi André,
On 03.09.24 16:24, André Batista wrote:
>
> I'm sorry for that, I should've checked that this string would match on
> earlier versions of ffmpeg. Looking back, replacing the 'die' clause
> would make more sense. However, since changing it now would trigger
> many rebuilds, I'll send a patch which changes the match only for the
> broken earlier versions.
>
Thanks, your patch looks a lot more sensible than my bruteforce way. I
have successfully rebuild my system with your patch applied.
What would be the best way to get it to master? QA seems to think the
issue contains no patch.
> Thanks for reporting and feel free to CC me if/when you see that a patch
> of mine has been incomplete or otherwise has caused issues.
Have a nice day,
Dariqq
prev parent reply other threads:[~2024-09-03 17:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 15:46 bug#72917: ffmpeg@{3,4,5} build failures on i686-linux Dariqq
2024-09-01 12:15 ` 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 ` Dariqq [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=e2ef4ecd-3775-4f1b-8c5d-ddf452f067a9@posteo.net \
--to=dariqq@posteo.net \
--cc=72917@debbugs.gnu.org \
--cc=ludo@gnu.org \
--cc=nandre@riseup.net \
/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).