Bug#857839: installation-reports: ppc64el fails to boot after installation on JFS partition
Package: installation-reports Boot method: ISO image Image version: http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso Date: Tue Mar 15 2017 14:36:17 Machine: qemu VM / powerVM Processor: ppc64el Memory: 4Gb Partitions: /dev/sda1 7.3 MBPowerPC PReP boot partition /dev/sda2 6.6 GBjfs /dev/sda3 4.2 GBswap Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Using qemu, I created a ppc64el virtual machine. I selected the guided partitioning to use the entire disk. I changed the root partition (partition 2) from ext4 to JFS. The installation went well but it failed to boot some times. I got the same on P8 PowerVM. Here what I got on boot: Loading Linux 4.9.0-2-powerpc64le ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.9.0-2-powerpc64le (debian-ker...@lists.debian.org) (gcc version 6.3.0 20170221 (Debian 6.3.0-8) ) #1 SMP Debian 4.9.13-1 (2017-02-27) Detected machine type: 0101 Max number of cores passed to firmware: 512 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.9.0-2-powerpc64le root=/dev/sda2 ro quiet memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 041c alloc_top: 3000 alloc_top_hi : 0001 rmo_top : 3000 ram_top : 0001 instantiating rtas at 0x2fff... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x041d -> 0x041d0a2f Device tree struct 0x041e -> 0x041f Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... -> smp_release_cpus() spinning_secondaries = 3 <- smp_release_cpus() Linux ppc64le #1 SMP Debian 4.fsck.jfs version 1.1.15, 04-Mar-2011 processing started: 3/15/2017 14:36:17 The current device is: /dev/sda2 Block size in bytes: 4096 Filesystem size in blocks: 160 **Phase 0 - Replay Journal Log Filesystem is clean. [1.213186] Unable to handle kernel paging request for data at address 0x [1.213483] Faulting instruction address: 0xd0bce14c [1.213691] Oops: Kernel access of bad area, sig: 11 [#1] [1.213908] SMP NR_CPUS=2048 [1.214039] NUMA [1.214144] pSeries [1.214246] Modules linked in: ip_tables x_tables autofs4 jfs sd_mod virtio_net ibmvscsi scsi_transport_srp virtio_pci virtio_ring virtio [1.215059] CPU: 1 PID: 933 Comm: (journald) Not tainted 4.9.0-2-powerpc64le #1 Debian 4.9.13-1 [1.215394] task: c341d000 task.stack: c34ec000 [1.215639] NIP: d0bce14c LR: d0bce080 CTR: c012df80 [1.215923] REGS: c34eef10 TRAP: 0300 Not tainted (4.9.0-2-powerpc64le Debian 4.9.13-1) [1.216249] MSR: 80010280b033[1.217196] CR: 28242822 XER: 2000 [1.217343] CFAR: c012f9fc DAR: DSISR: 4000 SOFTE: 1 GPR00: d0bce080 c34ef190 d0be8d08 c000f6f67a00 GPR04: 0001 0001 GPR08: 000201d4 d0bdb680 GPR12: c012df80 cfb80900 0020 GPR16: 0010 c34ef3e0 c34ef8b0 GPR20: 024213ca c34ef918 c000fc796868 GPR24: 0020 c34ef38c c34ef380 c34ef388 GPR28: 0020 c000fb6f8c48 f03da600 c000fb6f8c28 NIP [d0bce14c] release_metapage+0x174/0x340 [jfs] [1.221512] LR [d0bce080] release_metapage+0xa8/0x340 [jfs] [1.221585] Unable to handle kernel paging request for data at address 0x [1.221586] Faulting instruction address: 0xd0bce518 [1.222342] Call Trace: [1.222458] [c34ef190] [d0bce080] release_metapage+0xa8/0x340 [jfs] (unreliable) [1.222897] [c34ef210] [d0bb843c] xtLookup+0x1b4/0x200 [jfs] [1.223223] [c34ef350] [d0bb23c4] jfs_get_block+0x2fc/0x320 [jfs] [1.223605] [c34ef3c0] [c036b77c] do_mpage_readpage+0x54c/0x780 [1.223986] [c34ef890] [c036bad0] mpage_readpages+0x120/0x1e0 [1.224312] [c34ef970] [d0bb2494] jfs_readpages+0x4c/0x80 [jfs] [1.224757] [c34ef9b0] [c0254eb8]
Bug#839643: [Pkg-rust-maintainers] Bug#839643: src:rustc: FTBFS on ppc64el
On 02/26/2017 03:49 PM, Ximin Luo wrote: > Erwan Prioul: >> Hi, >> >> I've been able to build the rust package on ppc64el with the attached patch. >> In the patch: >> * workaround to avoid issue with the tests smoke_dtor and >> test_typed_arena_drop_small_count: no optimization on ppc64el >> * add ignore flags to asm test files that have no meaning for ppc64el >> * add a reference to a library in a makefile >> >> Thanks for considering the patch. >> > > Hi Erwan, thanks for the patch! I've applied it in our git, and going to test > it soon. > > However could you explain d-missing-ref-dlsym-ppc64el.patch a bit and why > it's not suitable for upstream? This patch adds a reference to the dl library. Without it, the related test fails with: "undefined reference to `dlsym'", at least on ppc64el. Actually, my patch is quite rough, it misses a test about the architecture to add or not the option -ldl. Erwan.
Bug#839643: src:rustc: FTBFS on ppc64el
Hi, I've been able to build the rust package on ppc64el with the attached patch. In the patch: * workaround to avoid issue with the tests smoke_dtor and test_typed_arena_drop_small_count: no optimization on ppc64el * add ignore flags to asm test files that have no meaning for ppc64el * add a reference to a library in a makefile Thanks for considering the patch. Erwan. diff -Naur a/debian/patches/d-missing-ref-dlsym-ppc64el.patch b/debian/patches/d-missing-ref-dlsym-ppc64el.patch --- a/debian/patches/d-missing-ref-dlsym-ppc64el.patch 1970-01-01 00:00:00.0 + +++ b/debian/patches/d-missing-ref-dlsym-ppc64el.patch 2017-01-04 20:34:56.0 + @@ -0,0 +1,15 @@ +diff -Naur a/src/test/run-make/issue-24445/Makefile b/src/test/run-make/issue-24445/Makefile +--- a/src/test/run-make/issue-24445/Makefile 2017-02-17 10:21:17.092001151 + b/src/test/run-make/issue-24445/Makefile 2017-02-21 13:07:36.719995153 + +@@ -3,9 +3,9 @@ + ifeq ($(UNAME),Linux) + all: + $(RUSTC) foo.rs +- $(CC) foo.c -lfoo -L $(TMPDIR) -Wl,--gc-sections -lpthread -o $(TMPDIR)/foo ++ $(CC) foo.c -lfoo -L $(TMPDIR) -Wl,--gc-sections -lpthread -ldl -o $(TMPDIR)/foo + $(call RUN,foo) +- $(CC) foo.c -lfoo -L $(TMPDIR) -Wl,--gc-sections -lpthread -pie -fPIC -o $(TMPDIR)/foo ++ $(CC) foo.c -lfoo -L $(TMPDIR) -Wl,--gc-sections -lpthread -ldl -pie -fPIC -o $(TMPDIR)/foo + $(call RUN,foo) + else + all: diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2017-02-17 10:20:57.256001150 + +++ b/debian/patches/series 2017-01-04 20:34:56.0 + @@ -9,6 +9,7 @@ u-ignoretest-arm64.patch u-ignoretest-jemalloc.patch u-detect-mips-cpu.patch +u-ignoretest-powerpc.patch # Debian-specific patches, not suitable for upstream d-rust-gdb-paths @@ -19,3 +20,4 @@ d-dynamic-link-llvm.patch d-use-system-jquery.patch d-fill-in-mips-mk-rules.patch +d-missing-ref-dlsym-ppc64el.patch diff -Naur a/debian/patches/u-ignoretest-powerpc.patch b/debian/patches/u-ignoretest-powerpc.patch --- a/debian/patches/u-ignoretest-powerpc.patch 1970-01-01 00:00:00.0 + +++ b/debian/patches/u-ignoretest-powerpc.patch 2017-01-04 20:34:56.0 + @@ -0,0 +1,66 @@ +diff -Naur a/src/test/compile-fail/asm-bad-clobber.rs b/src/test/compile-fail/asm-bad-clobber.rs +--- a/src/test/compile-fail/asm-bad-clobber.rs 2017-02-17 10:21:15.192001150 + b/src/test/compile-fail/asm-bad-clobber.rs 2017-02-20 10:53:33.355996252 + +@@ -12,6 +12,7 @@ + // ignore-arm + // ignore-aarch64 + // ignore-s390x ++// ignore-powerpc + + #![feature(asm, rustc_attrs)] + +diff -Naur a/src/test/compile-fail/asm-in-bad-modifier.rs b/src/test/compile-fail/asm-in-bad-modifier.rs +--- a/src/test/compile-fail/asm-in-bad-modifier.rs 2017-02-17 10:21:15.040001150 + b/src/test/compile-fail/asm-in-bad-modifier.rs 2017-02-20 10:53:55.13754 + +@@ -9,6 +9,7 @@ + // except according to those terms. + + // ignore-s390x ++// ignore-powerpc + + #![feature(asm)] + +diff -Naur a/src/test/compile-fail/asm-misplaced-option.rs b/src/test/compile-fail/asm-misplaced-option.rs +--- a/src/test/compile-fail/asm-misplaced-option.rs2017-02-17 10:21:16.120001149 + b/src/test/compile-fail/asm-misplaced-option.rs2017-02-20 10:54:33.619839143 + +@@ -12,6 +12,7 @@ + // ignore-arm + // ignore-aarch64 + // ignore-s390x ++// ignore-powerpc + + #![feature(asm, rustc_attrs)] + +diff -Naur a/src/test/compile-fail/asm-out-assign-imm.rs b/src/test/compile-fail/asm-out-assign-imm.rs +--- a/src/test/compile-fail/asm-out-assign-imm.rs 2017-02-17 10:21:14.804001149 + b/src/test/compile-fail/asm-out-assign-imm.rs 2017-02-20 10:55:26.796023677 + +@@ -9,6 +9,7 @@ + // except according to those terms. + + // ignore-s390x ++// ignore-powerpc + + #![feature(asm)] + +diff -Naur a/src/test/compile-fail/asm-out-no-modifier.rs b/src/test/compile-fail/asm-out-no-modifier.rs +--- a/src/test/compile-fail/asm-out-no-modifier.rs 2017-02-17 10:21:12.548001149 + b/src/test/compile-fail/asm-out-no-modifier.rs 2017-02-20 10:55:37.908025746 + +@@ -9,6 +9,7 @@ + // except according to those terms. + + // ignore-s390x ++// ignore-powerpc + + #![feature(asm)] + +diff -Naur a/src/test/compile-fail/asm-out-read-uninit.rs b/src/test/compile-fail/asm-out-read-uninit.rs +--- a/src/test/compile-fail/asm-out-read-uninit.rs 2017-02-17 10:21:12.968001149 + b/src/test/compile-fail/asm-out-read-uninit.rs 2017-02-20 10:55:49.260001428 + +@@ -9,6 +9,7 @@ + // except according to those terms. + + // ignore-s390x ++// ignore-powerpc + + #![feature(asm)] + diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2017-02-17 10:20:57.256001150 + +++ b/debian/rules 2017-01-04 20:34:56.0 + @@ -106,6 +106,11 @@ DEB_CONFIGURE_FLAGS += --disable-optimize
Bug#853755: installation-reports: ppc64el fails to boot after installation
I ran successful tests from [1] which includes the upstream commit from [2]. [1] https://anonscm.debian.org/cgit/pkg-systemd/systemd.git/commit/?id=4de2441f351136a0f6f5b9797a77f9705879ccdf [2] https://github.com/systemd/systemd/issues/5230 Erwan. signature.asc Description: OpenPGP digital signature
Bug#853755: installation-reports: ppc64el fails to boot after installation
On 02/02/2017 02:46 PM, Michael Biebl wrote: > > Erwan, could you try 232-1 from snapshots.debian.org and see if the > problem is reproducible there? I ran few tests. 232-1 is OK, same result for 232-8 and 232-10. The issue appeared in 232-11. Erwan. signature.asc Description: OpenPGP digital signature
Bug#853755: installation-reports: ppc64el fails to boot after installation
Hello, On 02/01/2017 04:58 PM, Cyril Brulebois wrote: > Hi, > > Erwan Prioul <er...@linux.vnet.ibm.com> (2017-02-01): >> Unfortunately, I don't have a working image. >> The issue has appeared since last Saturday, Jan 28th. > > Could this be due to latest kernel updates? 4.9.6-x were accepted on > the 27/28th. You could either use rescue mode or redo an installation, > and in /target (before rebooting into the installed system), try > installing an older version of the linux-image package. Older binaries > are available on snapshots: > http://snapshot.debian.org/package/linux/ AFAIK 4.9.6-x is not yet provided in the daily image for ppc64el. It's still the 4.9.2-2. Anyway, I ran a couple of tests with 4.9.6-3 and 4.8.15-2, and I got the same error. I did another install but this time I took the previous version of systemd, 232-8 instead of 232-14 (current version), and it worked. > Anyway, I think this should be filed against src:linux since the > installation process itself seems to have worked fine. Feel free to > reassign once you have found in which version the regression was > introduced (if that's indeed a regression). > > KiBi. I'll reassign this to systemd. Erwan. signature.asc Description: OpenPGP digital signature
Bug#853755: installation-reports: ppc64el fails to boot after installation
Hi KiBi, On 01/31/2017 08:04 PM, Cyril Brulebois wrote: > Hi Erwan, > > Erwan Prioul <er...@linux.vnet.ibm.com> (2017-01-31): >> Package: installation-reports >> >> Boot method: ISO image >> Image version: >> http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso >> Date: Tue Jan 31 16:18:45 2017 >> >> Machine: qemu VM >> Processor: ppc64el >> Memory: 4Gb >> Partitions: >> /dev/sda1 7.3 MBPowerPC PReP boot partition >> /dev/sda2 6.6 GBext4 >> /dev/sda3 4.2 GBswap >> >> Initial boot: [O] >> Detect network card:[O] >> Configure network: [O] >> Detect CD: [O] >> Load installer modules: [O] >> Detect hard drives: [O] >> Partition hard drives: [O] >> Install base system:[O] >> Clock/timezone setup: [O] >> User/password setup:[O] >> Install tasks: [O] >> Install boot loader:[O] >> Overall install:[O] >> >> Comments/Problems: >> >> Using qemu, I created a ppc64el virtual machine. >> I selected the guided partitioning to use the entire disk (all the >> default options). >> The installation went well but it failed to boot then. >> I got the same on P8 PowerVM and P8 baremetal. > > Do you have a reference image which managed to boot after installation, > which might help us pinpoint the regression (since it looks like one)? Unfortunately, I don't have a working image. The issue has appeared since last Saturday, Jan 28th. Erwan. signature.asc Description: OpenPGP digital signature
Bug#853755: installation-reports: ppc64el fails to boot after installation
Package: installation-reports Boot method: ISO image Image version: http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso Date: Tue Jan 31 16:18:45 2017 Machine: qemu VM Processor: ppc64el Memory: 4Gb Partitions: /dev/sda1 7.3 MBPowerPC PReP boot partition /dev/sda2 6.6 GBext4 /dev/sda3 4.2 GBswap Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[O] Overall install:[O] Comments/Problems: Using qemu, I created a ppc64el virtual machine. I selected the guided partitioning to use the entire disk (all the default options). The installation went well but it failed to boot then. I got the same on P8 PowerVM and P8 baremetal. Loading Linux 4.9.0-1-powerpc64le ... Loading initial ramdisk ... OF stdout device is: /vdevice/vty@7100 Preparing to boot Linux version 4.9.0-1-powerpc64le (debian-ker...@lists.debian.org) (gcc version 6.3.0 20161229 (Debian 6.3.0-2) ) #1 SMP Debian 4.9.2-2 (2017-01-12) Detected machine type: 0101 Max number of cores passed to firmware: 512 (NR_CPUS = 2048) Calling ibm,client-architecture-support... done command line: BOOT_IMAGE=/boot/vmlinux-4.9.0-1-powerpc64le root=/dev/sda2 ro quiet memory layout at init: memory_limit : (16 MB aligned) alloc_bottom : 0420 alloc_top: 3000 alloc_top_hi : 0001 rmo_top : 3000 ram_top : 0001 instantiating rtas at 0x2fff... done prom_hold_cpus: skipped copying OF device tree... Building dt strings... Building dt structure... Device tree strings 0x0421 -> 0x04210a2f Device tree struct 0x0422 -> 0x0423 Quiescing Open Firmware ... Booting Linux via __start() @ 0x0200 ... -> smp_release_cpus() spinning_secondaries = 3 <- smp_release_cpus() Linux ppc64le #1 SMP Debian 4./dev/sda2: clean, 29927/400624 files, 271614/160 blocks [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [DEPEND] Dependency failed for Flush Journal to Persistent Storage. [ OK ] Started Load Kernel Modules. [ OK ] Stopped Journal Service. Starting Journal Service... Starting Apply Kernel Variables... [ OK ] Started Remount Root and Kernel File Systems. [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ OK ] Stopped Journal Service. Starting Journal Service... Starting udev Coldplug all Devices... Starting Load/Save Random Seed... [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ OK ] Started Apply Kernel Variables. [ OK ] Stopped Journal Service. Starting Journal Service... [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ OK ] Stopped Journal Service. Starting Journal Service... [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ OK ] Stopped Journal Service. [FAILED] Failed to start Journal Service. See 'systemctl status systemd-journald.service' for details. [ OK ] Started Load/Save Random Seed. [ OK ] Started Create Static Device Nodes in /dev. Starting udev Kernel Device Manager... [1.398789] systemd[968]: systemd-udevd.service: Failed at step ADDRESS_FAMILIES spawning /lib/systemd/systemd-udevd: File exists [FAILED] Failed to start udev Kernel Device Manager. See 'systemctl status systemd-udevd.service' for details. [ OK ] Stopped udev Kernel Device Manager. Starting udev Kernel Device Manager... [1.423971] systemd[978]: systemd-udevd.service: Failed at step ADDRESS_FAMILIES spawning /lib/systemd/systemd-udevd: File exists [ OK ] Started udev Coldplug all Devices. [FAILED] Failed to start udev Kernel Device Manager. See 'systemctl status systemd-udevd.service' for details. [ OK ] Stopped udev Kernel Device Manager. Starting udev Kernel Device Manager... [1.458088] systemd[993]: systemd-udevd.service: Failed at step ADDRESS_FAMILIES spawning /lib/systemd/systemd-udevd: File exists [FAILED] Failed to start udev Kernel Device Manager. See 'systemctl status systemd-udevd.service' for details. [ OK ] Stopped udev Kernel Device Manager. Starting udev Kernel Device Manager... [1.498435] systemd[995]: systemd-udevd.service: Failed at step ADDRESS_FAMILIES spawning /lib/systemd/systemd-udevd: File exists [FAILED] Failed to start udev Kernel Device Manager. See 'systemctl status systemd-udevd.service' for details.
Bug#839643: src:rustc: ppc64el is missing
Hi, I've noticed big progress upstream. I'm able to compile on ppc64el \o/ What would be the next steps to have it packaged? First, I guess, is to have a new tag/version upstream, but then? Erwan.
Bug#847179: src:vflib3: FTBFS on ppc64el
Package: src:vflib3 Version: 3.6.14.dfsg-3+nmu2 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, it fails with this message: make[2]: Entering directory '/«PKGBUILDDIR»/t1lib' mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/VFlib/3.6.14/t1lib make[2]: Leaving directory '/«PKGBUILDDIR»/t1lib' make[2]: Entering directory '/«PKGBUILDDIR»/ascii-jtex' Installing ADJ files for Japanese TeX... mkdir /«PKGBUILDDIR»/debian/tmp/usr/share/VFlib/3.6.14/ascii-jtex make[2]: Leaving directory '/«PKGBUILDDIR»/ascii-jtex' Installing vflibcaps... make[1]: Leaving directory '/«PKGBUILDDIR»' # Remove RPATH from the generated library. (lintian) chrpath -d debian/tmp/usr/lib/libVFlib3.so.5.4.6 open: No such file or directory elf_open: Invalid argument make: *** [install] Error 1 dpkg-buildpackage: error: fakeroot debian/rules binary-arch gave error exit status 2 The attached patch fixes this issue. It updates few debian files and ltconfig (the same fix has been applied in Ubuntu on this file). Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/compat b/debian/compat --- a/debian/compat 2016-12-05 16:20:40.701369448 +0100 +++ b/debian/compat 2016-12-05 16:22:35.953673637 +0100 @@ -1 +1 @@ -5 +9 diff -Naur a/debian/control b/debian/control --- a/debian/control 2016-12-05 16:20:40.677369384 +0100 +++ b/debian/control 2016-12-05 16:22:22.401637846 +0100 @@ -8,7 +8,7 @@ Package: vflib3-dev Section: libdevel Architecture: any -Depends: vflib3 (= ${Source-Version}), libfreetype6-dev, libkpathsea-dev, libc6-dev +Depends: vflib3 (= ${source:Version}), libfreetype6-dev, libkpathsea-dev, libc6-dev Description: Development files for VFlib3 VFlib3 is a font rasterizer library for multi-lingual information processing. Using VFlib3, you can obtain bitmap data of characters(glyphs) diff -Naur a/ltconfig b/ltconfig --- a/ltconfig 2016-12-05 16:20:41.077370439 +0100 +++ b/ltconfig 2016-12-05 16:21:42.481532448 +0100 @@ -2006,11 +2006,7 @@ if test -f /lib/ld.so.1; then dynamic_linker='GNU ld.so' else -# Only the GNU ld.so supports shared libraries on MkLinux. -case "$host_cpu" in -powerpc*) dynamic_linker=no ;; -*) dynamic_linker='Linux ld.so' ;; -esac +dynamic_linker='Linux ld.so' fi ;;
Bug#847090: src:simbody: FTBFS on ppc64el
Package: src:simbody Version: 3.5.3+dfsg-1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, it fails with this message: /«BUILDDIR»/simbody-3.5.3+dfsg/SimTKcommon/src/ParallelExecutor.cpp:174:27: fatal error: windows.h: No such file or directory compilation terminated. SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/build.make:281: recipe for target 'SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/src/ParallelExecutor.cpp.o' failed make[3]: *** [SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/__/src/ParallelExecutor.cpp.o] Error 1 make[3]: *** Waiting for unfinished jobs make[3]: Leaving directory '/«BUILDDIR»/simbody-3.5.3+dfsg/obj-powerpc64le-linux-gnu' CMakeFiles/Makefile2:1156: recipe for target 'SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/all' failed make[2]: *** [SimTKcommon/sharedTarget/CMakeFiles/SimTKcommon.dir/all] Error 2 make[2]: Leaving directory '/«BUILDDIR»/simbody-3.5.3+dfsg/obj-powerpc64le-linux-gnu' Makefile:141: recipe for target 'all' failed make[1]: *** [all] Error 2 make[1]: Leaving directory '/«BUILDDIR»/simbody-3.5.3+dfsg/obj-powerpc64le-linux-gnu' dh_auto_build: make -j4 returned exit code 2 debian/rules:30: recipe for target 'build-arch' failed make: *** [build-arch] Error 2 This can be fixed by using the __linux__ macro instead of __linux. The attached patch, applied in Ubuntu, fixes this issue. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/patches/fix-cpp-macros.diff b/debian/patches/fix-cpp-macros.diff --- a/debian/patches/fix-cpp-macros.diff1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/fix-cpp-macros.diff2016-12-05 14:44:55.257836328 +0100 @@ -0,0 +1,21 @@ +diff -Naur a/SimTKcommon/src/ParallelExecutor.cpp b/SimTKcommon/src/ParallelExecutor.cpp +--- a/SimTKcommon/src/ParallelExecutor.cpp 2016-12-05 14:18:01.125575391 +0100 b/SimTKcommon/src/ParallelExecutor.cpp 2016-12-05 14:28:32.259231919 +0100 +@@ -167,7 +167,7 @@ +#include +#include + #else +- #ifdef __linux ++ #ifdef __linux__ + #include + #include +#else +@@ -187,7 +187,7 @@ +return(1); + } + #else +-#ifdef __linux ++#ifdef __linux__ + long nProcessorsOnline = sysconf(_SC_NPROCESSORS_ONLN); + if( nProcessorsOnline == -1 ) { + return(1); diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2016-12-05 14:18:01.133575412 +0100 +++ b/debian/patches/series 2016-12-05 14:45:23.381910979 +0100 @@ -1 +1,2 @@ fix_ppc64el.patch +fix-cpp-macros.diff
Bug#841062: installation-reports
Package: installation-reports Boot method: ISO image Image version: http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso Date: Mon Oct 17 00:44:56 2016 Machine: qemu VM / P8 baremetal / powerVM Processor: ppc64el Memory: 4Gb Partitions: /dev/sda1 JFS (more than 10Gb) /dev/sda3 swap Initial boot: [O] Detect network card:[O] Configure network: [O] Detect CD: [O] Load installer modules: [O] Detect hard drives: [O] Partition hard drives: [O] Install base system:[O] Clock/timezone setup: [O] User/password setup:[O] Install tasks: [O] Install boot loader:[E] Overall install:[E] Comments/Problems: When partitionning the disk, I chose the guided partitionning to use the entire disk and one partition, then I changed the file system of the main partition to JFS instead of ext4. Everything went right until the grub installation. It failed with: Install the GRUB boot loader on a hard disk --- !! ERROR: Unable to install GRUB in /dev/sda1 Executing 'grub-install /dev/sda1' failed. This is a fatal error. from /var/log/syslog: Oct 17 00:51:19 grub-installer: info: Installing grub on '/dev/sda1' Oct 17 00:51:19 grub-installer: info: grub-install does not support --no-floppy Oct 17 00:51:19 grub-installer: info: Running chroot /target grub-install --force "/dev/sda1" Oct 17 00:51:19 grub-installer: Installing for powerpc-ieee1275 platform. Oct 17 00:51:20 grub-installer: grub-install: error: Oct 17 00:51:20 grub-installer: unknown filesystem. Oct 17 00:51:20 grub-installer: error: Running 'grub-install --force "/dev/sda1"' failed. Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 3 (pipe:[9531]) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 4 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 5 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): File descriptor 6 (/dev/pts/4) leaked on lvdisplay invocation. Parent PID 5736: /bin/sh Oct 17 01:09:20 main-menu[974]: (process:5214): Volume group "sda" not found Oct 17 01:09:20 main-menu[974]: (process:5214): Cannot process volume group sda Oct 17 01:09:20 main-menu[974]: WARNING **: Configuring 'grub-installer' failed with error code 1 Oct 17 01:09:20 main-menu[974]: WARNING **: Menu item 'grub-installer' failed.
Bug#839643: src:rustc: ppc64el is missing
Package: src:rustc Version: 1.11.0+dfsg1-3 Severity: normal Dear Maintainer, I tried to build the package. I followed the guidelines from debian/README.Debian, but I hit an issue: $ upstream_bootstrap_arch=ppc64el debian/rules source_orig-dl QUILT_PATCHES=debian/patches quilt push -aq; x=$?; if [ $x = 2 ]; then exit 0; else exit $x; fi Applying patch debian/patches/rust-gdb-paths Applying patch debian/patches/rust-lldb-paths Applying patch debian/patches/add-soname Applying patch debian/patches/avoid-redundant-dls.diff Applying patch debian/patches/dont-download-stage0.diff Applying patch debian/patches/reproducible-dl-stage0.patch Applying patch debian/patches/fix-configure-for-deb-arches.patch Applying patch debian/patches/ignore-failing-armhf-tests_01.patch Applying patch debian/patches/ignore-failing-armhf-tests_02.patch Applying patch debian/patches/ignore-failing-armhf-tests_03.patch Applying patch debian/patches/ignore-failing-armhf-tests_04.patch Applying patch debian/patches/dynamic-link-llvm.patch Applying patch debian/patches/if-local-rust-same-version-then-force-local-rebuild.patch Applying patch debian/patches/ignore-stdcall-test-on-arm64.patch Applying patch debian/patches/fix-non-x86-doc-tests.patch Applying patch debian/patches/nodoc-for-build-arch.patch Now at patch debian/patches/nodoc-for-build-arch.patch /usr/bin/make -f debian/rules clean make[1]: Entering directory '/root/r/t/rustc-1.11.0' dh clean --parallel dh_testdir debian/rules override_dh_auto_clean make[2]: Entering directory '/root/r/t/rustc-1.11.0' set -e; \ if [ -f Makefile ]; then \ /usr/bin/make clean-all; \ rm -f Makefile config.stamp config.mk; \ fi rm -f src/rt/hoedown/src/html_blocks.c # clean up after building this ourselves rm -f src/bootstrap/bootstrap.pyc make[2]: Leaving directory '/root/r/t/rustc-1.11.0' dh_clean make[1]: Leaving directory '/root/r/t/rustc-1.11.0' debian/make_orig-dl_tarball.sh downloading https://static.rust-lang.org/dist/2016-07-05/rustc-1.10.0-powerpc64le-unknown-linux-gnu.tar.gz.sha256 to dl/rustc-1.10.0-powerpc64le-unknown-linux-gnu.tar.gz.sha256 % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3430 3430 0295 0 --:--:-- 0:00:01 --:--:-- 295 downloading https://static.rust-lang.org/dist/2016-07-05/rustc-1.10.0-powerpc64le-unknown-linux-gnu.tar.gz to /tmp/tmpvObYaP % Total% Received % Xferd Average Speed TimeTime Time Current Dload Upload Total SpentLeft Speed 100 3360 3360 0502 0 --:--:-- --:--:-- --:--:-- 502 verifying /tmp/tmpvObYaP removing /tmp/tmpvObYaP Traceback (most recent call last): File "src/etc/get-stage0.py", line 46, in main(sys.argv[1]) File "src/etc/get-stage0.py", line 34, in main bootstrap.get(url, dst, use_local_hash_if_present=True) File "/root/r/t/rustc-1.11.0/src/bootstrap/bootstrap.py", line 44, in get if not verify(temp_path, sha_path, verbose): File "/root/r/t/rustc-1.11.0/src/bootstrap/bootstrap.py", line 75, in verify expected, _ = f.readline().split() ValueError: too many values to unpack debian/rules:209: recipe for target 'source_orig-dl' failed make: *** [source_orig-dl] Error 1 It seems the tarball for ppc64el doesn't exist (pretty obvious). I'd be glad to help to enable rustc on ppc64el. Regards, Erwan.
Bug#834601: installation-reports
Package: installation-reports Boot method: ISO image Image version: http://cdimage.debian.org/mirror/cdimage/daily-builds/daily/current/ppc64el/iso-cd/debian-testing-ppc64el-netinst.iso Date: Wed Aug 17 07:44:46 CEST 2016 Machine: qemu VM Processor: ppc64el Memory: 4Gb Initial boot: [O] Detect network card:[ ] Configure network: [ ] Detect CD: [ ] Load installer modules: [ ] Detect hard drives: [ ] Partition hard drives: [ ] Install base system:[ ] Clock/timezone setup: [ ] User/password setup:[ ] Install tasks: [ ] Install boot loader:[ ] Overall install:[ ] Comments/Problems: Right after the Grub menu, I got glitches in the screens to choose the language and the next ones. The top menu isn't well refreshed and the list of locations isn't displayed properly. I've gotten this issue since the 12th of July. Here some "screenshots": The installer menu: ┌┤ [!] Debian installer main menu ├┐ │ │ │ Choose the next step in the install process: │ │ │ │ Choose language │ │ Access software for a blind person using a braille display │ │ Configure the keyboard │ │ Detect and mount CD-ROM │ │ Load installer components from CD │ │ Change debconf priority │ │ Check the CD-ROM(s) integrity │ │ Save debug logs │ │ Execute a shell │ │ Abort the installation │ │ │ └──┘ moves; selects; activates buttons The top menu is missing (and some edges too): ──┤ [!!] Select a language ├┐ │ Choose the language to be used for the installation process. The│ selected language will also be the default language for the installed │ system. │ │ Language: │ │ C │ Basque ▒ │ Catalan │ Danish ▒ │ Dutch▒ │ English ▒ │ Finnish ▒ │ French │ │ │ │ └─┘ moves; selects; activates buttons After about 20 seconds the top menu appears: [(1*installer) 2 shell 3 shell 4- log ][ Aug 17 7:44 ] ──┤ [!!] Select a language ├┐ │ Choose the language to be used for the installation process. The│ selected language will also be the default language for the installed │ system. │ │ Language: │ │ C │ Basque ▒ │ Catalan │ Danish ▒ │ Dutch▒ │ English ▒ │ Finnish ▒ │
Bug#813817: src:pyg: FTBFS on ppc64el
Package: src:pyg Version: 0.9.8 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, it failed: make[4]: Entering directory '/root/pyg-0.9.8/wlp/module' make[4]: *** No rule to make target '/usr/lib/python2.7/config/Makefile', needed by 'sedscript'. Stop. make[4]: Leaving directory '/root/pyg-0.9.8/wlp/module' Makefile.pre.in:295: recipe for target 'boot' failed make[3]: *** [boot] Error 2 In Ubuntu, a similiar patch than the one provided was applied to achieve the following: * Fix build failure with python in multiarch location. * adapt /wlp/C/Makefile for multiarched libfl.a * include required string.h in wlp/C/commands.l Thanks for considering the patch. Erwan Prioul. diff -Naur a/wlp/C/commands.l b/wlp/C/commands.l --- a/wlp/C/commands.l 2016-02-05 15:03:38.516765954 +0100 +++ b/wlp/C/commands.l 2016-02-05 15:29:23.808118531 +0100 @@ -4,6 +4,7 @@ #include "commands.tab.h" /*#define DEBUG*/ #include "macro.h" +#include %} OWNER "<"[a-zA-Z0-9_.+-]+@[a-zA-Z0-9._-]+">" diff -Naur a/wlp/C/Makefile b/wlp/C/Makefile --- a/wlp/C/Makefile 2016-02-05 15:03:38.512765955 +0100 +++ b/wlp/C/Makefile 2016-02-05 15:29:23.808118531 +0100 @@ -17,21 +17,23 @@ SRCDIR=. BINDIR=. +DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) + OBJFILE=structs.o commands.tab.o lex.yy.o all: archive bin # archive file for python module -archive: structs bison flex /usr/lib/libfl.a macro.h structs.h commands.tab.h +archive: structs bison flex macro.h structs.h commands.tab.h $(AR) $(AROPTS) $(BINDIR)/wlp.a $(OBJFILE) \ - /usr/lib/libfl.a + /usr/lib/$(DEB_HOST_MULTIARCH)/libfl.a # binary (executable) file for testing executable: bin -bin: structs bison flex /usr/lib/libfl.a macro.h structs.h commands.tab.h +bin: structs bison flex macro.h structs.h commands.tab.h $(CC) $(CCSHARED) $(CCOPTS) $(OBJFILE) \ - yytest.c /usr/lib/libfl.a -o ./yytest + yytest.c /usr/lib/$(DEB_HOST_MULTIARCH)/libfl.a -o ./yytest flex: $(FLEX) $(FLEXOPTS) commands.l diff -Naur a/wlp/module/Makefile.pre.in b/wlp/module/Makefile.pre.in --- a/wlp/module/Makefile.pre.in 2016-02-05 15:03:38.520765953 +0100 +++ b/wlp/module/Makefile.pre.in 2016-02-05 15:29:23.808118531 +0100 @@ -166,6 +166,7 @@ DESTSHARED= $(BINLIBDEST)/site-packages LIBPL= $(LIBP)/config +LIBPL= $(shell python$(VERSION)-config --configdir) PYTHONLIBS= $(LIBPL)/libpython$(VERSION).a
Bug#779672: patch to fix Multi-Line Architecture fields
Here is a very small patch (using linux-any) to fix the issue. Erwan. diff -Naur a/debian/control b/debian/control --- a/debian/control2016-02-04 17:19:35.952421456 +0100 +++ b/debian/control2016-02-04 17:20:04.896499097 +0100 @@ -10,8 +10,7 @@ X-Python-Version: >= 2.7 Package: calendarserver -Architecture: alpha amd64 arm64 armel armhf hppa i386 m68k mips mipsel powerpc - ppc64 ppc64el s390x sparc x32 +Architecture: linux-any Depends: ${shlibs:Depends}, ${misc:Depends}, ${python:Depends}, memcached, python-zope.interface (>= 4), python-openssl (>= 0.9), python-kerberos, python-xattr (>= 0.5), python-pygresql (>= 4.1.1),
Bug#813593: Acknowledgement (src:memcached: FTBFS on ppc64el)
My bad, the given patch achieves this: * debian/patches/disable_slabs_test.patch: disable unreliable test.
Bug#813593: src:memcached: FTBFS on ppc64el
Package: src:memcached Version: 1.4.25-1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, tests are failing. In Ubuntu, a similiar patch than the one provided was applied to achieve the following: * debian/patches/fix-distribution.patch: added patch to show distribution on version (updated to make merging easier). Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/patches/disable_slabs_test.patch b/debian/patches/disable_slabs_test.patch --- a/debian/patches/disable_slabs_test.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/disable_slabs_test.patch 2016-02-03 14:51:04.920279212 +0100 @@ -0,0 +1,113 @@ +Description: disable unreliable test +Author: Marc Deslauriers <marc.deslauri...@canonical.com> + +Index: memcached-1.4.25/t/slabs-reassign2.t +=== +--- memcached-1.4.25.orig/t/slabs-reassign2.t 2015-11-19 20:18:56.0 -0500 /dev/null 1970-01-01 00:00:00.0 + +@@ -1,105 +0,0 @@ +-#!/usr/bin/perl +- +-use strict; +-use warnings; +-use Test::More tests => 11; +-use FindBin qw($Bin); +-use lib "$Bin/lib"; +-use MemcachedTest; +- +-my $server = new_memcached('-m 60 -o slab_reassign,slab_automove=2,lru_crawler,lru_maintainer'); +-my $sock = $server->sock; +- +-my $value = "B"x11000; +-my $keycount = 5000; +- +-my $res; +-for (1 .. $keycount) { +-print $sock "set nfoo$_ 0 0 11000 noreply\r\n$value\r\n"; +-} +- +-my $todelete = 0; +-{ +-my $stats = mem_stats($sock); +-cmp_ok($stats->{curr_items}, '>', 4000, "stored at least 4000 11k items"); +-$todelete = $stats->{curr_items} / 2; +-#for ('evictions', 'reclaimed', 'curr_items', 'cmd_set', 'bytes') { +-#print STDERR "$_: ", $stats->{$_}, "\n"; +-#} +-} +- +-# Make room in old class so rescues can happen when we switch slab classes. +-for (1 .. $todelete) { +-print $sock "delete nfoo$_ noreply\r\n"; +-} +- +-$value = "B"x7000; +-for (1 .. $keycount) { +-print $sock "set ifoo$_ 0 0 7000 noreply\r\n$value\r\n"; +-} +- +-my $missing = 0; +-my $hits = 0; +-for (1 .. $keycount) { +-print $sock "get ifoo$_\r\n"; +-my $body = scalar(<$sock>); +-my $expected = "VALUE ifoo$_ 0 7000\r\n$value\r\nEND\r\n"; +-if ($body =~ /^END/) { +-$missing++; +-} else { +-$body .= scalar(<$sock>) . scalar(<$sock>); +-if ($body ne $expected) { +-print STDERR "Something terrible has happened: $expected\nBODY:\n$body\nDONETEST\n"; +-} else { +-$hits++; +-} +-} +-} +-#print STDERR "HITS: $hits, MISSES: $missing\n"; +- +-{ +-my $stats = mem_stats($sock); +-cmp_ok($stats->{evictions}, '<', 2000, 'evictions were less than 2000'); +-#for ('evictions', 'reclaimed', 'curr_items', 'cmd_set', 'bytes') { +-#print STDERR "$_: ", $stats->{$_}, "\n"; +-#} +-} +- +-cmp_ok($hits, '>', 4000, 'were able to fetch back 2/3rds of 8k keys'); +-my $stats_done = mem_stats($sock); +-cmp_ok($stats_done->{slab_reassign_rescues}, '>', 0, 'some reassign rescues happened'); +-cmp_ok($stats_done->{slab_reassign_evictions_nomem}, '>', 0, 'some reassign evictions happened'); +- +-print $sock "flush_all\r\n"; +-is(scalar <$sock>, "OK\r\n", "did flush_all"); +-my $tries; +-for ($tries = 20; $tries > 0; $tries--) { +-sleep 1; +-my $stats = mem_stats($sock); +-if ($stats->{slab_global_page_pool} == 56) { +-last; +-} +-} +-cmp_ok($tries, '>', 0, 'reclaimed 61 pages before timeout'); +- +-{ +-my $stats = mem_stats($sock, "slabs"); +-is($stats->{total_malloced}, 62914560, "total_malloced is what we expect"); +-} +- +-# Set into an entirely new class. Overload a bit to try to cause problems. +-$value = "B"x4096; +-for (1 .. $keycount * 4) { +-print $sock "set jfoo$_ 0 0 4096 noreply\r\n$value\r\n"; +-} +- +-{ +-my $stats = mem_stats($sock); +-cmp_ok($stats->{curr_items}, '>', 1, "stored at least 1 4k items"); +-is($stats->{slab_global_page_pool}, 0, "drained the global page pool"); +-} +- +-{ +-my $stats = mem_stats($sock, "slabs"); +-is($stats->{total_malloced}, 62914560, "total_malloced is same after re-assignment"); +-} diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2016-02-03 14:46:29.309396624 +0100 +++ b/debian/patches/series 2016-02-03 14:49:14.840749414 +0100 @@ -4,3 +4,4 @@ 04_add_init_retry.patch 06_eol_comment_handling.patch 07_disable_tests.patch +disable_slabs_test.patch
Bug#798652: scilab: scilab doesn't work on ppc64el: could not find the Java configuration for the model <>
Package: scilab Version: 5.5.2-1 Severity: normal While scilab is available on ppc64el, it doesn't actually work: > $ /usr/bin/scilab > Could not find the Java configuration for the model . Please contact > us on http://bugzilla.scilab.org > /usr/bin/scilab-bin: error while loading shared libraries: libjava.so: cannot > open shared object file: No such file or directory I apply this patch to get rid of the error: > --- scilab-5.5.2.orig/bin/scilab > +++ scilab-5.5.2/bin/scilab > @@ -528,7 +528,7 @@ > "ppc"|"powerpc") > proc="ppc" > ;; > -"ppc64"|"ppc64el") > +"ppc64"|"ppc64el"|"ppc64le") > proc="ppc64" > ;; > "s390") Unfortunately, we then get another error: > $ /usr/bin/scilab > Could not create a Scilab main class. Error: > Exception in thread "main" java.lang.ExceptionInInitializerError > at javax.media.opengl.GLProfile.(GLProfile.java:120) > at org.scilab.modules.gui.SwingView.(Unknown Source) > at org.scilab.modules.gui.SwingView.registerSwingView(Unknown Source) > at org.scilab.modules.core.Scilab.(Unknown Source) > Caused by: java.lang.RuntimeException: Please port CPU detection to your > platform (linux/ppc64) > at > jogamp.common.os.PlatformPropsImpl.getCPUTypeImpl(PlatformPropsImpl.java:304) > at > jogamp.common.os.PlatformPropsImpl.(PlatformPropsImpl.java:134) > ... 4 more > > Scilab cannot create Scilab Java Main-Class (we have not been able to find > the main Scilab class. Check if the Scilab and thirdparty packages are > available). Thanks, Erwan.
Bug#798651: getfem++: FTBFS on ppc64el: Could not find the Java configuration for the model
Package: getfem++ Version: 4.2.1~beta1~svn4635~dfsg-5 Severity: normal Dear Maintainer, getfem++ doesn't build on ppc64el. Let me know if you need any details. > powerpc64le-linux-gnu-gcc -pthread -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -fno-strict-aliasing -Wall -g -O2 > -fstack-protector-strong -Wformat -Werror=format-security -O3 > -D_FORTIFY_SOURCE=2 -DGMM_USES_BLAS -I/usr/include -I/usr/include -fPIC > -I../../../src/getfem -I../../../src/getfem -I./.. -I. > -I/usr/lib/python2.7/dist-packages/numpy/core/include > -I/usr/include/python2.7 -c getfem_python_c.c -o ./getfem_python_c.o > In file included from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarraytypes.h:1804:0, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/ndarrayobject.h:17, > from > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/arrayobject.h:4, > from getfem_python_c.c:22: > /usr/lib/python2.7/dist-packages/numpy/core/include/numpy/npy_1_7_deprecated_api.h:15:2: > warning: #warning "Using deprecated NumPy API, disable it by " "#defining > NPY_NO_DEPRECATED_API NPY_1_7_API_VERSION" [-Wcpp] > #warning "Using deprecated NumPy API, disable it by " \ > ^ > powerpc64le-linux-gnu-gcc -pthread -shared -Wl,-O1 -Wl,-Bsymbolic-functions > -Wl,-z,relro -fno-strict-aliasing -DNDEBUG -g -fwrapv -O2 -Wall > -Wstrict-prototypes -D_FORTIFY_SOURCE=2 -g -fstack-protector-strong -Wformat > -Werror=format-security -Wl,-z,relro -Wall -g -O2 -fstack-protector-strong > -Wformat -Werror=format-security -O3 -D_FORTIFY_SOURCE=2 -DGMM_USES_BLAS > -I/usr/include -I/usr/include ./getfem_python_c.o -L../.libs > -L../../../src/.libs -lgetfemint -lgetfem -lzmumps_seq -lcmumps_seq > -ldmumps_seq -lsmumps_seq -lmuparser -lqhull -lsuperlu -lblas -lsuperlu > -lmetis -lstdc++ -lm -o ./_getfem.so > make[6]: Leaving directory > '/build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/python' > Making all in scilab > make[6]: Entering directory > '/build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/scilab' > SCI_DISABLE_TK=1 SCI_JAVA_ENABLE_HEADLESS=1 scilab -nw -nb -f > /build/getfem++-QE2FtB/getfem++-4.2.1~beta1~svn4635~dfsg/interface/src/scilab/makefile_builder.sce > Could not find the Java configuration for the model . Please contact > us on http://bugzilla.scilab.org > /usr/bin/scilab-bin: error while loading shared libraries: libjava.so: cannot > open shared object file: No such file or directory > Makefile:893: recipe for target 'all' failed > make[6]: *** [all] Error 127 It seems the bug is in scilab. I'll file a bug. Maybe it would be good to leave this bug open until scilab is fixed, and then we can check if this package works on ppc64el. Thanks, Erwan.
Bug#797792: src:r-base: incomplete FLIBS prevents to build a package depending on r-base-core
Package: src:r-base Version: 3.2.2-1 Severity: normal Tags: patch Dear Maintainer, I've noticed that r-cran-bayesm can't be built on ppc64el. It's because some library paths are missing from the FLIBS variable defined in /etc/R/Makeconf. The file /etc/R/Makeconf is coming from the package r-base-core. The attached patch adds the missing paths to FLIBS, only for ppc64el. This way the package r-cran-bayesm could be built. Thanks for considering the patch. Erwan Prioul. diff -Naur a/configure b/configure --- a/configure 2015-08-13 16:47:29.565087740 +0200 +++ b/configure 2015-09-02 14:56:33.701599837 +0200 @@ -26516,6 +26516,13 @@ main_ldflags="-Wl,--export-dynamic" STATICR1="-Wl,--whole-archive" STATICR2="-Wl,--no-whole-archive" +## FLIBS needs all the -L options on powerpc64le +## (it enables the build of packages with a dependency on this one) +case "${host_cpu}" in + powerpc64le) +FLIBS_IN_SO="${FLIBS_IN_SO} $CLIBS" +;; +esac ;; mingw*) SHLIB_EXT=".dll"
Bug#795478: src:angband: use autotools-dev to fix FTBFS on ppc64el
Package: src:angband Version: 1:3.5.1-2 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Really use autotools-dev. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2015-08-14 12:08:12.977386255 +0200 +++ b/debian/rules 2015-08-14 12:09:08.977383279 +0200 @@ -23,7 +23,7 @@ include /usr/share/dpkg/buildflags.mk %: - dh $@ + dh $@ --with autotools_dev override_dh_auto_clean:
Bug#795367: src:mruby: FTBFS on ppc64el
Package: src:mruby Version: 1.1.0+20150807+git4fdf4922-1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, the tests fail: Total: 853 OK: 852 KO: 1 Crash: 0 Time: 0.39 seconds rake aborted! Command Failed: [build/host/test/mrbtest -v] Rakefile:122:in `block (2 levels) in top (required)' make[1]: *** [test] Error 1 dh_auto_test: make -j1 test returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Makefile:12: recipe for target 'test' failed make[1]: Leaving directory '/«BUILDDIR»/mruby-1.1.0+20150807+git4fdf4922' It seems coming from the options given to gcc, especially those ones: -g3 -O0. As said in documention: GCC allows you to use -g with -O. The shortcuts taken by optimized code may occasionally produce surprising results. In this case, for ppc64el, it makes fail a test with large doubles and prevents the packages to be built. The attached patch removes the -O0 option when building the package for ppc64el architecture. Thanks for considering this patch. Regards, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16.0-4-powerpc64le Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/patches/ppc64el.patch b/debian/patches/ppc64el.patch --- a/debian/patches/ppc64el.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/ppc64el.patch 2015-08-13 13:00:26.273811806 +0200 @@ -0,0 +1,13 @@ +diff -Naur a/tasks/mruby_build.rake b/tasks/mruby_build.rake +--- a/tasks/mruby_build.rake 2015-08-13 12:55:56.705826133 +0200 b/tasks/mruby_build.rake 2015-08-13 12:59:50.785813692 +0200 +@@ -100,7 +100,8 @@ + compilers.each do |c| + c.defines += %w(MRB_DEBUG) + if toolchains.any? { |toolchain| toolchain == gcc } +- c.flags += %w(-g3 -O0) ++ c.flags += %w(-g3) ++ c.flags += %w(-O0) if ENV['DEB_TARGET_ARCH'] != 'ppc64el' + end + end + @mrbc.compile_options += ' -g' diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2015-08-13 12:55:56.725826132 +0200 +++ b/debian/patches/series 2015-08-13 13:02:44.593804455 +0200 @@ -1 +1,2 @@ enable_verbose_build.patch +ppc64el.patch
Bug#791347: src:libexplain: FTBFS on ppc64el
Package: src:libexplain Version: 1.4.D001-2 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, the test t0056a fails on an error related with the O_LARGEFILE flag. PATH=`pwd`/bin:$PATH /bin/sh test/00/t0056a.sh 3c3 which is unsuitable for writing (O_RDONLY | O_LARGEFILE) --- which is unsuitable for writing (O_RDONLY | 020) FAILED test of write vs EINVAL make[1]: *** [t0056a] Error 1 Makefile:40798: recipe for target 't0056a' failed make[1]: Leaving directory '/«PKGBUILDDIR»' dh_auto_test: make -j1 check returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 The attached patch includes a workaround to set O_LARGEFILE_HIDDEN to the proper value on ppc64el architecture. Thanks for considering this patch. Regards, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.16.0-4-powerpc64le Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/patches/ppc64el-largefile.patch b/debian/patches/ppc64el-largefile.patch --- a/debian/patches/ppc64el-largefile.patch1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/ppc64el-largefile.patch2015-07-03 17:44:40.517180785 +0200 @@ -0,0 +1,16 @@ +diff -Naur a/libexplain/ac/fcntl.h b/libexplain/ac/fcntl.h +--- a/libexplain/ac/fcntl.h2015-07-03 17:24:03.657246523 +0200 b/libexplain/ac/fcntl.h2015-07-03 17:31:13.741223664 +0200 +@@ -58,7 +58,12 @@ + * flags values returned by the kernel. + */ + #if defined(__linux__) (O_LARGEFILE == 0) ++#if !defined(__PPC64__) + #define O_LARGEFILE_HIDDEN 010 ++#else ++/* workaround for ppc64el */ ++#define O_LARGEFILE_HIDDEN 020 ++#endif + #endif + + diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2015-07-03 17:24:02.861246565 +0200 +++ b/debian/patches/series 2015-07-03 17:34:19.833213774 +0200 @@ -1,2 +1,3 @@ autofoo.patch alpha-fcntl-h.patch +ppc64el-largefile.patch
Bug#789945: [PATCH] libmodplug:
On 06/25/2015 08:27 PM, Zed Pobre wrote: On Thu, Jun 25, 2015 at 04:03:07PM +0200, Erwan Prioul wrote: Source: libmodplug Source-Version: 1:0.8.8.5-1 Tags: patch This light change enables the build for the ppc64el architecture. Thanks for considering it. [...] rm -f build-stamp configure-stamp + rm -f config.guess config.sub rm -f compile config.h.in config.log conftest conftest.o ltconfig dh_clean Well, I *can* do this, but I'm really curious about what's breaking. This change will delete two pre-existing files during the clean process that are modified during the build process. What you end up with is still not what you started with, and the build process should overwrite them regardless. Why is ppc64el breaking? Is this something specific to an autobuilder? The build on ppc64el ends like this: configure: error: cannot guess build type; you must specify one make: *** [configure-stamp] Error 1 checking build system type... debian/rules:17: recipe for target 'configure-stamp' failed There is no entry for the ppc64el architecture in the config.sub and config.guess files. The files aren't overwritten as expected during the build process. That's why my patch removes them, kind of ugly way to get recent version of these files. I've reworked my patch (in attachment) to use dh_autotools-dev_updateconfig and dh_autotools-dev_restoreconfig instead of rm. I hope this new patch is better than the previous one. Regards, Erwan. Index: libmodplug-1:0.8.8.5-1/debian/rules === --- libmodplug-1:0.8.8.5-1/debian/rules +++ libmodplug-1:0.8.8.5-1/debian/rules @@ -15,8 +15,9 @@ configure: configure-stamp configure-stamp: dh_testdir + dh_autotools-dev_updateconfig libtoolize --copy --force aclocal autoconf autoheader @@ -42,8 +43,9 @@ dh_testdir test ! -f Makefile || $(MAKE) distclean rm -f build-stamp configure-stamp rm -f compile config.h.in config.log conftest conftest.o ltconfig + dh_autotools-dev_restoreconfig dh_clean install: build dh_testdir
Bug#789945: [PATCH] libmodplug:
Source: libmodplug Source-Version: 1:0.8.8.5-1 Tags: patch Hi, This light change enables the build for the ppc64el architecture. Thanks for considering it. Erwan. --- Index: libmodplug-1:0.8.8.5-1/debian/rules === --- libmodplug-1:0.8.8.5-1/debian/rules +++ libmodplug-1:0.8.8.5-1/debian/rules @@ -41,8 +41,9 @@ clean: dh_testdir test ! -f Makefile || $(MAKE) distclean rm -f build-stamp configure-stamp + rm -f config.guess config.sub rm -f compile config.h.in config.log conftest conftest.o ltconfig dh_clean install: build -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#746109: (no subject)
I was able to build the package according to the suggested fix from bug #745969 (thx Edmund). Thanks for considering the attached patch. Erwan. diff -Naur a/tokens.h b/tokens.h --- a/tokens.h 2014-12-29 16:18:19.442013464 +0100 +++ b/tokens.h 2014-12-29 16:26:12.782018555 +0100 @@ -93,7 +93,6 @@ extern int clex_lineno; extern FILE * yycin; extern char * yyctext; -extern int yycleng; extern int yyclength, yycsize; extern char * yyccomment; @@ -104,7 +103,6 @@ extern int plex_lineno; extern FILE * yypin; extern char * yyptext; -extern int yypleng; extern char * yypcomment; extern int yyplex(void); @@ -114,7 +112,6 @@ extern int perllex_lineno; extern FILE * yyperlin; extern char * yyperltext; -extern int yyperlleng; extern char * yyperlcomment; extern int yyperllex(void); @@ -123,7 +120,6 @@ extern int phplex_lineno; extern FILE * yyphpin; extern char * yyphptext; -extern int yyphpleng; extern char * yyphpcomment; extern int yyphplex(void); @@ -132,7 +128,6 @@ extern int rubylex_lineno; extern FILE * yyrubyin; extern char * yyrubytext; -extern int yyrubyleng; extern char * yyrubycomment; extern int yyrubylex(void);;
Bug#749354: (no subject)
Dear Maintainer, The attached patch fixes the GNUmakefile in the apps/certpatch directory. There were few typos leading to a failure when building the package. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/patches/08_gnumakefile.patch b/debian/patches/08_gnumakefile.patch --- a/debian/patches/08_gnumakefile.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/08_gnumakefile.patch 2014-12-10 15:00:27.183615507 +0100 @@ -0,0 +1,21 @@ +diff -Naur a/apps/certpatch/GNUmakefile b/apps/certpatch/GNUmakefile +--- a/apps/certpatch/GNUmakefile 2014-12-10 13:47:07.003568180 +0100 b/apps/certpatch/GNUmakefile 2014-12-10 15:00:03.159615249 +0100 +@@ -30,14 +30,14 @@ + # This code was written under funding by Ericsson Radio Systems. + # + ++.CURDIR:= $(shell pwd) + PROG= certpatch + SRCS= certpatch.c + BINDIR?= /usr/sbin +-TOPSRC= ${.CURDIR}../.. +-TOPOBJ!= cd ${TOPSRC}; printf all:\n\t@pwd\n |${MAKE} -f- ++TOPSRC= ${.CURDIR}/../.. ++TOPOBJ!= cd ${TOPSRC}; printf all:\n\t@pwd\n |${MAKE} --no-print-directory -f- + OS= linux + FEATURES!= awk '/^FEATURES=/ { print $$0 }' ${.CURDIR}/../../Makefile | sed 's/FEATURES=.//' +-.PATH: ${TOPSRC} ${TOPSRC}/sysdep/${OS} ${TOPOBJ} + CFLAGS+= -I${TOPSRC} -I${TOPSRC}/sysdep/${OS} -I${TOPOBJ} -Wall + LDFLAGS+= -lcrypto -lssl -lgmp + MAN= certpatch.8 diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-12-10 13:47:06.619568176 +0100 +++ b/debian/patches/series 2014-12-10 15:00:49.679615749 +0100 @@ -5,3 +5,4 @@ 05_openssl.patch 06_sysdep.patch 07_fix_ifreq_len.patch +08_gnumakefile.patch
Bug#759464: (no subject)
Dear Maintainer, The attached patch uses autotools-dev to fix the issue. To use dh-autoreconf it seems an update of configuration files is needed upstream. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev helper for newer arches to resolve FTBFS. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-12-09 11:31:47.138551557 +0100 +++ b/debian/control 2014-12-09 11:54:25.966566172 +0100 @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Christian Bayle ba...@debian.org -Build-Depends: debhelper ( 3.0), libx11-dev, x11proto-core-dev +Build-Depends: debhelper ( 3.0), libx11-dev, x11proto-core-dev, libtool, autoconf, autotools-dev Standards-Version: 3.6.2.0 Package: libibtk-dev diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-12-09 11:31:47.138551557 +0100 +++ b/debian/rules 2014-12-09 11:55:48.934567064 +0100 @@ -5,6 +5,8 @@ # Uncomment this to turn on verbose mode. #export DH_VERBOSE=1 +export AUTOMAKE=true + CFLAGS = -O2 -Wall ifneq (,$(findstring debug,$(DEB_BUILD_OPTIONS))) CFLAGS += -g @@ -22,6 +24,9 @@ configure: configure-stamp configure-stamp: dh_testdir + dh_autotools-dev_updateconfig + libtoolize -f -c -i + autoconf -f # Add here commands to configure the package. ./configure --enable-shared --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --sysconfdir=/etc @@ -46,6 +51,7 @@ -$(MAKE) clean -rm -f config.log + dh_autotools-dev_restoreconfig dh_clean install: build
Bug#753219: (no subject)
Dear Maintainer, The attached patch fix the line separator issue (thx to Juhani) and also replaces autotools-dev with dh-autoreconf (to follow this recommandation[1]). Thanks for considering the patch. Erwan Prioul. [1] https://wiki.debian.org/qa.debian.org/FTBFS#A2014-01-21_using_dh-autoreconf_during_the_build diff -Naur a/debian/control b/debian/control --- a/debian/control2014-09-11 15:19:25.432629600 +0200 +++ b/debian/control2014-09-11 15:58:31.768504894 +0200 @@ -4,7 +4,7 @@ Maintainer: Mohammed Sameer msam...@debian.org Build-Depends: autoconf, automake1.11, - autotools-dev, + dh-autoreconf, debhelper (= 7.1), iso-codes, libbz2-dev, diff -Naur a/debian/patches/fix_tooltip_crash.patch b/debian/patches/fix_tooltip_crash.patch --- a/debian/patches/fix_tooltip_crash.patch2014-09-11 15:19:25.456629598 +0200 +++ b/debian/patches/fix_tooltip_crash.patch2014-09-11 15:34:16.460582242 +0200 @@ -1,4 +1,5 @@ -Use the new Gtk::Tooltip API instead of the old Gtk::Tooltips API--- a/src/toolbar.cc +Use the new Gtk::Tooltip API instead of the old Gtk::Tooltips API +--- a/src/toolbar.cc +++ b/src/toolbar.cc @@ -94,26 +94,21 @@ #endif diff -Naur a/debian/patches/replace_fribidi-config_pkg-config.patch b/debian/patches/replace_fribidi-config_pkg-config.patch --- a/debian/patches/replace_fribidi-config_pkg-config.patch2014-09-11 15:19:25.456629598 +0200 +++ b/debian/patches/replace_fribidi-config_pkg-config.patch2014-09-11 15:34:16.460582242 +0200 @@ -1,4 +1,5 @@ -fribidi only ships fribidi.pc now. Patched configure.in--- a/configure.in +fribidi only ships fribidi.pc now. Patched configure.in +--- a/configure.in +++ b/configure.in @@ -145,14 +145,8 @@ fi diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-09-11 15:19:25.444629599 +0200 +++ b/debian/rules 2014-09-11 15:42:45.264555200 +0200 @@ -4,9 +4,10 @@ #export DH_VERBOSE=1 export AUTOMAKE = automake-1.11 +export ACLOCAL = aclocal-1.11 %: - dh $@ --with quilt,autotools_dev + dh $@ --with quilt,autoreconf override_dh_auto_configure: autoreconf -i
Bug#769281: src:wmlongrun: use autotools-dev to fix FTBFS on ppc64el
Package: src:wmlongrun Version: 0.3.0-pre1-4.2 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to resolve FTBFS on newer arches. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-11-12 13:08:25.859998912 +0100 +++ b/debian/control 2014-11-12 13:10:22.567992709 +0100 @@ -2,7 +2,7 @@ Section: x11 Priority: optional Maintainer: Francois Gurin mat...@debian.org -Build-Depends: debhelper ( 3.0.0), libx11-dev, libxext-dev, libxpm-dev, libxt-dev +Build-Depends: debhelper ( 3.0.0), libx11-dev, libxext-dev, libxpm-dev, libxt-dev, autotools-dev Standards-Version: 3.6.1.1 Package: wmlongrun diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-11-12 13:08:25.859998912 +0100 +++ b/debian/rules 2014-11-12 13:11:59.879987537 +0100 @@ -23,6 +23,7 @@ config.status: configure dh_testdir + dh_autotools-dev_updateconfig # Add here commands to configure the package. ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info @@ -44,14 +45,10 @@ rm -f build-stamp # Add here commands to clean up after the build process. - ./configure - -$(MAKE) distclean - -test -r /usr/share/misc/config.sub \ - cp -f /usr/share/misc/config.sub config.sub - -test -r /usr/share/misc/config.guess \ - cp -f /usr/share/misc/config.guess config.guess + [ -f Makefile ] $(MAKE) distclean || true + dh_autotools-dev_restoreconfig dh_clean install: build
Bug#769286: src:xprobe: use autotools-dev to fix FTBFS on ppc64el
Package: src:xprobe Version: 0.3-1.1 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to resolve FTBFS on newer arches. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-11-12 13:38:49.163902005 +0100 +++ b/debian/control 2014-11-12 13:40:46.987895742 +0100 @@ -2,7 +2,7 @@ Section: net Priority: extra Maintainer: Richard Atterer atte...@debian.org -Build-Depends: debhelper ( 4), libpcap-dev (= 0.7.1) +Build-Depends: debhelper ( 4), libpcap-dev (= 0.7.1), autotools-dev Standards-Version: 3.5.9 Package: xprobe diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-11-12 13:38:49.159902005 +0100 +++ b/debian/rules 2014-11-12 13:40:22.823897027 +0100 @@ -6,8 +6,7 @@ configure: configure-stamp configure-stamp: dh_testdir src/xprobe.cc - ln -s ../../../../cfg-scripts/config.guess libs-external/USI++/src/cfgaux - ln -s ../../../../cfg-scripts/config.sub libs-external/USI++/src/cfgaux + dh_autotools-dev_updateconfig ./configure --prefix=/usr --mandir=/usr/share/man --sysconfdir=/etc touch configure-stamp @@ -24,8 +23,7 @@ dh_testroot rm -f build-stamp configure-stamp -$(MAKE) distclean - rm -f libs-external/USI++/src/cfgaux/config.guess - rm -f libs-external/USI++/src/cfgaux/config.sub + dh_autotools-dev_restoreconfig dh_clean install: build
Bug#769300: src:ussp-push: use autotools-dev to fix FTBFS on ppc64el
Package: src:ussp-push Version: 0.11-1 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to resolve FTBFS on newer arches. Thanks for considering the patch. Erwan Prioul. diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-11-12 16:04:53.947436164 +0100 +++ b/debian/control 2014-11-12 16:16:18.071399804 +0100 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Hendrik Sattler deb...@hendrik-sattler.de Uploaders: Simon Richter s...@debian.org -Build-Depends: debhelper (= 7.0.0), libbluetooth-dev, libopenobex1-dev, pkg-config, xsltproc, docbook-xsl, docbook-xml, quilt (= 0.45) +Build-Depends: debhelper (= 7.0.0), libbluetooth-dev, libopenobex1-dev, pkg-config, xsltproc, docbook-xsl, docbook-xml, quilt (= 0.45), autotools-dev Standards-Version: 3.8.1.0 Package: ussp-push diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-11-12 16:04:53.943436164 +0100 +++ b/debian/rules 2014-11-12 16:15:02.259403833 +0100 @@ -23,6 +23,7 @@ build-arch: build-arch-stamp build-arch-stamp: $(QUILT_STAMPFN) dh_testdir + dh_autotools-dev_updateconfig mkdir -p $(CURDIR)/debian/build cd $(CURDIR)/debian/build \ $(CURDIR)/configure --srcdir=$(CURDIR) --prefix=/usr @@ -42,6 +43,7 @@ rm -rf $(CURDIR)/debian/tmp rm -rf $(CURDIR)/debian/build debian/rules unpatch + dh_autotools-dev_restoreconfig dh_clean install: build
Bug#766366: src:choreonoid: FTBFS on ppc64el: cast from pointer to udword loses precision
Package: src:choreonoid Version: 1.1.0+dfsg-6.1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, I got this error: BUILDDIR/choreonoid-1.1.0+dfsg/src/Collision/Opcode/OPC_OptimizedTree.cpp:579:35: error: cast from ‘Opcode::AABBCollisionNode*’ to ‘udword {aka unsigned int}’ loses precision [-fpermissive] udword Nb = (Data - udword(Nodes))/Nodes[i].GetNodeSize(); The issue seems to come from OPC_OptimizedTree.cpp's definition of REMAP_DATA which only handles x86_64 arch: #ifdef __x86_64 #define REMAP_DATA(member) \ /* Fix data */ \ Data = Nodes[i].member;\ if(!(Data1)) \ { \ /* Compute box number */ \ uqword Nb = (Data - uqword(Nodes))/Nodes[i].GetNodeSize(); \ Data = uqword(mNodes[Nb]);\ } \ /* ...remapped */ \ mNodes[i].member = Data; #else #define REMAP_DATA(member) \ /* Fix data */ \ Data = Nodes[i].member;\ if(!(Data1)) \ { \ /* Compute box number */ \ udword Nb = (Data - udword(Nodes))/Nodes[i].GetNodeSize(); \ Data = udword(mNodes[Nb]);\ } \ /* ...remapped */ \ mNodes[i].member = Data; #endif For ppc64el, as for x86_64, uqword should be used instead of udword. In the attached patch, I've changed the #ifdef line to this: #if defined(__x86_64) || defined(__PPC64__) Thanks for considering this patch. Regards, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/patches/fix-ppc64el.patch b/debian/patches/fix-ppc64el.patch --- a/debian/patches/fix-ppc64el.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/fix-ppc64el.patch 2014-10-22 16:00:54.756073954 +0200 @@ -0,0 +1,12 @@ +diff -Naur a/src/Collision/Opcode/OPC_OptimizedTree.cpp b/src/Collision/Opcode/OPC_OptimizedTree.cpp +--- a/src/Collision/Opcode/OPC_OptimizedTree.cpp b/src/Collision/Opcode/OPC_OptimizedTree.cpp +@@ -557,7 +557,7 @@ + } \ + } + +-#ifdef __x86_64 ++#if defined(__x86_64) || defined(__PPC64__) + #define REMAP_DATA(member) \ + /* Fix data */ \ + Data = Nodes[i].member; \ diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-10-16 12:09:30.164364404 +0200 +++ b/debian/patches/series 2014-10-22 16:01:22.268072491 +0200 @@ -7,3 +7,4 @@ 0007-Fix-cast-from-pointer-to-udword-losing-precision.patch 0008-Fix-OpenSceneGraph-compilation-issues.patch 0009-Install-libraries-always.patch +fix-ppc64el.patch
Bug#765672: src:gammaray: FTBFS on ppc64el
Package: src:gammaray Version: 2.1.0-3.1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, tests are failing. The issue seems to come from a typo in the debian-archs-fix-build.patch file. This patch adds a test in cmake/GammaRayProbeABI.cmake : elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL ppc64el) To fix the issue, ppc64el should be replaced by ppc64le. FYI the same fix has been applied on Ubuntu. Thanks for considering this patch. Regards, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/patches/ppc64el.patch b/debian/patches/ppc64el.patch --- a/debian/patches/ppc64el.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/ppc64el.patch 2014-10-16 15:26:55.519734834 +0200 @@ -0,0 +1,11 @@ +--- a/cmake/GammaRayProbeABI.cmake b/cmake/GammaRayProbeABI.cmake +@@ -80,7 +80,7 @@ + set(GAMMARAY_PROBE_ABI ${GAMMARAY_PROBE_ABI}-arm) + elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL mips64) + set(GAMMARAY_PROBE_ABI ${GAMMARAY_PROBE_ABI}-mips) +- elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL ppc64el) ++ elseif(CMAKE_SYSTEM_PROCESSOR STREQUAL ppc64le) + set(GAMMARAY_PROBE_ABI ${GAMMARAY_PROBE_ABI}-ppc64) + else() + set(GAMMARAY_PROBE_ABI ${GAMMARAY_PROBE_ABI}-${CMAKE_SYSTEM_PROCESSOR}) diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-10-16 13:06:34.900182383 +0200 +++ b/debian/patches/series 2014-10-16 15:27:16.639733712 +0200 @@ -1 +1,2 @@ debian-archs-fix-build.patch +ppc64el.patch
Bug#735832: (no subject)
Hi, I've collected and tested the patch applied by Ubuntu. It could be useful in the meantime the package will be updated with the upstream version. Erwan. diff -Naur a/debian/patches/01_editor.dpatch b/debian/patches/01_editor.dpatch --- a/debian/patches/01_editor.dpatch 2014-08-21 11:18:05.109832955 +0200 +++ b/debian/patches/01_editor.dpatch 2014-08-21 11:29:41.145795962 +0200 @@ -10,7 +10,7 @@ +++ wyrd-1.4.1/wyrdrc 2006-11-27 11:42:35.0 +0100 @@ -5,11 +5,11 @@ # the default reminder file to display - set reminders_file=~/.reminders + set reminders_file=$HOME/.reminders # command for editing an old appointment, given a line number %line% and filename %file% -set edit_old_command=$EDITOR +%line% %file% +set edit_old_command=${VISUAL:-$EDITOR} +%line% %file% diff -Naur a/debian/patches/02_fix-ftbfs-ocaml-4.patch b/debian/patches/02_fix-ftbfs-ocaml-4.patch --- a/debian/patches/02_fix-ftbfs-ocaml-4.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/02_fix-ftbfs-ocaml-4.patch 2014-08-21 11:39:19.529765221 +0200 @@ -0,0 +1,36 @@ +From: Paul Pelzl +Subject: fix 'configure' test which incorrectly rejected OCaml 4 + . + Patch not needed for wyrd = 1.4.6 + . +Origin: upstream, http://bazaar.launchpad.net/~pelzlpj/wyrd/wyrd-dev/revision/304 +Bug-Ubuntu: https://launchpad.net/bugs/1281275 +Bug-Debian: http://bugs.debian.org/735832 + +--- + configure|2 +- + configure.in |2 +- + 2 files changed, 2 insertions(+), 2 deletions(-) + +--- a/configure.in b/configure.in +@@ -63,7 +63,7 @@ + OCAMLMINORVERSION=`echo $OCAMLVERSION | cut -d '.' -f 2` + if test $OCAMLMAJORVERSION -lt 3 ; then +AC_MSG_ERROR(Wyrd requires OCaml version 3.08 or greater.) +-else ++elif test $OCAMLMAJORVERSION -eq 3; then +if test $OCAMLMINORVERSION -lt 8 ; then + AC_MSG_ERROR(Wyrd requires OCaml version 3.08 or greater.) +fi +--- a/configure b/configure +@@ -1724,7 +1724,7 @@ +{ { echo $as_me:$LINENO: error: Wyrd requires OCaml version 3.08 or greater. 5 + echo $as_me: error: Wyrd requires OCaml version 3.08 or greater. 2;} +{ (exit 1); exit 1; }; } +-else ++elif test $OCAMLMAJORVERSION -eq 3; then +if test $OCAMLMINORVERSION -lt 8 ; then + { { echo $as_me:$LINENO: error: Wyrd requires OCaml version 3.08 or greater. 5 + echo $as_me: error: Wyrd requires OCaml version 3.08 or greater. 2;} diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/series 2014-08-21 11:20:54.249823966 +0200 @@ -0,0 +1,2 @@ +01_editor.dpatch +02_fix-ftbfs-ocaml-4.patch diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-08-21 11:18:05.105832956 +0200 +++ b/debian/rules 2014-08-21 11:19:09.873829513 +0200 @@ -2,7 +2,6 @@ include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk -include /usr/share/cdbs/1/rules/dpatch.mk DEB_CONFIGURE_EXTRA_FLAGS = --enable-utf8 diff -Naur a/debian/source/format b/debian/source/format --- a/debian/source/format 1970-01-01 01:00:00.0 +0100 +++ b/debian/source/format 2014-08-21 11:21:50.185820993 +0200 @@ -0,0 +1 @@ +3.0 (quilt)
Bug#758796: src:parole: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:parole Version: 0.5.4-1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, it failed, due to libtool and configuration files not being updated. Please consider this patch, which uses dh-autoreconf to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-08-21 14:13:01.465275083 +0200 +++ b/debian/control 2014-08-21 14:56:17.273137119 +0200 @@ -8,7 +8,8 @@ libgtk2.0-dev (= 2.20), libgstreamer0.10-dev, libgstreamer-plugins-base0.10-dev, libdbus-1-dev, libdbus-glib-1-dev, libxfce4ui-1-dev, libxfconf-0-dev (= 4.10), - libnotify-dev, libtagc0-dev + libnotify-dev, libtagc0-dev, + dh-autoreconf, xfce4-dev-tools, gtk-doc-tools Standards-Version: 3.9.4 Homepage: http://goodies.xfce.org/projects/applications/parole Vcs-Svn: svn://anonscm.debian.org/pkg-xfce/goodies/trunk/parole/ diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-08-21 14:13:01.565275078 +0200 +++ b/debian/rules 2014-08-21 14:16:32.993263841 +0200 @@ -5,7 +5,7 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all %: - dh $@ --parallell + dh $@ --parallell --with autoreconf override_dh_makeshlibs: dh_makeshlibs -X usr/lib/$(DEB_HOST_MULTIARCH)/parole-0 @@ -15,4 +15,5 @@ dh_install --fail-missing override_dh_auto_configure: + xdt-autogen dh_auto_configure -- --disable-silent-rules
Bug#758120: src:meanwhile: update aclocal.m4 and configure to fix FTBFS on ppc64el
Package: src:meanwhile Version: 1.0.2-4.1 Severity: normal Tags: patch Dear Maintainer, While trying to build the package on ppc64el, it failed, due to missing entry about powerpc64le in aclocal.m4 and configure files. Please consider this patch to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/aclocal.m4 b/aclocal.m4 --- a/aclocal.m4 2014-08-12 16:48:55.690106660 +0200 +++ b/aclocal.m4 2014-08-14 12:31:22.325743827 +0200 @@ -535,7 +535,10 @@ x86_64-*linux*) LD=${LD-ld} -m elf_i386 ;; -ppc64-*linux*|powerpc64-*linux*) +powerpc64le-*) + LD=${LD-ld} -m elf32lppclinux + ;; +powerpc64-*) LD=${LD-ld} -m elf32ppclinux ;; s390x-*linux*) @@ -551,7 +554,10 @@ x86_64-*linux*) LD=${LD-ld} -m elf_x86_64 ;; -ppc*-*linux*|powerpc*-*linux*) +powerpcle-*) + LD=${LD-ld} -m elf64lppc + ;; +powerpc-*) LD=${LD-ld} -m elf64ppc ;; s390*-*linux*) diff -Naur a/configure b/configure --- a/configure 2014-08-12 16:48:55.878106650 +0200 +++ b/configure 2014-08-14 12:31:22.329743827 +0200 @@ -3819,7 +3819,10 @@ x86_64-*linux*) LD=${LD-ld} -m elf_i386 ;; -ppc64-*linux*|powerpc64-*linux*) +powerpc64le-*) + LD=${LD-ld} -m elf32lppclinux + ;; +powerpc64-*) LD=${LD-ld} -m elf32ppclinux ;; s390x-*linux*) @@ -3835,7 +3838,10 @@ x86_64-*linux*) LD=${LD-ld} -m elf_x86_64 ;; -ppc*-*linux*|powerpc*-*linux*) +powerpcle-*) + LD=${LD-ld} -m elf64lppc + ;; +powerpc-*) LD=${LD-ld} -m elf64ppc ;; s390*-*linux*)
Bug#757334: Missing build-dep in previous patch
Hi, In my previous patch I forgot to add some build dependencies. Here a new patch that replace the previous one. Sorry for the inconvenience. Erwan. diff -Naur a/debian/control b/debian/control --- a/debian/control2014-08-06 13:51:51.774223809 +0200 +++ b/debian/control2014-08-06 13:52:43.894221039 +0200 @@ -5,7 +5,7 @@ Uploaders: Yves-Alexis Perez cor...@debian.org, Lionel Le Folgoc mrpo...@gmail.com Build-Depends: debhelper (= 9), intltool (= 0.31), pkg-config, - libglib2.0-dev, libgtk2.0-dev, libxfce4util-dev (= 4.10.0), dpkg-dev (= 1.16.1) + libglib2.0-dev, libgtk2.0-dev, libxfce4util-dev (= 4.10.0), dpkg-dev (= 1.16.1), dh-autoreconf, xfce4-dev-tools, gtk-doc-tools Standards-Version: 3.9.3 Homepage: http://www.xfce.org/ Vcs-Svn: svn://svn.debian.org/pkg-xfce/desktop/trunk/garcon diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-08-06 13:51:51.778223809 +0200 +++ b/debian/rules 2014-08-06 13:53:14.550219410 +0200 @@ -4,7 +4,11 @@ export DEB_BUILD_MAINT_OPTIONS=hardening=+all %: - dh $@ --parallel + dh $@ --parallel --with autoreconf + +override_dh_auto_configure: + xdt-autogen + dh_auto_configure override_dh_install: dh_install --fail-missing -X .la
Bug#757201: src:upower: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:upower Version: 0.99.0-3 Severity: normal Tags: patch Dear Maintainer, I got a failure while building the package on ppc64el architecture. Since this package uses libtool, a full autoreconf seems necessary. This is because it needs new libtool macros for ppc64el. The attached patch was applied to achieve the following: * Build using dh-autoreconf. * Patch configure.ac because side-by-side use of IT_PROG_INTLTOOL and AM_GNU_GETTEXT is not supported. Thanks for considering the patch. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-08-04 17:23:04.346734439 +0200 +++ b/debian/control 2014-08-05 10:29:32.479461085 +0200 @@ -21,6 +21,7 @@ libimobiledevice-dev (= 0.9.7) [linux-any], libgirepository1.0-dev (= 0.10.7-1~), gobject-introspection (= 0.9.12-4~), + dh-autoreconf Standards-Version: 3.9.5 Vcs-Git: git://git.debian.org/git/pkg-utopia/upower.git Vcs-Browser: http://git.debian.org/?p=pkg-utopia/upower.git;a=summary diff -Naur a/debian/patches/configure.patch b/debian/patches/configure.patch --- a/debian/patches/configure.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/configure.patch 2014-08-06 09:06:20.747134308 +0200 @@ -0,0 +1,12 @@ +--- a/configure.ac 2014-08-04 17:23:03.682734474 +0200 b/configure.ac 2014-08-05 12:32:56.283067579 +0200 +@@ -234,9 +234,6 @@ + # i18n support + IT_PROG_INTLTOOL([0.40.0]) + +-AM_GNU_GETTEXT_VERSION([0.17]) +-AM_GNU_GETTEXT([external]) +- + AC_SUBST([GETTEXT_PACKAGE],[${PACKAGE_TARNAME}]) + AC_DEFINE([GETTEXT_PACKAGE],[PACKAGE_TARNAME],[Define to the gettext package name]) + diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/series 2014-08-06 09:07:53.931129355 +0200 @@ -0,0 +1 @@ +configure.patch diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-08-04 17:23:04.358734438 +0200 +++ b/debian/rules 2014-08-05 17:27:09.714129315 +0200 @@ -1,7 +1,7 @@ #!/usr/bin/make -f %: - dh $@ --with gir + dh $@ --with gir --with autoreconf override_dh_auto_configure: dh_auto_configure -- \ @@ -29,3 +29,11 @@ override_dh_makeshlibs: dh_makeshlibs -- -c4 + +override_dh_auto_clean: + rm -f libupower-glib/up-client-glue.c \ + libupower-glib/up-client-glue.h \ + libupower-glib/up-device-glue.c \ + libupower-glib/up-device-glue.h \ + libupower-glib/up-wakeups-glue.c \ + libupower-glib/up-wakeups-glue.h
Bug#756518: src:presage: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:presage Version: 0.8.9-1 Severity: normal Tags: patch Dear Maintainer, While trying to build presage on ppc64el, it failed, due to libtool and configuration files not being updated and also because automake -Werror is enabled. Dimitri John Ledkov x...@ubuntu.com has written a patch that disables automake -Werror. Please consider the attached patch, which uses dh-autoreconf and includes the patch from Dimitri. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-30 16:47:22.833808672 +0200 +++ b/debian/control 2014-07-30 16:54:36.529785622 +0200 @@ -4,6 +4,8 @@ Maintainer: Matteo Vescovi matteo.vesc...@yahoo.co.uk Build-Depends: debhelper (= 7.0.50~), autotools-dev, + dh-autoreconf, + pkg-config, libsqlite3-dev, sqlite3, libtinyxml-dev (= 2.5.3), diff -Naur a/debian/patches/no-automake-werror.patch b/debian/patches/no-automake-werror.patch --- a/debian/patches/no-automake-werror.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/no-automake-werror.patch 2014-07-30 17:15:47.813718054 +0200 @@ -0,0 +1,14 @@ +Description: Disable automake -Werror. +Author: Dimitri John Ledkov x...@ubuntu.com + +--- presage-0.8.8.orig/configure.ac presage-0.8.8/configure.ac +@@ -23,7 +23,7 @@ dnl Process this file with autoconf to p + + + AC_INIT([presage],[0.8.9],[matteo.vesc...@yahoo.co.uk]) +-AM_INIT_AUTOMAKE([-Wall -Werror]) ++AM_INIT_AUTOMAKE([-Wall]) + + AC_CONFIG_SRCDIR([src/lib/presage.cpp]) + AC_CONFIG_HEADERS([config.h:config.hin]) diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/series 2014-07-30 17:18:52.605708233 +0200 @@ -0,0 +1 @@ +no-automake-werror.patch diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-30 16:47:22.853808671 +0200 +++ b/debian/rules 2014-07-30 16:50:49.369797695 +0200 @@ -5,7 +5,7 @@ PYVERS=$(shell pyversions -vs) %: - dh $@ --with autotools_dev --with python2 + dh $@ --with autoreconf --with python2 # Enable build hardening
Bug#704206: teem: FTBFS[any-i386]: testsuite failures
Hi, Based on the patch provided by Adam, the attached patch fixes FTBFS on ppc64el. It adds ppc64el to the arches using -ffp-contract=off. Hoping it helps, Erwan. diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-29 14:15:22.230885507 +0200 +++ b/debian/rules 2014-07-29 14:15:45.574884266 +0200 @@ -16,7 +16,7 @@ ifneq (,$(filter $(DEB_HOST_ARCH_CPU), i386)) CFLAGS += -ffloat-store endif -ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 s390 s390x)) +ifneq (,$(filter $(DEB_HOST_ARCH_CPU), powerpc ppc64 ppc64el s390 s390x)) CFLAGS += -ffp-contract=off endif
Bug#756394: src:qof: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:qof Version: 0.8.7-1 Severity: normal Tags: patch Dear Maintainer, While trying to build qof on ppc64el, it failed, due to libtool and configuration files not being updated. Please consider this patch, which uses dh-autoreconf to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-29 15:30:43.886645185 +0200 +++ b/debian/control 2014-07-29 15:31:38.038642307 +0200 @@ -4,7 +4,7 @@ Maintainer: Neil Williams codeh...@debian.org Uploaders: Goedson Teixeira Paixao goed...@debian.org Build-Depends: cdbs (= 0.4.93~), debhelper (= 9), xsltproc, - libglib2.0-dev (= 2.9.0), libxml2-dev (= 2.5.10), libsqlite0-dev + libglib2.0-dev (= 2.9.0), libxml2-dev (= 2.5.10), libsqlite0-dev, dh-autoreconf Build-Depends-Indep: doxygen Standards-Version: 3.9.4 Homepage: http://alioth.debian.org/projects/qof/ diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-29 15:30:43.898645185 +0200 +++ b/debian/rules 2014-07-29 15:31:20.846643221 +0200 @@ -19,6 +19,7 @@ include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk +include /usr/share/cdbs/1/rules/autoreconf.mk # backends do not need ldconfig (anymore) DEB_DH_MAKESHLIBS_ARGS=-Xlibqof2-backend
Bug#756014: src:exo: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:exo Version: 0.10.2-3 Severity: normal Tags: patch Dear Maintainer, While trying to build exo on ppc64el, it failed, due to libtool and configuration files not being updated. Please consider this patch, which uses dh-autoreconf to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-25 14:43:06.281165396 +0200 +++ b/debian/control 2014-07-25 14:44:22.533161343 +0200 @@ -7,7 +7,7 @@ Build-Depends: debhelper (= 9), libxfce4util-dev (= 4.10.0), dpkg-dev (= 1.16.1), libxfce4ui-1-dev (= 4.10.0), liburi-perl, chrpath, intltool, libglib2.0-dev (= 2.30), xfce4-dev-tools (= 4.10.0), libtool, - gtk-doc-tools + gtk-doc-tools, dh-autoreconf Standards-Version: 3.9.5 Homepage: http://www.xfce.org Vcs-Svn: svn://anonscm.debian.org/pkg-xfce/desktop/trunk/exo/ diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-25 14:43:06.289165395 +0200 +++ b/debian/rules 2014-07-25 14:46:52.677153363 +0200 @@ -10,7 +10,10 @@ MSGFMT = /usr/bin/msgfmt --endianness little %: - dh $@ --parallel + dh $@ --parallel --with autoreconf + +override_dh_autoreconf: + xdt-autogen override_dh_auto_configure: MSGFMT=$(MSGFMT) dh_auto_configure -- --disable-gtk-doc --disable-silent-rules
Bug#756031: src:aiksaurus: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:aiksaurus Version: 1.2.1+dev-0.12-6.1 Severity: normal Tags: patch Dear Maintainer, While trying to build exo on ppc64el, it failed, due to libtool and configuration files not being updated. Please consider this patch, which uses dh-autoreconf to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/configure.ac b/configure.ac --- a/configure.ac 2014-07-25 15:43:54.488971497 +0200 +++ b/configure.ac 2014-07-25 16:13:50.396876046 +0200 @@ -50,6 +50,9 @@ LT_CURRENT=`expr $AIK_MICRO_VERSION - $AIK_INTERFACE_AGE` LT_REVISION=$AIK_INTERFACE_AGE LT_AGE=`expr $AIK_BINARY_AGE - $AIK_INTERFACE_AGE` +m4_pattern_allow([LT_CURRENT]) +m4_pattern_allow([LT_REVISION]) +m4_pattern_allow([LT_AGE]) LT_AIK_VERSION_INFO=$LT_CURRENT:$LT_REVISION:$LT_AGE diff -Naur a/debian/compat b/debian/compat --- a/debian/compat 2014-07-25 15:43:54.756971483 +0200 +++ b/debian/compat 2014-07-25 16:19:26.368858189 +0200 @@ -1 +1 @@ -4 +9 diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-25 15:43:54.740971483 +0200 +++ b/debian/control 2014-07-25 15:44:22.064970031 +0200 @@ -2,7 +2,7 @@ Section: devel Priority: optional Maintainer: Masayuki Hatta (mhatta) mha...@debian.org -Build-Depends: debhelper ( 4.2.21), libgtk2.0-dev +Build-Depends: debhelper ( 4.2.21), libgtk2.0-dev, dh-autoreconf Standards-Version: 3.8.0 Package: libaiksaurus-1.2-dev diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-25 15:43:54.752971483 +0200 +++ b/debian/rules 2014-07-25 16:14:55.152872604 +0200 @@ -31,8 +31,9 @@ #major=`ls src/.libs/lib*.so.* | \ # awk '{if (match($$0,/\.so\.[0-9]+$$/)) print substr($$0,RSTART+4)}'` -config.status: configure +config.status: dh_testdir + AUTOMAKE=automake --foreign dh_autoreconf # Add here commands to configure the package. ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info \ --enable-static @@ -54,12 +55,7 @@ # Add here commands to clean up after the build process. [ ! -f Makefile ] || $(MAKE) distclean -ifneq $(wildcard /usr/share/misc/config.sub) - cp -f /usr/share/misc/config.sub config.sub -endif -ifneq $(wildcard /usr/share/misc/config.guess) - cp -f /usr/share/misc/config.guess config.guess -endif + dh_autoreconf_clean dh_clean diff -Naur a/gtk/src/Makefile.am b/gtk/src/Makefile.am --- a/gtk/src/Makefile.am 2014-07-25 15:43:54.668971487 +0200 +++ b/gtk/src/Makefile.am 2014-07-25 16:13:50.400876046 +0200 @@ -44,6 +44,6 @@ bin_PROGRAMS = gaiksaurus gaiksaurus_SOURCES = gtkAiksaur.t.cpp -gaiksaurus_LDADD = libAiksaurusGTK.la +gaiksaurus_LDADD = libAiksaurusGTK.la $(GTK_LIBS) EXTRA_DIST = $(OTHERHEADERS)
Bug#755899: src:pth: update libtool.m4 and configure to fix FTBFS on ppc64el
Package: src:pth Version: 2.0.7-19 Severity: normal Tags: patch Dear Maintainer, While trying to build pth on ppc64el, it failed, due to missing entry about powerpc64le in libtool.m4 and configure files. Please consider this patch to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/patches/powerpc64le.diff 1970-01-01 00:00:00.0 + +++ b/debian/patches/powerpc64le.diff 2013-12-21 18:07:29.0 + @@ -0,0 +1,56 @@ +Index: b/configure +=== +--- a/configure b/configure +@@ -4383,7 +4383,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_i386 + ;; +-ppc64-*linux*|powerpc64-*linux*) ++ powerpc64le-*) ++ LD=${LD-ld} -m elf32lppclinux ++ ;; ++ powerpc64-*) + LD=${LD-ld} -m elf32ppclinux + ;; + s390x-*linux*) +@@ -4399,7 +4402,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_x86_64 + ;; +-ppc*-*linux*|powerpc*-*linux*) ++ powerpcle-*) ++ LD=${LD-ld} -m elf64lppc ++ ;; ++ powerpc-*) + LD=${LD-ld} -m elf64ppc + ;; + s390*-*linux*) +Index: b/libtool.m4 +=== +--- a/libtool.m4 b/libtool.m4 +@@ -533,7 +533,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_i386 + ;; +-ppc64-*linux*|powerpc64-*linux*) ++ powerpc64le-*) ++ LD=${LD-ld} -m elf32lppclinux ++ ;; ++ powerpc64-*) + LD=${LD-ld} -m elf32ppclinux + ;; + s390x-*linux*) +@@ -549,7 +552,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_x86_64 + ;; +-ppc*-*linux*|powerpc*-*linux*) ++ powerpcle-*) ++ LD=${LD-ld} -m elf64lppc ++ ;; ++ powerpc-*) + LD=${LD-ld} -m elf64ppc + ;; + s390*-*linux*) --- 2.0.7-19/debian/patches/series 2013-07-08 12:35:38.0 + +++ 2.0.7-19ubuntu1/debian/patches/series 2013-12-21 18:04:39.0 + @@ -5,3 +5,4 @@ 05-linux_3.patch 06-ldflags.patch 07-test_uctx_fix.patch +powerpc64le.diff
Bug#755915: src:malaga: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:malaga Version: 7.12-5 Severity: normal Tags: patch Dear Maintainer, While trying to build malaga on ppc64el, it failed, due to libtool and configuration files not being updated. Please consider this patch, which uses dh-autoreconf to fulfill that need. Thanks in advance, Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-24 14:52:44.421726751 +0200 +++ b/debian/control 2014-07-24 15:41:31.865571160 +0200 @@ -2,7 +2,7 @@ Maintainer: Timo Jyrinki t...@debian.org Section: misc Priority: optional -Build-Depends: libgtk2.0-dev, libglib2.0-dev, texinfo, texlive, libreadline-dev, debhelper ( = 7.0.8 ), autotools-dev, libcairo-dev, quilt (= 0.46-7~), dpkg (= 1.15.4) | install-info +Build-Depends: libgtk2.0-dev, libglib2.0-dev, texinfo, texlive, libreadline-dev, debhelper ( = 7.0.8 ), autotools-dev, libcairo-dev, quilt (= 0.46-7~), dpkg (= 1.15.4) | install-info, dh-autoreconf Standards-Version: 3.9.2 Package: malaga-bin diff -Naur a/debian/patches/no-ncurses.diff b/debian/patches/no-ncurses.diff --- a/debian/patches/no-ncurses.diff 2014-07-24 14:52:44.437726750 +0200 +++ b/debian/patches/no-ncurses.diff 2014-07-24 15:38:00.309582404 +0200 @@ -25,23 +25,3 @@ READLINE_CFLAGS=-DREADLINE else READLINE_LIBS= a/configure -+++ b/configure -@@ -18462,7 +18462,7 @@ - echo $ECHO_N (cached) $ECHO_C 6 - else - ac_check_lib_save_LIBS=$LIBS --LIBS=-lreadline -lcurses $LIBS -+LIBS=-lreadline $LIBS - cat conftest.$ac_ext _ACEOF - /* confdefs.h. */ - _ACEOF -@@ -18663,7 +18663,7 @@ - fi - if test $use_readline = yes - then -- READLINE_LIBS=-lreadline -lcurses -+ READLINE_LIBS=-lreadline - READLINE_CFLAGS=-DREADLINE - else - READLINE_LIBS= diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-24 14:52:44.437726750 +0200 +++ b/debian/rules 2014-07-24 15:42:54.713566757 +0200 @@ -21,7 +21,7 @@ major=`ls src/.libs/lib*.so.* | \ awk '{if (match($$0,/\.so\.[0-9]+$$/)) print substr($$0,RSTART+4)}'` -config.status: configure +configure-stamp: dh_testdir dh_quilt_patch ifneq $(wildcard /usr/share/misc/config.sub) @@ -30,13 +30,14 @@ ifneq $(wildcard /usr/share/misc/config.guess) cp -f /usr/share/misc/config.guess config.guess endif + -dh_autoreconf # Add here commands to configure the package. ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp build-doc -build-stamp: config.status +build-stamp: configure-stamp dh_testdir # Add here commands to compile the package. @@ -65,6 +66,7 @@ rm -rf build-doc rm -f debian/substvars + dh_autoreconf_clean dh_clean install: build
Bug#755790: lft: use autotools-dev to update config.{sub,guess} for new arches
Package: lft Version: 2.2-4 Severity: normal Tags: patch Dear Maintainer, While trying to build lft on ppc64el, it failed, due to config.{sub,guess} files not being updated. Please consider this patch, which uses autotools-dev to fulfill that need. Thanks! Erwan. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -6,6 +6,7 @@ build: build-stamp build-stamp: dh_testdir + dh_autotools-dev_updateconfig ./configure $(MAKE) touch $@ @@ -18,6 +19,7 @@ rm -f config.status rm -f lft rm -f *.o + dh_autotools-dev_restoreconfig dh_clean install: build --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: optional Homepage: http://www.mainnerve.com/lft/index.html Maintainer: Vince Mulhollon v...@debian.org -Build-Depends: debhelper (= 8), libpcap-dev +Build-Depends: debhelper (= 8), libpcap-dev, autotools-dev Standards-Version: 3.9.1.0 Package: lft
Bug#754097: src:uclmmbase: use autotools-dev to fix FTBFS on ppc64el
Package: src:uclmmbase Version: 1.2.16.0-1 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to update config.{sub,guess} for new arches. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-07 16:09:24.631547662 +0200 +++ b/debian/control 2014-07-07 16:23:56.067501346 +0200 @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: David MartÃnez Moreno en...@debian.org -Build-Depends: debhelper (= 4.0.16), gtk-doc-tools +Build-Depends: debhelper (= 4.0.16), gtk-doc-tools, autotools-dev Standards-Version: 3.6.2.2 Package: libuclmmbase1 diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-07 16:09:24.639547662 +0200 +++ b/debian/rules 2014-07-07 16:23:30.395502711 +0200 @@ -13,6 +13,7 @@ build: build-stamp build-stamp: dh_testdir + dh_autotools-dev_updateconfig ./configure --enable-ipv6 --prefix=/usr $(MAKE) touch build-stamp @@ -23,6 +24,7 @@ rm -f build-stamp install-stamp # Add here commands to clean up after the build process. -$(MAKE) distclean + dh_autotools-dev_restoreconfig dh_clean install: install-stamp
Bug#754092: libapache2-mod-defensible: use dh-autoreconf to fix FTBFS on ppc64el
Package: libapache2-mod-defensible Version: 1.4-3.1 Severity: normal Tags: patch Dear Maintainer, In Ubuntu, the attached patch was applied to achieve the following: * Use dh-autoreconf to fix FTBFS on ppc64el by getting new libtool macros. * Use automake's foreign option to fix FTBFS while autoreconfing. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-07-07 15:24:59.727689299 +0200 +++ b/debian/control 2014-07-07 15:25:46.255686827 +0200 @@ -3,7 +3,7 @@ Section: web Priority: extra Standards-Version: 3.8.0 -Build-Depends: debhelper (= 5.0.0), dh-apache2, apache2-dev (= 2.2.3-2) +Build-Depends: debhelper (= 5.0.0), dh-apache2, apache2-dev (= 2.2.3-2), dh-autoreconf Package: libapache2-mod-defensible Architecture: any diff -Naur a/debian/patches/automake-foreign.patch b/debian/patches/automake-foreign.patch --- a/debian/patches/automake-foreign.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/automake-foreign.patch 2014-07-07 15:39:50.515641955 +0200 @@ -0,0 +1,13 @@ +--- a/configure.in b/configure.in +@@ -1,8 +1,8 @@ + # configure.in for mod_defensible + # © 2007 Julien Danjou jul...@danjou.info + +-AC_INIT(mod_defensible) +-AM_INIT_AUTOMAKE(mod_defensible, 1.2) ++AC_INIT([mod_defensible], [1.2]) ++AM_INIT_AUTOMAKE([foreign]) + + AC_CONFIG_SRCDIR(mod_defensible.c) + diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-07-07 15:24:59.739689299 +0200 +++ b/debian/patches/series 2014-07-07 15:39:50.515641955 +0200 @@ -2,3 +2,4 @@ aplog-use-module.patch server-banner.patch conn-rec-remote-ip.patch +automake-foreign.patch diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-07-07 15:24:59.735689299 +0200 +++ b/debian/rules 2014-07-07 15:26:34.291684273 +0200 @@ -5,6 +5,7 @@ config.status: dh_testdir + dh_autoreconf ./configure build: build-stamp @@ -20,6 +21,7 @@ dh_testroot rm -f build-stamp config.log [ ! -f Makefile ] || $(MAKE) distclean + dh_autoreconf_clean dh_clean install: build
Bug#752769: src:libxfce4util: FTBFS on ppc64el
Package: src:libxfce4util Version: 4.10.1-1 Severity: normal Tags: patch Dear Maintainer, On Ubuntu the attached patch was applied to achieve the following: * Patch aclocal.m4 and configure to build on ppc64el. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash diff -Naur a/debian/patches/ppc64el.patch b/debian/patches/ppc64el.patch --- a/debian/patches/ppc64el.patch 1970-01-01 01:00:00.0 +0100 +++ b/debian/patches/ppc64el.patch 2014-06-26 14:30:45.354375178 +0200 @@ -0,0 +1,54 @@ +diff -Naur a/aclocal.m4 b/aclocal.m4 +--- a/aclocal.m4 2014-06-26 14:08:28.606446225 +0200 b/aclocal.m4 2014-06-26 14:12:48.802432396 +0200 +@@ -2060,7 +2060,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_i386 + ;; +- ppc64-*linux*|powerpc64-*linux*) ++ powerpc64le-*) ++ LD=${LD-ld} -m elf32lppclinux ++ ;; ++ powerpc64-*) + LD=${LD-ld} -m elf32ppclinux + ;; + s390x-*linux*) +@@ -2079,7 +2082,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_x86_64 + ;; +- ppc*-*linux*|powerpc*-*linux*) ++ powerpcle-*) ++ LD=${LD-ld} -m elf64lppc ++ ;; ++ powerpc-*) + LD=${LD-ld} -m elf64ppc + ;; + s390*-*linux*|s390*-*tpf*) +diff -Naur a/configure b/configure +--- a/configure 2014-06-26 14:08:28.638446223 +0200 b/configure 2014-06-26 14:16:51.938419473 +0200 +@@ -8281,7 +8281,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_i386 + ;; +- ppc64-*linux*|powerpc64-*linux*) ++ powerpc64le-*) ++ LD=${LD-ld} -m elf32lppclinux ++ ;; ++ powerpc64-*) + LD=${LD-ld} -m elf32ppclinux + ;; + s390x-*linux*) +@@ -8300,7 +8303,10 @@ + x86_64-*linux*) + LD=${LD-ld} -m elf_x86_64 + ;; +- ppc*-*linux*|powerpc*-*linux*) ++ powerpcle-*) ++ LD=${LD-ld} -m elf64lppc ++ ;; ++ powerpc-*) + LD=${LD-ld} -m elf64ppc + ;; + s390*-*linux*|s390*-*tpf*) diff -Naur a/debian/patches/series b/debian/patches/series --- a/debian/patches/series 2014-06-26 14:32:43.130368918 +0200 +++ b/debian/patches/series 2014-06-26 14:36:43.094356164 +0200 @@ -1,2 +1,3 @@ 01_add-desktop-base-in-config-dirs.patch 02_fix-abicheck.sh +ppc64el.patch
Bug#752769: [Pkg-xfce-devel] Bug#752769: src:libxfce4util: FTBFS on ppc64el
On 06/26/2014 03:07 PM, Yves-Alexis Perez wrote: On jeu., 2014-06-26 at 14:56 +0200, Erwan Prioul wrote: Dear Maintainer, On Ubuntu the attached patch was applied to achieve the following: * Patch aclocal.m4 and configure to build on ppc64el. Thanks for considering the patch. Is it not easier to run dh_autoreconf before the build? I've tried a bunch of times to use dh_autoreconf. It needed to tweak a bit configure.ac and Makefile.am, not a big deal. But it always ended with this kind of error: ./configure: line 13374: syntax error near unexpected token `am' ./configure: line 13374: `XDT_I18N(am ar ast bn ca cs cy da de dz el en_GB es et eu fi fr gl he hu id is it ja ka kk ko lt lv mk nb nl nn pa pl pt pt_BR ro ru si sk sl sq sv tl_PH tr ug uk ur ur_PK zh_CN zh_TW )' It's related to the XDT macros from the configure.ac. I couldn't figure out how to get rid of this. So that's why I've finally decided to patch aclocal.m4 and configure, even if I know it's not the best way to fix this issue. Erwan. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752769: [Pkg-xfce-devel] Bug#752769: src:libxfce4util: FTBFS on ppc64el
On 06/26/2014 03:42 PM, Yves-Alexis Perez wrote: On jeu., 2014-06-26 at 15:21 +0200, Erwan Prioul wrote: I've tried a bunch of times to use dh_autoreconf. It needed to tweak a bit configure.ac and Makefile.am, not a big deal. But it always ended with this kind of error: ./configure: line 13374: syntax error near unexpected token `am' ./configure: line 13374: `XDT_I18N(am ar ast bn ca cs cy da de dz el en_GB es et eu fi fr gl he hu id is it ja ka kk ko lt lv mk nb nl nn pa pl pt pt_BR ro ru si sk sl sq sv tl_PH tr ug uk ur ur_PK zh_CN zh_TW )' It's related to the XDT macros from the configure.ac. I couldn't figure out how to get rid of this. So that's why I've finally decided to patch aclocal.m4 and configure, even if I know it's not the best way to fix this issue. I think it needs a call do xdt-autogen before configure (and a build-dep on xfce4-dev-tools). Thanks for the help. I've reworked my patch (it replaces the previous one). This time it only patches debian/control and debian/rules. In debian/control the build-dep list has been extended. debian/rules runs dh_autoreconf and xdt-autogen is called before configure. Regards, Erwan. diff -Naur a/debian/control b/debian/control --- a/debian/control 2014-06-25 11:58:00.495454365 +0200 +++ b/debian/control 2014-06-26 16:45:34.801945231 +0200 @@ -5,7 +5,7 @@ Uploaders: Yves-Alexis Perez cor...@debian.org, Lionel Le Folgoc mrpo...@gmail.com Build-Depends: debhelper (= 9), libglib2.0-dev, intltool, - dpkg-dev (= 1.16.1) + dpkg-dev (= 1.16.1), dh-autoreconf, gtk-doc-tools, xfce4-dev-tools Standards-Version: 3.9.3 Homepage: http://www.xfce.org/ Vcs-Svn: svn://svn.debian.org/pkg-xfce/desktop/trunk/libxfce4util/ diff -Naur a/debian/rules b/debian/rules --- a/debian/rules 2014-06-25 11:58:00.495454365 +0200 +++ b/debian/rules 2014-06-26 16:37:20.845971484 +0200 @@ -9,5 +9,9 @@ override_dh_strip: dh_strip --dbg-package=libxfce4util6-dbg +override_dh_auto_configure: + xdt-autogen + dh_auto_configure $@ + %: - dh $@ --parallel + dh $@ --parallel --with autoreconf
Bug#752526: src:liblouis: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:liblouis Version: 2.5.3-2 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -23,17 +23,17 @@ PYVERS := $(shell pyversions -r) PY3VERS := $(shell py3versions -r) -config.status: configure +configure-stamp: dh_testdir - cp -f /usr/share/misc/config.sub build-aux/config.sub - cp -f /usr/share/misc/config.guess build-aux/config.guess + dh_autoreconf ./configure $(CROSS) --prefix=/usr --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info CFLAGS=$(CFLAGS) LDFLAGS=-Wl,-z,defs --enable-ucs4 + touch $@ build: build-indep build-arch build-indep: build-stamp build-arch: build-stamp -build-stamp: config.status +build-stamp: configure-stamp dh_testdir $(MAKE) cd python; \ @@ -45,7 +45,7 @@ clean: dh_testdir dh_testroot - rm -f build-stamp check-stamp + rm -f build-stamp check-stamp configure-stamp [ ! -f Makefile ] || $(MAKE) distclean -cd python; \ for py in $(PYVERS) $(PY3VERS); do \ @@ -53,9 +53,8 @@ done; \ rm -f louis/__init__.pyc rm -f doc/liblouis.info doc/stamp-vti doc/version.texi - rm -f build-aux/config.sub - rm -f build-aux/config.guess rm -fr python/build + dh_autoreconf_clean dh_clean install: build
Bug#752447: src:libapreq2: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:libapreq2 Version: 2.13-3 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -1,7 +1,7 @@ Source: libapreq2 Section: perl Priority: optional -Build-Depends: debhelper (= 7), apache2-dev (= 2.0.50-10), dh-apache2, libapr1-dev, libextutils-xsbuilder-perl, perl (= 5.8.0-7), libapache2-mod-perl2 (= 2.0.2-2.1), libapache2-mod-perl2-dev, dpkg-dev (= 1.16.1~), autotools-dev +Build-Depends: debhelper (= 7), apache2-dev (= 2.0.50-10), dh-apache2, libapr1-dev, libextutils-xsbuilder-perl, perl (= 5.8.0-7), libapache2-mod-perl2 (= 2.0.2-2.1), libapache2-mod-perl2-dev, dpkg-dev (= 1.16.1~), dh-autoreconf Maintainer: Steinar H. Gunderson se...@debian.org Standards-Version: 3.9.4 --- a/debian/rules +++ b/debian/rules @@ -32,7 +32,7 @@ build-arch: dh_testdir - dh_autotools-dev_updateconfig + -dh_autoreconf $(PERL) Makefile.PL --with-apache2-apxs=/usr/bin/apxs2 --prefix=/usr --libdir=/usr/lib/$(DEB_HOST_MULTIARCH) sed -i -r 's/(hardcode_into_libs)=.*$$/\1=no/' $(CURDIR)/libtool # See http://wiki.debian.org/RpathIssue. $(MAKE) OPTIMIZE=$(CFLAGS) LDDLFLAGS=-shared $(LDFLAGS) LD_RUN_PATH= @@ -43,7 +43,7 @@ [ ! -f Makefile ] || $(MAKE) distclean $(RM) -r $(TMP) $(RM) config.nice glue/perl/Makefile.old glue/perl/t/REPORT glue/perl/t/SMOKE - dh_autotools-dev_restoreconfig + dh_autoreconf_clean dh_clean binary: binary-arch binary-indep
Bug#751390: src:pcre3: use dh-autoreconf to fix FTBFS on ppc64el
On 06/18/2014 08:24 PM, Mark Baker wrote: On 18 Jun 2014, at 18:44, Helmut Grohne hel...@subdivi.de wrote: Control: tags -1 - patch On Mon, Jun 16, 2014 at 06:28:40PM +0200, Helmut Grohne wrote: On Thu, Jun 12, 2014 at 02:00:26PM +0200, Erwan Prioul wrote: * Build using dh-autoreconf for new port support. The original pcre3 package patches configure to fix the soname. Yes. It is unfortunate that this is necessary, but debian had PCRE building a shared library before this was supported upstream, and when upstream added shared library support I felt that compatibility with existing debian packages was more important than compatibility with other linux distributions so kept the soname I had previously used. Since then there has never been a need for a change to the soname, or I would have taken the opportunity to change it to be the same as upstream. By applying dh-autoreconf this fix is ignored and the resulting binary packages become broken. Presumably what I need to do is to patch configure.ac instead of configure. The version numbers appear to be conveniently at the top of there, so this should be straightforward. Hi, I've reworked the initial patch according to the previous comments: - Nothing about parallel building. - No more changes about the dh_makeshlibs invocations. - A new entry into debian/patches to patch files outside the debian directory (no_jit_ppc64el.patch to disable JIT on ppc64el). I've added a change into soname.patch to apply changes into configure.ac instead of configure. Erwan. --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Mark Baker m...@mnb.org.uk Standards-Version: 3.9.3 -Build-Depends: debhelper (= 5.0.22), dpkg-dev (= 1.16.0) +Build-Depends: debhelper (= 5.0.22), dpkg-dev (= 1.16.0), dh-autoreconf Package: libpcre3 Section: libs --- a/debian/patches/no_jit_ppc64el.patch +++ b/debian/patches/no_jit_ppc64el.patch @@ -0,0 +1,18 @@ +Description: Disable JIT on ppc64el, needs explicit porting to ELFv2. +Author: Adam Conrad adcon...@ubuntu.com + +--- pcre3-8.31.orig/sljit/sljitConfigInternal.h pcre3-8.31/sljit/sljitConfigInternal.h +@@ -94,7 +94,11 @@ + #define SLJIT_CONFIG_ARM_V5 1 + #endif + #elif defined(__ppc64__) || defined(__powerpc64__) +-#define SLJIT_CONFIG_PPC_64 1 ++# if _CALL_ELF != 2 ++# define SLJIT_CONFIG_PPC_64 1 ++# else ++# define SLJIT_CONFIG_UNSUPPORTED 1 ++# endif + #elif defined(__ppc__) || defined(__powerpc__) + #define SLJIT_CONFIG_PPC_32 1 + #elif defined(__mips__) --- a/debian/patches/series +++ b/debian/patches/series @@ -4,3 +4,4 @@ pcregrep.1-patch soname.patch bug1287 +no_jit_ppc64el.patch --- a/debian/patches/soname.patch +++ b/debian/patches/soname.patch @@ -1,23 +1,20 @@ From: Mark Baker m...@mnb.org.uk Description: Change soname to what debian use -Index: pcre3-8.31/configure + +Index: b/configure.ac === pcre3-8.31.orig/configure 2012-07-06 10:02:02.0 +0100 -+++ pcre3-8.31/configure 2012-09-13 19:47:13.0 +0100 -@@ -17190,13 +17190,13 @@ - # (Note: The libpcre*_version bits are m4 variables, assigned above) +--- a/configure.ac b/configure.ac +@@ -17,9 +17,9 @@ + # 50 lines of this file. Please update that if the variables above are moved. - EXTRA_LIBPCRE_LDFLAGS=$EXTRA_LIBPCRE_LDFLAGS \ -- $NO_UNDEFINED -version-info 1:1:0 -+ $NO_UNDEFINED -version-info 16:1:13 + # Libtool shared library interface versions (current:revision:age) +-m4_define(libpcre_version, [1:1:0]) +-m4_define(libpcre16_version, [0:1:0]) +-m4_define(libpcreposix_version, [0:1:0]) ++m4_define(libpcre_version, [16:1:13]) ++m4_define(libpcre16_version, [16:1:13]) ++m4_define(libpcreposix_version, [16:1:13]) + m4_define(libpcrecpp_version, [0:0:0]) - EXTRA_LIBPCRE16_LDFLAGS=$EXTRA_LIBPCRE16_LDFLAGS \ -- $NO_UNDEFINED -version-info 0:1:0 -+ $NO_UNDEFINED -version-info 16:1:13 - - EXTRA_LIBPCREPOSIX_LDFLAGS=$EXTRA_LIBPCREPOSIX_LDFLAGS \ --$NO_UNDEFINED -version-info 0:1:0 -+$NO_UNDEFINED -version-info 16:1:13 - - EXTRA_LIBPCRECPP_LDFLAGS=$EXTRA_LIBPCRECPP_LDFLAGS \ - $NO_UNDEFINED -version-info 0:0:0 \ + AC_PREREQ(2.57) --- a/debian/rules +++ b/debian/rules @@ -27,9 +27,10 @@ INSTALL_PROGRAM += -s endif -config.status: configure +configure-stamp: dh_testdir # Add here commands to configure the package. + dh_autoreconf CC_FOR_BUILD=cc CFLAGS=$(CFLAGS) ./configure \ --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr --mandir=\$${prefix}/share/man \ @@ -38,11 +39,12 @@ --enable-utf8 --enable-unicode-properties \ --disable-silent-rules \ $(shell . debian/jit-test) + touch configure-stamp build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp -build
Bug#751390: src:pcre3: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:pcre3 Version: 8.31-5 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf for new port support. * Enable parallel builds. * Disable JIT on ppc64el, needs explicit porting to ELFv2. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -12,6 +12,9 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) CFLAGS = -Wall -g +ifneq (,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) + NJOBS = -j$(patsubst parallel=%,%,$(filter parallel=%,$(DEB_BUILD_OPTIONS))) +endif INSTALL = install INSTALL_FILE= $(INSTALL) -p-o root -g root -m 644 INSTALL_PROGRAM = $(INSTALL) -p-o root -g root -m 755 @@ -27,9 +30,10 @@ INSTALL_PROGRAM += -s endif -config.status: configure +configure-stamp: dh_testdir # Add here commands to configure the package. + dh_autoreconf CC_FOR_BUILD=cc CFLAGS=$(CFLAGS) ./configure \ --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr --mandir=\$${prefix}/share/man \ @@ -38,25 +42,26 @@ --enable-utf8 --enable-unicode-properties \ --disable-silent-rules \ $(shell . debian/jit-test) + touch configure-stamp build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp -build-stamp: config.status +build-stamp: configure-stamp dh_testdir # Add here commands to compile the package. - $(MAKE) + $(MAKE) $(NJOBS) ifeq ($(DEB_BUILD_GNU_TYPE),$(DEB_HOST_GNU_TYPE)) $(MAKE) check endif touch build-stamp -clean: config.status +clean: dh_testdir dh_testroot - rm -f build-stamp + rm -f configure-stamp build-stamp # Add here commands to clean up after the build process. [ ! -f Makefile ] || $(MAKE) distclean ### -test -r /usr/share/misc/config.sub \ @@ -64,6 +69,7 @@ ### -test -r /usr/share/misc/config.guess \ ### cp -f /usr/share/misc/config.guess config.guess rm -f dftables testsavedregex + dh_autoreconf_clean dh_clean install: build @@ -112,8 +118,8 @@ rm debian/libpcre3-dbg/usr/lib/debug/usr/lib/libpcre* dh_compress -a dh_fixperms -a - dh_makeshlibs -plibpcre3 --add-udeb=libpcre3-udeb -V 'libpcre3 (= 8.10)' - dh_makeshlibs -plibpcrecpp0 -V 'libpcrecpp0 (= 7.7)' + dh_makeshlibs -plibpcre3 --add-udeb=libpcre3-udeb + dh_makeshlibs -plibpcrecpp0 dh_installdeb -a # dh_perl -a dh_shlibdeps -a -ldebian/libpcre3/usr/lib/$(DEB_HOST_MULTIARCH) --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Mark Baker m...@mnb.org.uk Standards-Version: 3.9.3 -Build-Depends: debhelper (= 5.0.22), dpkg-dev (= 1.16.0) +Build-Depends: debhelper (= 5.0.22), dpkg-dev (= 1.16.0), dh-autoreconf Package: libpcre3 Section: libs --- a/sljit/sljitConfigInternal.h +++ b/sljit/sljitConfigInternal.h @@ -94,7 +94,11 @@ #define SLJIT_CONFIG_ARM_V5 1 #endif #elif defined(__ppc64__) || defined(__powerpc64__) -#define SLJIT_CONFIG_PPC_64 1 +# if _CALL_ELF != 2 +# define SLJIT_CONFIG_PPC_64 1 +# else +# define SLJIT_CONFIG_UNSUPPORTED 1 +# endif #elif defined(__ppc__) || defined(__powerpc__) #define SLJIT_CONFIG_PPC_32 1 #elif defined(__mips__)
Bug#750652: proftpd-mod-dnsbl: use autotools-dev to update config.{sub, guess} for new arches
Package: proftpd-mod-dnsbl Version: 0.1.5-3 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to update config.{sub,guess} for new arches. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -7,7 +7,7 @@ DEBNAME=proftpd-mod-dnsbl %: - dh $@ + dh $@ --with autotools_dev override_dh_auto_configure: debian/control ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
Bug#750663: src:pygtk: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:pygtk Version: 2.24.0-3 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build with dh-autoreconf for new libtool. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -44,7 +44,12 @@ unpatch: cp config.guess.orig config.guess rm -rf .pc -build-%/configure-stamp: patch-stamp +autoreconf-stamp: patch-stamp + dh_testdir + dh_autoreconf autoreconf -- -f -i -I m4 + touch $@ + +build-%/configure-stamp: autoreconf-stamp dh_testdir mkdir -p build-$* cd build-$* \ @@ -57,7 +62,7 @@ build-%/build-stamp: build-%/configure-s PYTHON=/usr/bin/python$* $(MAKE) -C build-$* pyexecdir=$(call py_libdir_sh, $*) touch $@ -dbg-build-%/configure-stamp: patch-stamp +dbg-build-%/configure-stamp: autoreconf-stamp dh_testdir mkdir -p dbg-build-$* cd dbg-build-$* \ @@ -152,6 +157,8 @@ clean:: rm -rf debian/tmp-* rm -rf build-* dbg-build-* rm -f tests/*.pyc + rm -f autoreconf-stamp + dh_autoreconf_clean $(MAKE) -f debian/rules unpatch dh_clean --- a/debian/control.in +++ b/debian/control.in @@ -7,7 +7,7 @@ Build-Depends: debhelper (= 8), gnome-pkg-tools (= 0.10), cdbs, - autotools-dev, + dh-autoreconf, xvfb (= 2:1.6.0), xauth, xfonts-base, python-all-dev (= 2.6.6-3~), python-all-dbg,
Bug#750664: src:xcb-util-renderutil: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:xcb-util-renderutil Version: 0.3.8-1 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -6,6 +6,7 @@ Uploaders: Julien Danjou a...@debian.or Arnaud Fontaine ar...@debian.org Build-Depends: cdbs (= 0.4.93~), debhelper (= 9), + dh-autoreconf, libxcb1-dev (= 1.6), libxcb-render0-dev, pkg-config, --- a/debian/rules +++ b/debian/rules @@ -2,6 +2,7 @@ DEB_DH_INSTALL_SOURCEDIR=debian/tmp +include /usr/share/cdbs/1/rules/autoreconf.mk include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk
Bug#750672: src:m17n-lib: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:m17n-lib Version: 1.6.4-2 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Source: m17n-lib Section: utils Priority: optional Maintainer: Harshula Jayasuriya harsh...@debian.org -Build-Depends: debhelper (= 9), autotools-dev, libtool (= 2.2.4), automake (= 1.9.6), autoconf (= 2.61), pkg-config (= 0.22), libxt-dev, libx11-dev, libxaw7-dev, libxmu-dev, libfribidi-dev, libotf-dev (= 0.9.11), libfreetype6-dev, libxft-dev, libxrender-dev, libfontconfig1-dev, libgd2-noxpm-dev, libxml2-dev, libanthy-dev, ispell, libthai-dev, m17n-db +Build-Depends: debhelper (= 9), autotools-dev, libtool (= 2.2.4), automake (= 1.9.6), autoconf (= 2.61), pkg-config (= 0.22), libxt-dev, libx11-dev, libxaw7-dev, libxmu-dev, libfribidi-dev, libotf-dev (= 0.9.11), libfreetype6-dev, libxft-dev, libxrender-dev, libfontconfig1-dev, libgd2-noxpm-dev, libxml2-dev, libanthy-dev, ispell, libthai-dev, m17n-db, dh-autoreconf Standards-Version: 3.9.3 Homepage: http://www.nongnu.org/m17n/ --- a/debian/rules +++ b/debian/rules @@ -37,26 +37,22 @@ version=`ls src/.libs/lib*.so.* | \ major=`ls src/.libs/lib*.so.* | \ awk '{if (match($$0,/\.so\.[0-9]+$$/)) print substr($$0,RSTART+4)}'` -config.status: configure +configure-stamp: dh_testdir -ifneq $(wildcard /usr/share/misc/config.sub) - cp -f /usr/share/misc/config.sub config.sub -endif -ifneq $(wildcard /usr/share/misc/config.guess) - cp -f /usr/share/misc/config.guess config.guess -endif + dh_autoreconf ./configure $(CROSS) \ --prefix=/usr \ --mandir=\$${prefix}/share/man \ --infodir=\$${prefix}/share/info \ $(shell $(dpkg_buildflags) --export=configure) + touch $@ build-arch: build build-indep: build build: build-stamp -build-stamp: config.status +build-stamp: configure-stamp dh_testdir $(MAKE) touch $@ @@ -66,12 +62,7 @@ clean: dh_testroot rm -f build-stamp [ ! -f Makefile ] || $(MAKE) distclean -ifneq $(wildcard /usr/share/misc/config.sub) - rm -f config.sub -endif -ifneq $(wildcard /usr/share/misc/config.guess) - rm -f config.guess -endif + dh_autoreconf_clean dh_clean install: build
Bug#749051: src:confuse: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:confuse Version: 2.7-4 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build with dh-autoreconf instead of autotools-dev for new libtool. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -22,12 +22,7 @@ endif config.status: configure dh_testdir - - -test -r /usr/share/misc/config.sub \ - cp -f /usr/share/misc/config.sub support/config.sub - -test -r /usr/share/misc/config.guess \ - cp -f /usr/share/misc/config.guess support/config.guess - + dh_autoreconf CFLAGS=$(CFLAGS) ./configure \ --enable-shared \ --host=$(DEB_HOST_GNU_TYPE) \ @@ -61,7 +56,7 @@ clean: dh_testroot rm -f build-stamp [ ! -f Makefile ] || $(MAKE) distclean - rm -f support/config.sub support/config.guess + dh_autoreconf_clean dh_clean install: build --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Section: libs Priority: optional Maintainer: Aurelien Jarno aure...@debian.org -Build-Depends: debhelper (= 8.1.3), autotools-dev, pkg-config +Build-Depends: debhelper (= 8.1.3), dh-autoreconf, pkg-config Standards-Version: 3.9.2 Homepage: http://www.nongnu.org/confuse/
Bug#749053: src:libvoikko: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:libvoikko Version: 3.7-2 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build-depend on pkg-config. * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -1,7 +1,7 @@ Source: libvoikko Priority: optional Maintainer: Timo Jyrinki t...@debian.org -Build-Depends: debhelper (= 9.0.0), dpkg-dev (= 1.13.19), autotools-dev, python (= 2.6.6-3~), hardening-wrapper +Build-Depends: debhelper (= 9.0.0), dpkg-dev (= 1.13.19), autotools-dev, python (= 2.6.6-3~), hardening-wrapper, dh-autoreconf, pkg-config Standards-Version: 3.9.4 Section: libs Homepage: http://voikko.puimula.org/ --- a/debian/rules +++ b/debian/rules @@ -11,7 +11,7 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-archi export DEB_BUILD_HARDENING=1 %: - dh $@ --fail-missing --with python2 + dh $@ --fail-missing --with python2,autoreconf override_dh_auto_configure: dh_auto_configure -- --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info --with-dictionary-path=/usr/lib/voikko --libdir=/usr/lib/$(DEB_HOST_MULTIARCH)
Bug#749054: src:libhx: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:libhx Version: 3.19-1 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -1,7 +1,7 @@ Source: libhx Priority: extra Maintainer: Bastian Kleineidam cal...@debian.org -Build-Depends: debhelper (= 9), hardening-wrapper +Build-Depends: debhelper (= 9), hardening-wrapper, dh-autoreconf Standards-Version: 3.9.5 XS-Testsuite: autopkgtest Section: libs --- a/debian/rules +++ b/debian/rules @@ -3,7 +3,7 @@ export DEB_BUILD_HARDENING=1 DEB_HOST_MULTIARCH ?= $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) %: - dh $@ + dh $@ --with autoreconf override_dh_auto_configure: dh_auto_configure -- --enable-static
Bug#749064: src:libcdr: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:libcdr Version: 0.0.15-1 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Build using dh-autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules +++ b/debian/rules @@ -4,7 +4,7 @@ #export DH_VERBOSE=1 %: - dh $@ + dh $@ --with autoreconf override_dh_auto_configure: dh_auto_configure -- --docdir=/usr/share/doc/libcdr-doc --libdir=/usr/lib \ --- a/debian/control +++ b/debian/control @@ -2,6 +2,7 @@ Priority: optional Maintainer: Rene Engelhard r...@debian.org Build-Depends: autotools-dev, + dh-autoreconf, debhelper (= 9), doxygen, libboost-dev,
Bug#748911: src:opal: FTBFS on 64 bits arch
Package: src:opal Version: 3.10.10~dfsg-2.2 Severity: normal Tags: patch Dear Maintainer, The attached patch has been applied on Ubuntu to fix a FTBFS on 64 bits arch. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/rules 2013-02-17 14:36:10.0 + +++ b/debian/rules 2014-01-22 18:18:13.0 + @@ -1,6 +1,9 @@ #!/usr/bin/make -f #export DH_VERBOSE:=1 +ifeq (64,$(strip $(shell dpkg-architecture -qDEB_HOST_ARCH_BITS))) + export EXTRA_EXTRA_CPPFLAGS:=-DP_64BIT=1 +endif DEBVERSION := $(shell head -n 1 debian/changelog \ | sed -e 's/^[^(]*(\([^)]*\)).*/\1/') --- a/Makefile.in 2014-03-24 15:58:00.0 + +++ b/Makefile.in 2014-03-24 15:58:01.0 + @@ -530,11 +530,11 @@ DEPS := $(patsubst %.dep, $(OPAL_DEPDIR $(OPAL_OBJDIR)/%.o : %.cxx @if [ ! -d $(OPAL_OBJDIR) ] ; then mkdir -p $(OPAL_OBJDIR) ; fi - $(Q_CC)$(CXX) $(CXXFLAGS) -c $ -o $@ + $(Q_CC)$(CXX) $(CXXFLAGS) $(EXTRA_EXTRA_CPPFLAGS) -c $ -o $@ $(OPAL_OBJDIR)/%.o : %.c @if [ ! -d $(OPAL_OBJDIR) ] ; then mkdir -p $(OPAL_OBJDIR) ; fi - $(Q_CC)$(CC) $(CFLAGS) -c $ -o $@ + $(Q_CC)$(CC) $(CFLAGS) $(EXTRA_EXTRA_CPPFLAGS) -c $ -o $@ # # define rule for .dep files
Bug#748947: src:cmor: FTBFS on ppc64el
Package: src:cmor Version: 2.8.0-4 Severity: normal Tags: patch Dear Maintainer, On Ubuntu the attached patch was applied to achieve the following: * d/rules: Fix misspelling. * d/control: Add missing build-dependencies for ppc64el. * Explicitly link missing netcdf lib dependencies for ppc64el. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/configure.ac +++ b/configure.ac @@ -211,28 +211,28 @@ if [ test ${with_netcdfb} != -yes ]; t AC_CHECK_FILE([${with_netcdf}/bin/nc-config],[HAS_NCCONFIG=yes],[HAS_NCCONFIG=no]) if [ test ${HAS_NCCONFIG} == yes ] ; then NCCFLAGS=`${with_netcdf}/bin/nc-config --cflags` - NCLDFLAGS=`${with_netcdf}/bin/nc-config --libs` + NCLDFLAGS=`${with_netcdf}/bin/nc-config --libs` ${EXTRA_NCLDFLAGS} else #echo CRAP! NCCFLAGS= -I${with_netcdf}/include if [ test ${RTAG} != none ] ; then - NCLDFLAGS= -L${with_netcdf}/lib ${RTAG}${with_netcdf}/lib -lnetcdf + NCLDFLAGS= -L${with_netcdf}/lib ${RTAG}${with_netcdf}/lib -lnetcdf ${EXTRA_NCLDFLAGS} else - NCLDFLAGS= -L${with_netcdf}/lib -lnetcdf + NCLDFLAGS= -L${with_netcdf}/lib -lnetcdf ${EXTRA_NCLDFLAGS} fi fi else NCCFLAGS=-lnetcdf -NCLDFLAGS= +NCLDFLAGS= ${EXTRA_NCLDFLAGS} fi else AC_PATH_PROG(NCCONFIG,nc-config,no) if [ test NCCONFIG != no ] ; then NCCFLAGS=`${NCCONFIG} --cflags` - NCLDFLAGS=`${NCCONFIG} --libs` + NCLDFLAGS=`${NCCONFIG} --libs` ${EXTRA_NCLDFLAGS} else NCCFLAGS=-lnetcdf - NCLDFLAGS= + NCLDFLAGS= ${EXTRA_NCLDFLAGS} fi fi --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: extra Maintainer: Alastair McKinstry mckins...@debian.org -Build-Depends: debhelper (= 8.1.3~), dh-buildinfo, libossp-uuid-dev, libudunits2-dev, libnetcdf-dev, uuid-dev, python-all-dev (= 2.6.6-3~), python-setuptools (= 0.6b3), libgfortran3, automake, python-numpy, gfortran +Build-Depends: debhelper (= 8.1.3~), dh-buildinfo, libossp-uuid-dev, libudunits2-dev, libnetcdf-dev, uuid-dev, python-all-dev (= 2.6.6-3~), python-setuptools (= 0.6b3), libgfortran3, automake, python-numpy, gfortran, pkg-config, libcurl4-gnutls-dev, libldap2-dev, heimdal-multidev, libsqlite3-dev, libsasl2-dev, libkeyutils-dev, libffi-dev, libhdf5-mpi-dev | libhdf5-dev Build-Conflicts: libcmor2 Standards-Version: 3.9.3 Homepage: http://www2-pcmdi.llnl.gov/cmor --- a/debian/rules +++ b/debian/rules @@ -7,7 +7,9 @@ DEB_HOST_MULTIARCH ?= $(shell dpkg-archi LIBDIR=/usr/lib/$(DEB_HOST_MULTIARCH) BUILD_ARCH_OS :-= $(shell dpkg-architecture -qDEB_BUILD_ARCH_OS) -BUILD_ARCH_CPU := $(shell dpkg-archtiecture -qDEB_BUILD_ARCH_CPU) +BUILD_ARCH_CPU := $(shell dpkg-architecture -qDEB_BUILD_ARCH_CPU) + +NETCDF_LIBS ?= $(shell pkg-config --libs heimdal-gssapi netcdf libffi) %: dh $@ --with python2 @@ -16,7 +18,10 @@ override_dh_auto_configure: autoreconf -fiv ln -sf /usr/share/misc/config.sub dh_auto_configure -- --disable-color --enable-verbose-test \ - UUIDLDFLAGS=-lossp-uuid UUIDFLAGS=-I/usr/include/ossp SZLIBFLAGS=nosz + UUIDLDFLAGS=-lossp-uuid UUIDFLAGS=-I/usr/include/ossp SZLIBFLAGS=nosz \ + EXTRA_NCLDFLAGS=-lhdf5 -lm -lcurl $(NETCDF_LIBS) -lz -lidn -lrtmp -lgcrypt \ + -lgnutls -lgssapi_krb5 -llber -lldap_r -lgpg-error -ltasn1 -lp11-kit\ + -lk5crypto -lkrb5support -lsasl2 -lkeyutils -lsqlite3 override_dh_auto_clean: rm -rf config.sub config.log config.status libcmor.a libcmor.so.2 build test_grid
Bug#748851: rlog: use dh-autoreconf to fix FTBFS on ppc64el
Package: rlog Version: 1.4-2 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Use dh-autoreconf to fix FTBFS on ppc64el as well by getting new libtool macros (still updates config.{sub,guess}). * Add fix_autoreconf_FTBFS to fix FTBFS with autoreconf due to commented-out rules. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- 1.4-2/debian/control +++ 1.4-2ubuntu2/debian/control @@ -1,7 +1,7 @@ Source: rlog Priority: optional Maintainer: Eduard Bloch bl...@debian.org -Build-Depends: debhelper (= 5.0.0), doxygen-latex, gcc (=4:4.3.4) +Build-Depends: debhelper (= 5.0.0), doxygen-latex, gcc (=4:4.3.4), dh-autoreconf Standards-Version: 3.9.2 Section: libs --- 1.4-2/debian/rules +++ 1.4-2ubuntu2/debian/rules @@ -46,6 +46,7 @@ export CXXFLAGS config.status: configure dh_testdir + dh_autoreconf # Add here commands to configure the package. ./configure --host=$(DEB_HOST_GNU_TYPE) --build=$(DEB_BUILD_GNU_TYPE) --prefix=/usr --mandir=\$${prefix}/share/man --infodir=\$${prefix}/share/info @@ -74,6 +75,7 @@ clean: # cp -f /usr/share/misc/config.guess config/config.guess #endif + dh_autoreconf_clean dh_clean install: build --- 1.4-2/docs/Makefile.am +++ 1.4-2ubuntu2/docs/Makefile.am @@ -24,8 +24,6 @@ html/index.html: ../Doxyfile $(SOURCES) -cd .. @DOXYGEN@ Doxyfile clean-local: - #-rm -rf html - #-rm -rf latex endif all-local: html/index.html
Bug#748855: src:libusb: use dh-autoreconf to fix FTBFS on ppc64el
Package: src:libusb Version: 0.1.12-23.3 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Use dh_autoreconf. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control 2012-04-03 21:13:30.0 + +++ b/debian/control 2013-12-03 13:53:27.0 + @@ -2,7 +2,7 @@ Source: libusb Section: libs Priority: optional Maintainer: Aurelien Jarno aure...@debian.org -Build-Depends: debhelper (= 8.1.3), autotools-dev, pkg-config, docbook, docbook-dsssl +Build-Depends: debhelper (= 8.1.3), dh-autoreconf, autotools-dev, pkg-config, docbook, docbook-dsssl Standards-Version: 3.9.3 Package: libusb-0.1-4 --- a/debian/rules 2013-11-14 11:57:49.0 + +++ b/debian/rules 2013-12-03 13:54:15.0 + @@ -55,6 +55,8 @@ configure-common-stamp: cp -f /usr/share/misc/config.sub config.sub cp -f /usr/share/misc/config.guess config.guess + dh_autoreconf + touch $@ configure-deb: configure-deb-stamp @@ -134,6 +136,7 @@ clean: # Remove install dirs rm -rf $(CURDIR)/debian/tmp $(CURDIR)/debian/tmp-udeb + dh_autoreconf_clean dh_clean install: build
Bug#748851: (no subject)
Hello, As said Breno, this bug is a dup of #747877. I've missed it when checking for dup. Sorry. This bug, #748851, can be cancelled. Erwan Prioul. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748747: fileschanged: use autotools-dev to update config.{sub,guess} for new arches
Package: fileschanged Version: 0.6.5-1.2 Severity: normal Tags: patch Dear Maintainer, Please use autotools-dev to update config.{sub,guess} for new architectures. In Ubuntu, a similiar patch was applied to achieve the following: * Use autotools-dev to update config.{sub,guess} for new arches. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Juan A. Diaz j...@linux.org.ar -Build-Depends: debhelper (= 5.0.0), dpatch, help2man, texinfo, libfam-dev (= 2.7.0-10) | libgamin-dev (= 0.1.7-4) +Build-Depends: debhelper (= 5.0.0), dpatch, help2man, texinfo, libfam-dev (= 2.7.0-10) | libgamin-dev (= 0.1.7-4), autotools-dev Standards-Version: 3.7.3 Homepage: http://fileschanged.sourceforge.net/ --- a/debian/rules +++ b/debian/rules @@ -23,13 +23,7 @@ configure-stamp: patch dh_testdir -ifneq $(wildcard /usr/share/misc/config.sub) - cp -f /usr/share/misc/config.sub config.sub -endif -ifneq $(wildcard /usr/share/misc/config.guess) - cp -f /usr/share/misc/config.guess config.guess -endif - + dh_autotools-dev_updateconfig ./configure --host=$(DEB_HOST_GNU_TYPE) \ --build=$(DEB_BUILD_GNU_TYPE) \ --prefix=/usr \ @@ -51,6 +45,7 @@ [ ! -f Makefile ] || $(MAKE) clean clean: up_clean unpatch + dh_autotools-dev_restoreconfig dh_clean install: build
Bug#748760: libmnl: update libtool.m4 for ppc64el
Package: libmnl Version: 1.0.3-3 Severity: normal Tags: patch Dear Maintainer, The attached patch has been applied on Ubuntu to fix a FTBFS on ppc64el. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Description: update-libtool.patch: Update libtool.m4 for powerpc64le. Author: Adam Conrad adcon...@ubuntu.com --- libmnl-1.0.3.orig/m4/libtool.m4 +++ libmnl-1.0.3/m4/libtool.m4 @@ -1312,7 +1312,7 @@ ia64-*-hpux*) rm -rf conftest* ;; -x86_64-*kfreebsd*-gnu|x86_64-*linux*|ppc*-*linux*|powerpc*-*linux*| \ +x86_64-*kfreebsd*-gnu|x86_64-*linux*|powerpc*-*linux*| \ s390*-*linux*|s390*-*tpf*|sparc*-*linux*) # Find out which ABI we are using. echo 'int i;' conftest.$ac_ext @@ -1324,9 +1324,19 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux* LD=${LD-ld} -m elf_i386_fbsd ;; x86_64-*linux*) - LD=${LD-ld} -m elf_i386 + case `/usr/bin/file conftest.o` in + *x86-64*) + LD=${LD-ld} -m elf32_x86_64 + ;; + *) + LD=${LD-ld} -m elf_i386 + ;; + esac + ;; + powerpc64le-*) + LD=${LD-ld} -m elf32lppclinux ;; - ppc64-*linux*|powerpc64-*linux*) + powerpc64-*) LD=${LD-ld} -m elf32ppclinux ;; s390x-*linux*) @@ -1345,7 +1355,10 @@ s390*-*linux*|s390*-*tpf*|sparc*-*linux* x86_64-*linux*) LD=${LD-ld} -m elf_x86_64 ;; - ppc*-*linux*|powerpc*-*linux*) + powerpcle-*) + LD=${LD-ld} -m elf64lppc + ;; + powerpc-*) LD=${LD-ld} -m elf64ppc ;; s390*-*linux*|s390*-*tpf*) @@ -1688,7 +1701,8 @@ AC_CACHE_VAL([lt_cv_sys_max_cmd_len], [d ;; *) lt_cv_sys_max_cmd_len=`(getconf ARG_MAX) 2 /dev/null` -if test -n $lt_cv_sys_max_cmd_len; then +if test -n $lt_cv_sys_max_cmd_len \ + test undefined != $lt_cv_sys_max_cmd_len; then lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \/ 4` lt_cv_sys_max_cmd_len=`expr $lt_cv_sys_max_cmd_len \* 3` else @@ -2512,17 +2526,6 @@ freebsd* | dragonfly*) esac ;; -gnu*) - version_type=linux # correct to gnu/linux during the next big refactor - need_lib_prefix=no - need_version=no - library_names_spec='${libname}${release}${shared_ext}$versuffix ${libname}${release}${shared_ext}${major} ${libname}${shared_ext}' - soname_spec='${libname}${release}${shared_ext}$major' - shlibpath_var=LD_LIBRARY_PATH - shlibpath_overrides_runpath=no - hardcode_into_libs=yes - ;; - haiku*) version_type=linux # correct to gnu/linux during the next big refactor need_lib_prefix=no @@ -2639,7 +2642,7 @@ linux*oldld* | linux*aout* | linux*coff* ;; # This must be glibc/ELF. -linux* | k*bsd*-gnu | kopensolaris*-gnu) +linux* | k*bsd*-gnu | kopensolaris*-gnu | gnu*) version_type=linux # correct to gnu/linux during the next big refactor need_lib_prefix=no need_version=no @@ -3255,10 +3258,6 @@ freebsd* | dragonfly*) fi ;; -gnu*) - lt_cv_deplibs_check_method=pass_all - ;; - haiku*) lt_cv_deplibs_check_method=pass_all ;; @@ -3297,7 +3296,7 @@ irix5* | irix6* | nonstopux*) ;; # This must be glibc/ELF. -linux* | k*bsd*-gnu | kopensolaris*-gnu) +linux* | k*bsd*-gnu | kopensolaris*-gnu | gnu*) lt_cv_deplibs_check_method=pass_all ;; @@ -4049,7 +4048,7 @@ m4_if([$1], [CXX], [ ;; esac ;; - linux* | k*bsd*-gnu | kopensolaris*-gnu) + linux* | k*bsd*-gnu | kopensolaris*-gnu | gnu*) case $cc_basename in KCC*) # KAI C++ Compiler @@ -4348,7 +4347,7 @@ m4_if([$1], [CXX], [ _LT_TAGVAR(lt_prog_compiler_static, $1)='-non_shared' ;; -linux* | k*bsd*-gnu | kopensolaris*-gnu) +linux* | k*bsd*-gnu | kopensolaris*-gnu | gnu*) case $cc_basename in # old Intel for x86_64 which still supported -KPIC. ecc*) @@ -6241,9 +6240,6 @@ if test $_lt_caught_CXX_error != yes; _LT_TAGVAR(ld_shlibs, $1)=yes ;; - gnu*) -;; - haiku*) _LT_TAGVAR(archive_cmds, $1)='$CC -shared $libobjs $deplibs $compiler_flags ${wl}-soname $wl$soname -o $lib' _LT_TAGVAR(link_all_deplibs, $1)=yes @@ -6405,7 +6401,7 @@ if test $_lt_caught_CXX_error != yes; _LT_TAGVAR(inherit_rpath, $1)=yes ;; - linux* | k*bsd*-gnu | kopensolaris*-gnu) + linux* | k*bsd*-gnu | kopensolaris*-gnu | gnu*) case $cc_basename in KCC*) # Kuck and Associates, Inc. (KAI) C++ Compiler
Bug#748361: m4: build tests are failing on ppc64el
Package: m4 Version: 1.4.17-2 Severity: normal Tags: upstream patch Dear Maintainer, I've noticed build tests are failing on ppc64el. In Ubuntu, the attached patch was applied to fix the issue (Fix detection of floating point endianness). Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash -- no debconf information Description: Fix detection of floating point endianness See https://lists.gnu.org/archive/html/bug-gnulib/2013-12/msg00104.html Author: Alan Modra amo...@gmail.com Author: Colin Watson cjwat...@ubuntu.com Forwarded: no Last-Update: 2013-12-18 Index: b/tests/test-isnanl.h === --- a/tests/test-isnanl.h +++ b/tests/test-isnanl.h @@ -24,6 +24,12 @@ #include nan.h #include macros.h +#ifdef __FLOAT_WORD_ORDER__ +# define FLOAT_BIG_ENDIAN (__FLOAT_WORD_ORDER__ != __ORDER_LITTLE_ENDIAN__) +#else +# define FLOAT_BIG_ENDIAN (LDBL_EXPBIT0_WORD NWORDS / 2) +#endif + int main () { @@ -56,10 +62,10 @@ # if LDBL_EXPBIT0_BIT 0 m.word[LDBL_EXPBIT0_WORD] ^= (unsigned int) 1 (LDBL_EXPBIT0_BIT - 1); # else -m.word[LDBL_EXPBIT0_WORD + (LDBL_EXPBIT0_WORD NWORDS / 2 ? 1 : - 1)] +m.word[LDBL_EXPBIT0_WORD + (FLOAT_BIG_ENDIAN ? 1 : - 1)] ^= (unsigned int) 1 (sizeof (unsigned int) * CHAR_BIT - 1); # endif -m.word[LDBL_EXPBIT0_WORD + (LDBL_EXPBIT0_WORD NWORDS / 2 ? 1 : - 1)] +m.word[LDBL_EXPBIT0_WORD + (FLOAT_BIG_ENDIAN ? 1 : - 1)] |= (unsigned int) 1 LDBL_EXPBIT0_BIT; ASSERT (isnanl (m.value)); } Index: b/tests/test-signbit.c === --- a/tests/test-signbit.c +++ b/tests/test-signbit.c @@ -36,6 +36,12 @@ double zerod = 0.0; long double zerol = 0.0L; +#ifdef __FLOAT_WORD_ORDER__ +# define FLOAT_BIG_ENDIAN (__FLOAT_WORD_ORDER__ != __ORDER_LITTLE_ENDIAN__) +#else +# define FLOAT_BIG_ENDIAN (LDBL_EXPBIT0_WORD NWORDS / 2) +#endif + static void test_signbitf () { @@ -156,10 +162,10 @@ # if LDBL_EXPBIT0_BIT 0 m.word[LDBL_EXPBIT0_WORD] ^= (unsigned int) 1 (LDBL_EXPBIT0_BIT - 1); # else -m.word[LDBL_EXPBIT0_WORD + (LDBL_EXPBIT0_WORD NWORDS / 2 ? 1 : - 1)] +m.word[LDBL_EXPBIT0_WORD + (FLOAT_BIG_ENDIAN ? 1 : - 1)] ^= (unsigned int) 1 (sizeof (unsigned int) * CHAR_BIT - 1); # endif -m.word[LDBL_EXPBIT0_WORD + (LDBL_EXPBIT0_WORD NWORDS / 2 ? 1 : - 1)] +m.word[LDBL_EXPBIT0_WORD + (FLOAT_BIG_ENDIAN ? 1 : - 1)] |= (unsigned int) 1 LDBL_EXPBIT0_BIT; (void) signbit (m.value); #undef NWORDS
Bug#748250: expat: use dh-autoreconf to fix FTBFS on ppc64el
Package: expat Version: 2.1.0-4 Severity: normal Tags: patch Dear Maintainer, For the ppc64el architecture in Ubuntu, since this package uses libtool, a full autoreconf is necessary. This is because we need new libtool macros for ppc64el. In Ubuntu, the attached patch was applied to achieve the following: * Use dh-autoreconf to fix FTBFS on ppc64el. * Enable parallel builds. Thanks for considering the patch. Erwan Prioul. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash --- a/debian/control +++ b/debian/control @@ -3,7 +3,7 @@ Priority: optional Maintainer: Laszlo Boszormenyi (GCS) g...@debian.org Standards-Version: 3.9.4 -Build-Depends: debhelper (= 8.1.3), docbook-to-man, +Build-Depends: debhelper (= 8.1.3), docbook-to-man, dh-autoreconf, dpkg-dev (= 1.16.0), gcc-multilib [i386 powerpc sparc s390] Homepage: http://expat.sourceforge.net --- a/debian/rules +++ b/debian/rules @@ -43,23 +43,33 @@ UPACKAGE = $(shell dh_listpackages | grep -- -udeb$$) -build/config.status: configure +COMMA = , +ifneq (,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS + NJOBS := -j $(subst parallel=,,$(filter parallel=%,$(subst $(COMMA), ,$(DEB_BUILD_OPTIONS +endif + +config-common-stamp: + dh_testdir + dh_autoreconf + touch $@ + +build/config.status: config-common-stamp dh_testdir (mkdir -p $(@D); cd $(@D); CFLAGS=$(CFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) \ ../configure $(CONFFLAGS) --prefix=/usr --mandir=\$${prefix}/share/man --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)) -buildw/config.status: configure +buildw/config.status: config-common-stamp dh_testdir (mkdir -p $(@D); cd $(@D); CFLAGS=$(CFLAGS) -DXML_UNICODE CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) \ ../configure $(CONFFLAGS) --prefix=/usr --mandir=\$${prefix}/share/man --libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH)) -build64/config.status: configure +build64/config.status: config-common-stamp dh_testdir (mkdir -p $(@D); cd $(@D); CFLAGS=-m64 $(CFLAGS) CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) \ ../configure $(CONFFLAGS) $(HOST64FLAG) --prefix=/usr --mandir=\$${prefix}/share/man \ --libdir=\$${prefix}/lib64) -buildw64/config.status: configure +buildw64/config.status: config-common-stamp dh_testdir (mkdir -p $(@D); cd $(@D); CFLAGS=-m64 $(CFLAGS) -DXML_UNICODE CPPFLAGS=$(CPPFLAGS) LDFLAGS=$(LDFLAGS) \ ../configure $(CONFFLAGS) $(HOST64FLAG) --prefix=/usr --mandir=\$${prefix}/share/man \ @@ -70,18 +80,19 @@ dh_testroot rm -rf build/ build64/ buildw/ buildw64/ rm -rf debian/tmp/ - dh_clean build-stamp debian/xmlwf.1 + dh_autoreconf_clean + dh_clean config-common-stamp build-stamp debian/xmlwf.1 build: build-stamp build-arch: build-stamp build-indep: build-stamp build-stamp: build/config.status buildw/config.status $(if $(BUILD64), build64/config.status buildw64/config.status) dh_testdir - $(MAKE) -C build/ - $(MAKE) -C buildw/ buildlib LIBRARY=libexpatw.la + $(MAKE) $(NJOBS) -C build/ + $(MAKE) $(NJOBS) -C buildw/ buildlib LIBRARY=libexpatw.la ifneq ($(BUILD64),) - $(MAKE) -C build64/ buildlib - $(MAKE) -C buildw64/ buildlib LIBRARY=libexpatw.la + $(MAKE) $(NJOBS) -C build64/ buildlib + $(MAKE) $(NJOBS) -C buildw64/ buildlib LIBRARY=libexpatw.la endif docbook-to-man doc/xmlwf.sgml debian/xmlwf.1 touch $@
Bug#743622: libnspr4-dev: support for ppc64el
Package: libnspr4-dev Version: 2:4.10.4-1 Severity: normal Tags: patch Dear Maintainer, I've noticed some defines aren't well set for powerpc64le (aka ppc64el) in linux config file (include/md/_linux.cfg). There is an assumption that powerpc64 is big endian, so defines are set in this way (for example IS_BIG_ENDIAN is defined). This assumption could lead to compiling error on ppc64el arch which is powperpc64 and little endian. To prevent errors, I've added a test to check for powerpc64 to verify the endianness (little or big). Hope it helps. -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages libnspr4-dev depends on: ii libnspr4 2:4.10.4-1 libnspr4-dev recommends no packages. libnspr4-dev suggests no packages. -- no debconf information --- a/nspr/pr/include/md/_linux.cfg +++ b/nspr/pr/include/md/_linux.cfg @@ -28,10 +28,56 @@ #endif #ifdef __powerpc64__ +#define IS_64 +#ifdef _LITTLE_ENDIAN + +#define IS_LITTLE_ENDIAN 1 +#undef IS_BIG_ENDIAN + +#define PR_BYTES_PER_BYTE 1 +#define PR_BYTES_PER_SHORT 2 +#define PR_BYTES_PER_INT4 +#define PR_BYTES_PER_INT64 8 +#define PR_BYTES_PER_LONG 8 +#define PR_BYTES_PER_FLOAT 4 +#define PR_BYTES_PER_DOUBLE 8 +#define PR_BYTES_PER_WORD 8 +#define PR_BYTES_PER_DWORD 8 + +#define PR_BITS_PER_BYTE8 +#define PR_BITS_PER_SHORT 16 +#define PR_BITS_PER_INT 32 +#define PR_BITS_PER_INT64 64 +#define PR_BITS_PER_LONG64 +#define PR_BITS_PER_FLOAT 32 +#define PR_BITS_PER_DOUBLE 64 +#define PR_BITS_PER_WORD64 + +#define PR_BITS_PER_BYTE_LOG2 3 +#define PR_BITS_PER_SHORT_LOG2 4 +#define PR_BITS_PER_INT_LOG25 +#define PR_BITS_PER_INT64_LOG2 6 +#define PR_BITS_PER_LONG_LOG2 6 +#define PR_BITS_PER_FLOAT_LOG2 5 +#define PR_BITS_PER_DOUBLE_LOG2 6 +#define PR_BITS_PER_WORD_LOG2 6 + +#define PR_ALIGN_OF_SHORT 2 +#define PR_ALIGN_OF_INT 4 +#define PR_ALIGN_OF_LONG8 +#define PR_ALIGN_OF_INT64 8 +#define PR_ALIGN_OF_FLOAT 4 +#define PR_ALIGN_OF_DOUBLE 8 +#define PR_ALIGN_OF_POINTER 8 +#define PR_ALIGN_OF_WORD8 + +#define PR_BYTES_PER_WORD_LOG2 3 +#define PR_BYTES_PER_DWORD_LOG2 3 + +#else /* assuming this is BIG ENDIAN */ #undef IS_LITTLE_ENDIAN #define IS_BIG_ENDIAN1 -#define IS_64 #define PR_BYTES_PER_BYTE 1 #define PR_BYTES_PER_SHORT 2 @@ -72,6 +118,7 @@ #define PR_BYTES_PER_WORD_LOG2 3 #define PR_BYTES_PER_DWORD_LOG2 3 +#endif #elif defined(__powerpc__)
Bug#742785: usbutils: lsusb -t exits with segmentation fault
Package: usbutils Version: 1:007-2 Severity: normal Tags: patch Hi, I got the following error running 'lsusb -t': # lsusb -t Segmentation fault It seems to happen because my directory /sys/bus/usb/devices/ is empty. I've checked the code and found that as the directory is empty, usbbuslist isn't populated (still NULL). In the function sort_busses, usbbuslist is used as it isn't NULL, but it's the case here, so it ends with a segmentation fault. To prevent this error I've added a quick check in the code about usbbuslist at the beginning of the function sort_busses. Patch in attachment. Hope it helps. --- a/lsusb-t.c 2013-06-06 19:13:12.0 -0400 +++ b/lsusb-t.c 2014-03-27 07:39:56.075336155 -0400 @@ -605,6 +605,7 @@ /* need to reverse sort bus numbers */ struct usbbusnode *t, *p, **pp; int swapped; + if (!usbbuslist) return; do { p = usbbuslist; pp = usbbuslist;