Your message dated Sun, 3 Mar 2013 15:22:38 +0100
with message-id
<CAJ0cceZvQ6+OKsr=htwmv3dxpmjuulhxbrreyyhjgpabx_q...@mail.gmail.com>
and subject line Re: Bug#701710: libav: FTBFS on powerpcspe
has caused the Debian Bug report #701710,
regarding libav: FTBFS on powerpcspe
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
701710: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=701710
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Source: libav
Version: 6:0.8.5-1
Severity: wishlist
Tags: patch sid
User: [email protected]
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
diff -ruN test/libav-0.8.5/debian/confflags libav-0.8.5/debian/confflags
--- test/libav-0.8.5/debian/confflags 2013-01-13 11:50:42.000000000 +0100
+++ libav-0.8.5/debian/confflags 2013-02-15 14:40:15.094319046 +0100
@@ -62,6 +62,8 @@
else ifeq ($(DEB_HOST_ARCH),powerpc)
FLAVORS += altivec
nooptflags += --disable-altivec
+else ifeq ($(DEB_HOST_ARCH),powerpcspe)
+ nooptflags += --disable-altivec
else ifeq ($(DEB_HOST_ARCH),sparc)
FLAVORS += vis
nooptflags += --disable-vis
@@ -113,6 +115,11 @@
confflags += --enable-pic
endif
+ifeq ($(DEB_HOST_ARCH),powerpcspe)
+confflags += --enable-pic
+confflags += --disable-altivec
+endif
+
# Additional features
confflags += $(call cond_enable,/usr/include/bzlib.h,bzlib)
confflags += $(call cond_enable,/usr/include/dc1394/dc1394.h,libdc1394)
--- End Message ---
--- Begin Message ---
Version: 6:9.1-1
On Sun, Mar 3, 2013 at 12:25 PM, Roland Stigge <[email protected]> wrote:
> Hi!
>
> On 02/03/13 18:13, Reinhard Tartler wrote:
>> On Wed, Feb 27, 2013 at 5:41 PM, Roland Stigge <[email protected]> wrote:
>>> I had a second look at this, and it turned out that it's actually a bug
>>> in upstream's configure.
>>
>> Your patch does not apply to current libav.org master. However, I have
>> found this upstream patch that may be related here:
>>
>> http://git.libav.org/?p=libav.git;a=commitdiff;h=20bcce50
>>
>> Can you please check if libav as found in debian/experimental works on
>> powerpcse already? I would expect so, but it would be great to double
>> check.
>
> Comfirmed that current libav 6:9.3-1 from experimental works fine on
> powerpcspe. :-)
Thanks for confirming that this issue has been fixed now. I'm
therefore closing this bug.
--
regards,
Reinhard
--- End Message ---
