Your message dated Sat, 1 Oct 2022 12:21:22 +0200
with message-id <[email protected]>
and subject line Re: Bug#1002550: ffmpeg: Please link against libatomic on
m68k, powerpc and sh4
has caused the Debian Bug report #1002550,
regarding ffmpeg: Please link against libatomic on m68k, powerpc and sh4
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
1002550: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1002550
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: ffmpeg
Severity: normal
User: [email protected]
Usertags: m68k powerpc sh4
X-Debbugs-Cc:
[email protected],[email protected],[email protected]
Hello!
The 32-bit architectures m68k, powerpc and sh4 need to link against
libatomic as well as it's already been done for armel and mipsel [1]
as can be seen from the survex FTBFS here [2].
Could you add these architectures to the list in [1]?
Thanks,
Adrian
> [1]
> https://salsa.debian.org/multimedia-team/ffmpeg/-/blob/debian/master/debian/rules#L81
> [2] https://buildd.debian.org/status/package.php?p=survex&suite=sid
--
.''`. John Paul Adrian Glaubitz
: :' : Debian Developer - [email protected]
`. `' Freie Universitaet Berlin - [email protected]
`- GPG: 62FF 8A75 84E0 2956 9546 0006 7426 3B37 F5B5 F913
--- End Message ---
--- Begin Message ---
Version: 5.1.2-1
On 2021-12-24 00:56:37 +0100, John Paul Adrian Glaubitz wrote:
> Source: ffmpeg
> Severity: normal
> User: [email protected]
> Usertags: m68k powerpc sh4
> X-Debbugs-Cc:
> [email protected],[email protected],[email protected]
>
> Hello!
>
> The 32-bit architectures m68k, powerpc and sh4 need to link against
> libatomic as well as it's already been done for armel and mipsel [1]
> as can be seen from the survex FTBFS here [2].
This issue has been fixed upstream in some 5.1.x version.
Cheers
--
Sebastian Ramacher
--- End Message ---
