Arches, please keyword dev-libs/udis86-1.7. It is used by the llvmpipe driver in the next mesa release. Target keywords: ~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~sh ~sparc ~x86 ~x86-fbsd
bsd done
Marked ~hppa.
Can you explain how archs like alpha, mips, or sparc can use a "Disassembler Library for x86 and x86-64"? Surely this is irrelevant on non x86[-64] platforms.
keyworded ~arch for ppc64
This looks good on x86 also.
~x86 keyword is alreday in the ebuild.
I'd tend to agree. This looks useless for PowerPC. Can you please tell us why we need to keyword this on non-x86 architectures? Thanks!
udis86 works (as in disassembles x86 code) on all arches. media-libs/mesa will link to it in the upcoming 7.9 release, regardless of arch. But I am not fully sure whether the udis86 code in mesa is actually executed on non-x86/amd64.
(In reply to comment #8) > But I am not fully sure whether the udis86 code in mesa is actually executed on > non-x86/amd64. This is exactly what we're asking. Maybe email the mesa-dev mailing list?
I asked on IRC, but got no response. <mattst88> chithead, did you ever confirm that udis86 is actually needed by mesa/llvmpipe, wrt bug 317149 ? <mattst88> just asking because I see that sys-devel/llvm-2.7 has a udis86 USE flag. <mattst88> so if it is actually needed by mesa, then mesa's dependency should be on sys-devel/llvm[udis] <mattst88> and if it's not needed, well, udis86 needs to be removed as a dependency I tend to think that it's not needed.
ppc stable
After investigating a little more, it seems that mesa will indeed use udis86 on all platforms. But it will attempt to disassemble native code with it, so the result appears not useful on any arch but x86{,-fbsd} and amd64. I will close this bug as fixed.
Should archs which have already keyworded/stabilized this remove their keywords? (~hppa ppc ~ppc64)
The keywords can stay unless arch teams want to get rid of them. udis86 works fine on all arches. And there is no automagic link-level dependency or (working) added functionality in mesa, so nothing will break from user perspective if mesa's udis86 dependency is restricted to x86, x86-fbsd and amd64.
