Bug#632303: audacious-plugins: enable oss4 output plugin

Michel Briand michelbriand at free.fr
Fri Jul 1 12:12:45 UTC 2011


Reinhard Tartler <siretart at tauware.de> - Fri, 01 Jul 2011 13:48:35 +0200

>On Fri, Jul 01, 2011 at 12:50:58 (CEST), Michel Briand wrote:
>
>> Package: audacious-plugins
>> Version: 2.4.4-1
>> Severity: normal
>>
>> Hello,
>>
>> oss4 output plugin is disabled by default by upstream.
>>
>> oss (v3) output plugin does not work correctly with oss4 mixer [1],
>> whereas the new oss4 plugin handles correctly the mixer ioctl.
>>
>> I've modified the package to enable oss4. Tested locally.
>> It works perfectly.
>>
>> Here is a quilt diff :
>>
>> --- a/debian/control
>> +++ b/debian/control
>> @@ -6,6 +6,7 @@
>>             Bilal Akhtar <bilalakhtar at ubuntu.com>
>>  Build-Depends: audacious-dev (>= 2.4.3),
>>                 debhelper (>= 7.0.50~),
>> +               oss4-dev,
>>                 libasound2-dev (>= 1.0) [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386] | libasound-dev (>= 1.0) [!kfreebsd-i386 !kfreebsd-amd64 !hurd-i386],
>>                 libavcodec-dev (>= 4:0.6.1),
>>                 libavformat-dev (>= 4:0.6.1),
>
>oss4-dev is an arch:all package without dependencies, which makes me
>suspicious. I guess that OSS4 is a pure syscall interface that does not
>require some additional library (unlike e.g. ALSA). But will that work
>with hurd or kFreeBSD as well?

I agree. It's a important question. But I don't have enough knowledge
to answer fully (I don't know about kFreeBSD).

oss4-dev package contains soundcard.h which is required to compile the
oss4 plugin for audacious :

...
/usr/include/linux/soundcard.h
package diverts others to: /usr/include/linux/soundcard.h.oss3

Indeed oss4 API rely on standard syscalls (open/ioctl ...). No library needed.


>
>> --- a/debian/rules
>> +++ b/debian/rules
>> @@ -15,6 +15,7 @@
>>                 --disable-altivec \
>>                 --disable-psf \
>>                 --disable-rpath \
>> +               --enable-oss4 \
>>                 $(additional_confflags)
>
>Will that result in a usable package on kFreeBSD, or do we need to
>enable that flag on Linux only?
>

Have you oss4 devices working on kFreeBSD ?






More information about the pkg-multimedia-maintainers mailing list