especially it shouldn't be in the "# these will more than likely never work on solaris" section. from http://www.4front-tech.com/developer/sources/stable/cddl/oss-v4.1-build1051-src-cddl.txt: OSS is currently compatible with the following operating systems and processor architectures. Other environments may be supported later. Operating system Version Processor architecture Solaris/OpenSolaris 10 or later x86, amd64, Sparc (64 bit) Linux 2.6 or later x86, x86_64 FreeBSD 6 or later x86, x86_64 SCO UnixWare 7 or later x86 SCO OpenServer 6 or later x86 Reproducible: Always
I admit, building a working oss-ebuild or even adapting one from gentoo-linux is a non-trivial task...
So what do you have working? I'm confused here ;) Do we unmask it because it does work? Or is this a hypothetical situation that it "should work" ?
libao can be build with (autodetected) oss support when the headers are supplied externally (i.e. from blastwave.org) and some ugly things to get those used by the ebuild. libao is a little b0rked, skipping leads to a frozen mplayer/mpd/whatever (stuck in nanosleep() or something). so it works but has an external dependancy as long as there's no working oss ebuild which also provides a method to install (or link?) the OSS drivers into the root-filesystem - well gotta go, an exam is waiting for me (well they are prolly _not_ waiting for me...)
if it works, we need to remove it from the mask, otherwise ... ?
