On Sunday 09 January 2005 4:54 pm, Danny van Dyk wrote: > The AMD64 Porting Team currently faces a problem concerning USE-Flags > that trigger usage of handwritten assembler code in certain packages. > The mentioned sourcecodes are nearly all written in x86 assembler. > However, the new mplayer versions contains amd64 assembler code. To use > it, the "sse" USE-Flag has to be set, which is currently use.mask'ed. We > can't unmask it, as this would break all the other ebuilds that > currently "use sse"! > > Solving the problem at hand would mean a 3-step conversion: > > 1) Each ebuild that actually uses one of the USE-Flags specified in > > ~ asm.eclass:ASM_USEFLAGS="sse sse2 mmx mmx2 3dnow 3dnowext" > > will have to inherit asm.eclass [1]. This would mean changes to approx. > 150 ebuilds in the tree. > > 2) The specified USE-Flags get unmasked. > > 3) Each ebuild that features both amd64 and x86 assembler for USE-Flag > "foo" will have to include the following line > > ~ bar.ebuild:ASM_ARCHS_FOO="x86 amd64" > > As it inherits asm.eclass, the use() function has been modified to > check whether both the USE-Flag is set AND the USE-Flag is available > for the particular architecture.
This seems like a more obvious bug: The ebuilds w/ only x86 assembly should be using "use sse && use x86" instead of simply "use sse" > > I think the ppc64 team could benefit of this eclass as well when > sources emerge that feature ppc64 altivec assembler. I'm not too sure, since PPC is somewhat more bit-inspecific than x86 is, so it might work with the same assembly... -- Luke-Jr Developer, Utopios http://utopios.org/ -- [email protected] mailing list
