I own both G3's and G4's running Debian Stable. I can take them down
for limited periods (a day or so) to run other versions of Debian.
If someone who knows what he/she's doing can walk me through the steps
(I'm an experienced system admin. But I'm not a developer.) I'm
willing to do whatever needs to be done to get this bug fixed.
Let me know where to begin...
Rick
On Apr 3, 2010, at 7:14 PM, peter green wrote:
peter green wrote:
>The bug is actually in libsdl1.2debian. It has improper compile
flags
>for powerpc g3. What these are I do not know.
looking at the build log -maltivec seems to be the smoking gun. It
appears the upstream configure script is looking for altivec
support at build time and enabling it if it detects it (which is
the right thing to do when building for your own system but the
WRONG thing to do when building distribution packages)
Ideally this sort of issue needs access to ppc hardware both with
and without altivec to nail it down (you need to do the builds on
machines with altivec support and then check they work on machines
without it) . I'll try to take a look using qemu but I can't
promise anything.
I've come up with a patch which I beleive should fix this but
building with qemu is extremely slow and in any case to properly
test this really needs hardware both with (to do the build) and
without (to test it) altivec to properly test.
anyone on debian-powerpc have access to both and willing to test this?
--- libsdl1.2-1.2.14/debian/rules 2010-04-04 00:05:14.000000000 +0100
+++ libsdl1.2-1.2.14.new/debian/rules 2010-04-03 22:54:00.000000000
+0100
@@ -68,8 +68,10 @@
endif
# Don't use PlayStation 3 Cell driver on powerpc
+# Don't use altivec, since debian supports ppc systems that don't
have it
ifeq ($(DEB_BUILD_ARCH_CPU),powerpc)
confflags += --enable-video-ps3=no
+ confflage += --enable-altivec=no
endif
# Only build ALSA support on Linux targets
--
To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
