| Summary: | media-libs/dav1d: missing dependency: dev-lang/nasm | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Thomas Sachau <tommy> |
| Component: | Current packages | Assignee: | Luca Barbato <lu_zero> |
| Status: | RESOLVED INVALID | ||
| Severity: | normal | ||
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| See Also: | https://bugs.gentoo.org/show_bug.cgi?id=835766 | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Thomas Sachau
2019-04-02 19:35:17 UTC
Dependency on dev-lang/nasm is already in ebuild: $ portageq metadata / ebuild media-libs/dav1d-0.2.1 DEPEND asm? ( abi_x86_32? ( >=dev-lang/nasm-2.13 ) abi_x86_64? ( >=dev-lang/nasm-2.13 ) ) >=dev-util/meson-0.48.2 >=dev-util/ninja-1.7.2 $ Your build log shows that you have USE="asm" enabled. You must have some other problem... My build.log also shows, that i have neither abi_x86_64 nor abi_x86_32 enabled, so there is no dependency on dev-lang/nasm for me. Having a quick look at the ebuild, it seems like the intention was to only enable asm for the 64bit build. So why is there a condition on abi_x86_32? It would probably be better to depend on amd64? instead of those abi_x86_* flags. (In reply to Thomas Sachau from comment #2) > My build.log also shows, that i have neither abi_x86_64 nor abi_x86_32 > enabled, so there is no dependency on dev-lang/nasm for me. profiles/arch/amd64/use.force has abi_x86_64, so normally this USE flag would be forced for amd64 users. Why is it not forced for you? Is it caused by multilib Portage? > Having a quick look at the ebuild, it seems like the intention was to only > enable asm for the 64bit build. So why is there a condition on abi_x86_32? abi_x86_32 != abi_x86_x32 The intention is to enable asm for abi_x86_32 and abi_x86_64, but not abi_x86_x32. (In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > Dependency on dev-lang/nasm is already in ebuild: > $ portageq metadata / ebuild media-libs/dav1d-0.2.1 DEPEND > asm? ( abi_x86_32? ( >=dev-lang/nasm-2.13 ) abi_x86_64? ( > >=dev-lang/nasm-2.13 ) ) >=dev-util/meson-0.48.2 >=dev-util/ninja-1.7.2 > $ > > Your build log shows that you have USE="asm" enabled. > You must have some other problem... For me, I get the following: ============================ Program nasm found: YES (/usr/bin/nasm) meson.build:332:16: ERROR: Problem encountered: nasm 2.13.02 or later is required, found nasm 2.13.01 ============================ So, the dependency still needs to be fixed. (In reply to Aaron W. Swenson from comment #4) > (In reply to Arfrever Frehtes Taifersar Arahesis from comment #1) > > Dependency on dev-lang/nasm is already in ebuild: > > $ portageq metadata / ebuild media-libs/dav1d-0.2.1 DEPEND > > asm? ( abi_x86_32? ( >=dev-lang/nasm-2.13 ) abi_x86_64? ( > > >=dev-lang/nasm-2.13 ) ) >=dev-util/meson-0.48.2 >=dev-util/ninja-1.7.2 > > $ > > > > Your build log shows that you have USE="asm" enabled. > > You must have some other problem... > > For me, I get the following: > > ============================ > Program nasm found: YES (/usr/bin/nasm) > > meson.build:332:16: ERROR: Problem encountered: nasm 2.13.02 or later is > required, found nasm 2.13.01 > ============================ > > So, the dependency still needs to be fixed. I encountered the same error as Arron. Emerging nasm to 2.14.02 resolved the error. The reason the dependency wasn't satisfied for you is because you're overriding the ABI_X86_* flags? |
