[pulseaudio-discuss] svolume_orc.c: error: line 67: unknown directive: .longparam

[Paul Menzel]

Dear PulseAudio folks,


I get the following error with latest master (c0392af2).

| + do_compile
| + base_do_compile
| + '[' -e Makefile -o -e makefile -o -e GNUmakefile ']'
| + oe_runmake
| + oenote make
| + echo NOTE: make
| NOTE: make
| + make
| make  all-recursive
| make[1]: Entering directory `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv5te-oe-linux-uclibceabi/pulseaudio-0.9.22+git-r11.1-r0+c0392af20a504d7ced715cbd7152fd6d032125aa/git'
| Making all in src
| make[2]: Entering directory `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv5te-oe-linux-uclibceabi/pulseaudio-0.9.22+git-r11.1-r0+c0392af20a504d7ced715cbd7152fd6d032125aa/git/src'
|   ORCC   pulsecore/svolume-orc-gen.c
| In function pa_volume_s16ne_orc_2ch:
| error: line 67: unknown directive: .longparam
| error: variable "(null)" used before being written
| Failed to compile pa_volume_s16ne_orc_2ch
| Failed to compile pa_volume_s16ne_orc_2ch
| make[2]: *** [pulsecore/svolume-orc-gen.c] Error 1
| make[2]: Leaving directory `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv5te-oe-linux-uclibceabi/pulseaudio-0.9.22+git-r11.1-r0+c0392af20a504d7ced715cbd7152fd6d032125aa/git/src'
| make[1]: *** [all-recursive] Error 1
| make[1]: Leaving directory `/oe/build-minimal-uclibc/minimal-uclibc-dev/work/armv5te-oe-linux-uclibceabi/pulseaudio-0.9.22+git-r11.1-r0+c0392af20a504d7ced715cbd7152fd6d032125aa/git'
| make: *** [all] Error 2
| + die 'oe_runmake failed'
| + oefatal 'oe_runmake failed'
| + echo FATAL: 'oe_runmake failed'
| FATAL: oe_runmake failed
| + exit 1

I guess it has something to do with

        commit 4cd90d9e32ca9a23e3c0f7615974ea0c55ff3e49
        Author: Arun Raghavan <arun.raghavan at collabora.co.uk>
        Date:   Mon Oct 25 17:59:08 2010 +0100
        
            volume: Add Orc-based optimised volume scaling
            
            This adds volume scaling for 1- and 2-channel software volume scaling
            using Orc. While testing the MMX and SSE backends on a Core2, I see an
            ~2x performance benefit over the hand-rolled MMX and SSE code. Since I
            haven't been able to test on other architectures, the Orc code is only
            used when MMX/SSE* is present. This can be changed in the future after
            testing on AMD and ARM machines.

but I do not know anything about this.

I am using OpenEmbedded with `minimal` or `minimal-uclibc` for `MACHINE
= "at91sam9260ek"`. ORCC 0.4.9 is used on this system.


Thanks,

Paul
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
URL: <http://lists.freedesktop.org/archives/pulseaudio-discuss/attachments/20110321/47c8b745/attachment.pgp>