Bug#701710: libav: FTBFS on powerpcspe

[Reinhard Tartler]

On Tue, Feb 26, 2013 at 4:36 PM, Roland Stigge <stigge at antcom.de> wrote:
> libav FTBFS on powerpcspe[1] like this:
>
> [...]
> dh_testdir
> mkdir -p debian-static
> cd debian-static && CFLAGS="-fstack-protector --param=ssp-buffer-size=4 -Wformat -Werror=format-security" CPPFLAGS="-D_FORTIFY_SOURCE=2" LDFLAGS="-Wl,-z,relro" /«PKGBUILDDIR»/configure \
>                 --arch='powerpc' --enable-pthreads --enable-runtime-cpudetect --extra-version='6:0.8.5-1' --libdir=/usr/lib/powerpc-linux-gnuspe --prefix=/usr --disable-yasm   --enable-bzlib  --enable-libdc1394      --enable-libdirac       --enable-libfreetype    --enable-frei0r         --enable-gnutls         --enable-libgsm         --enable-libmp3lame     --enable-librtmp                --enable-libopenjpeg    --enable-libpulse       --enable-libschroedinger        --enable-libspeex       --enable-libtheora      --enable-vaapi  --enable-vdpau  --enable-libvorbis      --enable-libvpx         --enable-zlib --enable-gpl --enable-postproc --enable-swscale   --enable-libcdio        --enable-x11grab                --enable-libxvid
> You need a compiler that supports {} in AltiVec vector declarations.
> [...]
>
> The attached patch fixes this by assing support for powerpcspe in the Debian
> packaging, but omitting Altivec (not available on powerpcspe) in this case.
>
> Thanks,
>
> Roland
>
>
> [1] http://wiki.debian.org/PowerPCSPEPort
>

Thank you for the patch. I really think that upstream would be very
happy to include changes to configure that would make those switches
unnecessary. Would you be willing to send a patch against configure
upstream?

Cheers,
Reinhard

-- 
regards,
    Reinhard