Package: xulrunner
Version: 1.8.0.5-4
Severity: wishlist
Tags: patch

Hello,

the introduction of the new 'debian/patches/80_uname.dpatch' somehow broke
the ppc64 build.

When building 'xulrunner' on ppc64/unstable, I now get the following error:

xptcinvoke_ppc_linux.cpp:96: error: cast from 'void*' to 'PRUint32' loses 
precision
xptcinvoke_ppc_linux.cpp:104: error: cast from 'PRUint32*' to 'PRUint32' loses 
precision
xptcinvoke_ppc_linux.cpp:123: error: cast from 'PRUint32*' to 'PRUint32' loses 
precision
make[8]: *** [xptcinvoke_ppc_linux.o] Error 1
make[8]: Leaving directory 
`/xulrunner-1.8.0.5/xpcom/reflect/xptcall/src/md/unix'

With the attached patch 'xulrunner' can be compiled on ppc64.

The patch changes 80_uname.dpatch so that the package builds again on ppc64.
The patch also removes the 28_ppc64_build patch, which does not seem to
be necessary anymore, from the debian/patches/00list.

Regards
Andreas Jochens

diff -urN ../tmp-orig/xulrunner-1.8.0.5/debian/patches/00list 
./debian/patches/00list
--- ../tmp-orig/xulrunner-1.8.0.5/debian/patches/00list 2006-09-03 
17:12:35.000000000 +0000
+++ ./debian/patches/00list     2006-09-03 17:11:54.000000000 +0000
@@ -35,7 +35,7 @@
 25_passwdmgr_crash
 25_xpidl
 25_xrender_bug_workaround
-28_ppc64_build
+#28_ppc64_build
 30_distclean
 30_embedding_tests
 30_killAll
diff -urN ../tmp-orig/xulrunner-1.8.0.5/debian/patches/80_uname.dpatch 
./debian/patches/80_uname.dpatch
--- ../tmp-orig/xulrunner-1.8.0.5/debian/patches/80_uname.dpatch        
2006-09-03 17:12:35.000000000 +0000
+++ ./debian/patches/80_uname.dpatch    2006-09-03 16:51:19.000000000 +0000
@@ -44,7 +44,7 @@
  #
 -ifeq ($(OS_ARCH)$(OS_TEST),Linuxppc)
 +ifeq ($(OS_ARCH),Linux)
-+ifneq (,$(filter powerpc powerpc64,$(OS_TEST)))
++ifeq ($(OS_TEST),powerpc)
  CPPSRCS               := xptcinvoke_ppc_linux.cpp xptcstubs_ppc_linux.cpp
  ASFILES               := xptcinvoke_asm_ppc_linux.s xptcstubs_asm_ppc_linux.s
  AS            := $(CC) -c -x assembler-with-cpp


-- 
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]

Reply via email to