| Summary: | media-libs/assimp-5.2.3 fails to compile: USE Flag abi_x86_32 not in IUSE for assimp-5.2.3 | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Agostino Sarubbo <ago> |
| Component: | Current packages | Assignee: | Bernd <waebbl-gentoo> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | proxy-maint, sam |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: | build.log | ||
|
Description
Agostino Sarubbo
2022-04-29 05:54:40 UTC
Created attachment 775263 [details]
build.log
build log and emerge --info
Error(s) that match a know pattern in addition to what has been reported in the summary:
* die "USE Flag '${u}' not in IUSE for ${CATEGORY}/${PF}"
* USE Flag 'abi_x86_32' not in IUSE for media-libs/assimp-5.2.3
I tested in a x86_32 and multilib chroot, but unfortunately not in no-multilib environment.
Do I have to apply the patch unconditionally or is there a clean way to only apply if for a given arch?
I'm using the `if use ${ARCH}` construct in openexr as well, but that package is multilib aware, while assimp isn't.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=53b18c716a084458aef385357c686706370d2c7f commit 53b18c716a084458aef385357c686706370d2c7f Author: Sam James <sam@gentoo.org> AuthorDate: 2022-04-29 07:49:22 +0000 Commit: Sam James <sam@gentoo.org> CommitDate: 2022-04-29 07:50:22 +0000 media-libs/assimp: fix patch Package isn't multilib, so check 'use x86' instead of abi_x86_32 which is only provided w/ multilib eclasses. Closes: https://bugs.gentoo.org/841554 Signed-off-by: Sam James <sam@gentoo.org> media-libs/assimp/assimp-5.2.3.ebuild | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Thanks Sam! Hmm, I'm pretty sure, I tried `use x86` first but it led to an error during early ebuild, like the error shown in this bug report, so I switched to abi_x86_32. (In reply to Bernd from comment #5) > Thanks Sam! > Hmm, I'm pretty sure, I tried `use x86` first but it led to an error during > early ebuild, like the error shown in this bug report, so I switched to > abi_x86_32. No worries, it happens! |