Summary: | oss shouldn't be in use.mask on supported platforms | ||
---|---|---|---|
Product: | Gentoo/Alt | Reporter: | Florian Ermisch <floh.edo> |
Component: | Prefix Support | Assignee: | Gentoo Prefix <prefix> |
Status: | RESOLVED NEEDINFO | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Solaris | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Florian Ermisch
2009-02-14 14:39:06 UTC
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 ... ? |