GNOME Bugzilla – Bug 320238
Fails to build under powerpc
Last modified: 2006-02-07 14:35:49 UTC
Hi, Under Debian, gst-ffmpeg fails to build under powerpc because of an altivec include being sourced without the altivec CFLAGS: http://buildd.debian.org/fetch.php?&pkg=gst-ffmpeg&ver=0.8.7-1&arch=powerpc&stamp=1130408567&file=log&as=raw This is with toolchain package versions: libc6-dev_2.3.5-7 linux-kernel-headers_2.6.13+0rc3-2 gcc-4.0_4.0.2-3 g++-4.0_4.0.2-3 binutils_2.16.1cvs20050902-1 libstdc++6-4.0-dev_4.0.2-3 libstdc++6_4.0.2-3 Oddly, gst-ffmpeg 0.8.5 built fine under PPC: http://buildd.debian.org/fetch.php?&pkg=gst-ffmpeg&ver=0.8.5-2&arch=powerpc&stamp=1121427555&file=log&as=raw with toolchain package versions: libc6-dev_2.3.2.ds1-22 linux-kernel-headers_2.6.12.0-1 gcc-4.0_4.0.1-2 g++-4.0_4.0.1-2 binutils_2.16.1-2 libstdc++6-4.0-dev_4.0.1-2 libstdc++6_4.0.1-2 I don't have access to a Debian/PPC, and I've read that other people have built gst-ffmpeg 0.8.7 under PPC with altivec turned on just fine. I suppose one of the toolchain packages cited above is causing this, presumably GCC given the header reporting the #error. Cheers,
In a discussion with Sam Hocevar (Debian ffmpeg maintainer), he explained that -maltivec turns on Altivec supports, but doesn't produce altivec code unless explicitely requested. He said this flag can safely be used everywhere. Hence, I suggest adding -mativec to CFLAGS and leaving the other flags as they are.
okies, will look. We can probably mix it with the WARNERR_FLAGS (-Wall/-Wno-switch).
FYI, the upload I just did with this flag in the global CFLAGS passed to configure proved successful http://buildd.debian.org/fetch.php?&pkg=gst-ffmpeg&ver=0.8.7-2&arch=powerpc&stamp=1130692050&file=log&as=raw. (I also confirm the alpha fix: http://buildd.debian.org/fetch.php?&pkg=gst-ffmpeg&ver=0.8.7-2&arch=alpha&stamp=1130691541&file=log&as=raw) Cheers,
Was mostly fixed, needed ALTIVEC_CFLAGS in one more place. Now fixed in HEAD. Because the ffmpeg branch is the same it's fixed in 0.8 as well.
*** Bug 325724 has been marked as a duplicate of this bug. ***
*** Bug 330266 has been marked as a duplicate of this bug. ***