Bug#701710: libav: FTBFS on powerpcspe

[Roland Stigge]

Source: libav
Version: 6:0.8.5-1
Severity: wishlist
Tags: patch sid
User: debian-powerpcspe at breakpoint.cc
Usertags: powerpcspe

Hi,

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


-- System Information:
Debian Release: 7.0
  APT prefers unreleased
  APT policy: (500, 'unreleased'), (500, 'unstable')
Architecture: powerpcspe (ppc)

Kernel: Linux 3.8.0 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_GB.UTF-8)
Shell: /bin/sh linked to /bin/dash
-------------- next part --------------
A non-text attachment was scrubbed...
Name: libav.patch
Type: text/x-diff
Size: 818 bytes
Desc: not available
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20130226/b5f1b52a/attachment.patch>