| Summary: | media-libs/libaom-3.1.2: build fails with USE=abi_x86_32 on amd64 system | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | OKUMURA N. Shin-ya <oku.ns> |
| Component: | Current packages | Assignee: | Gentoo Media-video project <media-video> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | chicago, jstein, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: |
https://bugs.gentoo.org/show_bug.cgi?id=671340 https://bugs.gentoo.org/show_bug.cgi?id=835456 |
||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Bug Depends on: | |||
| Bug Blocks: | 827895 | ||
| Attachments: |
build log
build log (32), fail build log (64), success emerge --info |
||
|
Description
OKUMURA N. Shin-ya
2021-10-03 10:14:22 UTC
Created attachment 742617 [details]
build log
Created attachment 742620 [details]
build log (32), fail
Created attachment 742623 [details]
build log (64), success
Thank you for the report. We need to have all information at hand before ticket assignment. Please * paste the emerge info as described on https://wiki.gentoo.org/wiki/Attach_the_logs_to_the_bug_ticket Please reopen this ticket (Status:UNCONFIRMED) afterwards. See also https://bugs.gentoo.org/671340 Created attachment 742644 [details]
emerge --info
I attached emerge --info. Please tell me if more information(s) is needed. 32-bit build fails with CPU_FLAGS_X86="mmx mmxext sse sse2" flags. It start to work with: CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3" emerge -1 libaom Try if it works for you. Even if you have old CPU, probably it will work. I guess that libaom use some run-time check so it will use only current CPU-supported optimizations. Tell us if this workaround works for you. O.K, emerge success with CPU_FLAGS_X86="mmx mmxext sse sse2 sse3 ssse3" and then;
# ls -l /usr/lib{32,64}/libaom*.so.3.1.2
-rwxr-xr-x 1 root root 4926116 Dec 4 11:41 /usr/lib32/libaom.so.3.1.2
-rwxr-xr-x 1 root root 4497304 Dec 4 11:41 /usr/lib64/libaom.so.3.1.2
Thunderbird, that uses libaom, seems running well currently.
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=628a37720393c8362cdecfaa9686e1e873f320c5 commit 628a37720393c8362cdecfaa9686e1e873f320c5 Author: Sam James <sam@gentoo.org> AuthorDate: 2021-12-24 06:13:33 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2021-12-24 06:13:33 +0000 media-libs/libaom: add 3.2.0 Bug: https://bugs.gentoo.org/816027 Bug: https://bugs.gentoo.org/828112 Bug: https://bugs.gentoo.org/793932 Bug: https://bugs.gentoo.org/798126 Signed-off-by: Sam James <sam@gentoo.org> media-libs/libaom/Manifest | 1 + media-libs/libaom/libaom-3.2.0.ebuild | 84 +++++++++++++++++++++++++++++++++++ media-libs/libaom/libaom-9999.ebuild | 13 ++++-- 3 files changed, 95 insertions(+), 3 deletions(-) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=1f96696e0926a6e2ff71c7455755e6a5563f0570 commit 1f96696e0926a6e2ff71c7455755e6a5563f0570 Author: Sam James <sam@gentoo.org> AuthorDate: 2022-03-17 02:07:19 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-03-17 02:08:39 +0000 media-libs/libaom: workaround bugs in intrinsic-enabled/disabled builds - For 32-bit multilib builds on amd64, force on SSE3 & SSSE3. It seems to check at runtime anyway (for some targets, inc. this one). - For arm32-on-arm64 builds, go generic, because it gets confused by ARM64 when NEON is disabled (I think?). Could try forcing arm at some point. Closes: https://bugs.gentoo.org/816027 Closes: https://bugs.gentoo.org/835456 Signed-off-by: Sam James <sam@gentoo.org> media-libs/libaom/libaom-3.3.0.ebuild | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) |
