Snes9x currently compiles and runs as a native 64bit application but the ebuild is set to compile in 32bit mode. I request that the ebuild be modified to compile as a native 64bit app. Additionally, a 32bit useflag could be implemented that optionally uses the old behaviour, but I'm guessing this is not considered good practice. Reproducible: Always
the 64bit behavior is flaky at best. this is why we have the hack NATIVE_AMD64_BUILD_PLZ in place. i dont see much value in changing this behavior until snes9x stabilizes.
Really, what is the issue? Seems to work fine for me. If there are problems, could 64bit mode be a useflag? The 32bit version of snes9x has some issues on my system. They are obscure and linked to by configuration (dmix + libresample) but I would prefer to keep it as it is.
I've used snes9x in 64-bit mode with no problem. It's kind of silly that the only way to be able to use the package (aside from editing the ebuild) is by using a no-multilib profile.
I used snes9x with gtk patch long before it was included official in snes9x and in portage and never had any problems. multilib is maybe needed only when gtk flag is disabled and one wants only cli snes9x.
(In reply to comment #3) > I've used snes9x in 64-bit mode with no problem. > > It's kind of silly that the only way to be able to use the package (aside from > editing the ebuild) is by using a no-multilib profile. > Running as root: # NATIVE_AMD64_BUILD_PLZ="1" emerge snes9x worked for me, without having to modify the ebuild.
It pulls in all the emul-linux-x86-* packages though.
FYI, the 1.53 ebuild I attached to bug 380809 will automatically build native amd64 libraries.
use 1.53
