Bug#744884: add ppc64el support
Source: klibc Version: 2.0.2-1 Severity: important Tags: patch Maintainer, May you please include these 2 patches from klibc, in order to support the ppc64el architecture? [klibc] ppc64: Add ppc64le support [klibc] ppc64: build with -mcmodel=small A new upstream release with klibc 2.0.3 would resolve this as well. thank you -- Mauricio Faria de Oliveira IBM Linux Technology Center From: Anton Blanchard an...@samba.org Date: Tue, 3 Dec 2013 18:18:03 +1100 Subject: [klibc] ppc64: Add ppc64le support Add PowerPC 64bit little endian support. Signed-off-by: Anton Blanchard an...@samba.org Signed-off-by: H. Peter Anvin h...@zytor.com Trivial backport to 2.0.2 (Makefile conflict, no arm64 in source package): Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com --- Makefile| 6 +- usr/klibc/arch/ppc64/MCONFIG| 4 ++-- usr/klibc/arch/ppc64/crt0.S | 34 --- usr/klibc/arch/ppc64/setjmp.S | 40 ++-- usr/klibc/arch/ppc64/sysstub.ph | 45 ++--- 5 files changed, 87 insertions(+), 42 deletions(-) diff --git a/Makefile b/Makefile index 0a3ee69..0d06774 100644 --- a/Makefile +++ b/Makefile @@ -30,7 +30,11 @@ export OBJDUMP := $(KLIBCROSS)objdump NOSTDINC_FLAGS := -nostdlib -nostdinc -isystem $(shell $(CC) -print-file-name=include) -ARCH := $(shell uname -m | sed -e s/i.86/i386/ -e s/parisc64/parisc/ -e s/sun4u/sparc64/ -e s/arm.*/arm/ -e s/sa110/arm/ -e s/sh.*/sh/) +ARCH := $(shell uname -m | sed -e s/i.86/i386/ \ + -e s/parisc64/parisc/ -e s/sun4u/sparc64/ \ + -e s/arm.*/arm/ -e s/sa110/arm/ \ + -e s/sh.*/sh/ \ + -e s/ppc64le/ppc64/) export KLIBCARCH ?= $(ARCH) export KLIBCARCHDIR := $(shell echo $(KLIBCARCH) | sed -e s/s390x/s390/) diff --git a/usr/klibc/arch/ppc64/MCONFIG b/usr/klibc/arch/ppc64/MCONFIG index cb66614..0294c44 100644 --- a/usr/klibc/arch/ppc64/MCONFIG +++ b/usr/klibc/arch/ppc64/MCONFIG @@ -7,10 +7,10 @@ # accordingly. # -KLIBCARCHREQFLAGS = -m64 -mcall-aixdesc +KLIBCARCHREQFLAGS = -m64 +KLIBCARCHREQFLAGS += $(call cc-option, -mcall-aixdesc, ) KLIBCOPTFLAGS += -Os KLIBCBITSIZE = 64 -KLIBCLDFLAGS = -m elf64ppc # Extra linkflags when building the shared version of the library # This address needs to be reachable using normal inter-module diff --git a/usr/klibc/arch/ppc64/crt0.S b/usr/klibc/arch/ppc64/crt0.S index c976d5c..ed14534 100644 --- a/usr/klibc/arch/ppc64/crt0.S +++ b/usr/klibc/arch/ppc64/crt0.S @@ -9,25 +9,35 @@ # } # - .section .toc,aw -.LC0: .tc environ[TC],environ - .text - .align 4 - + .balign 4 + .globl _start +#if _CALL_ELF == 2 + .type _start,@function +_start: +#else .section .opd,aw + .balign 8 _start: .quad ._start, .TOC.@tocbase, 0 .previous - .size _start, 24 .type ._start,@function - .globl _start - .globl ._start ._start: - stdu%r1,-32(%r1) - addi%r3,%r1,32 +#endif + +#if _CALL_ELF == 2 +0: addis 2,12,.TOC.-0b@ha + addi 2,2,.TOC.-0b@l +#endif + + stdu %r1,-32(%r1) + addi %r3,%r1,32 li %r4,0 /* fini (unused) */ - b .__libc_init + b __libc_init nop - .size ._start,.-._start +#if _CALL_ELF == 2 + .size _start,.-_start +#else + .size _start,.-._start +#endif diff --git a/usr/klibc/arch/ppc64/setjmp.S b/usr/klibc/arch/ppc64/setjmp.S index 30db419..ecf9717 100644 --- a/usr/klibc/arch/ppc64/setjmp.S +++ b/usr/klibc/arch/ppc64/setjmp.S @@ -5,17 +5,21 @@ # .text - .align 4 - + .balign 4 + .globl setjmp +#if _CALL_ELF == 2 + .type setjmp,@function +setjmp: +#else .section .opd,aw + .balign 8 setjmp: - .quad .setjmp,.TOC.@tocbase,0 + .quad .setjmp, .TOC.@tocbase, 0 .previous - .size setjmp,24 .type .setjmp,@function - .globl setjmp .globl .setjmp .setjmp: +#endif mflr %r11 /* save return address */ mfcr %r12 /* save condition register */ std %r2,0(%r3) /* save TOC pointer (not needed) */ @@ -43,17 +47,28 @@ setjmp: std %r31,8(%r3) li %r3,0 /* indicate success */ blr/* return */ +#if _CALL_ELF == 2 + .size setjmp,.-setjmp +#else + .size setjmp,.-.setjmp +#endif - .size .setjmp,.-.setjmp + .text + .balign 4 + .globl longjmp +#if _CALL_ELF == 2 + .type longjmp,@function +longjmp: +#else .section .opd,aw + .balign 8 longjmp: - .quad .longjmp,.TOC.@tocbase,0 + .quad .longjmp, .TOC.@tocbase, 0 .previous - .size longjmp,24 .type .longjmp,@function - .globl longjmp .globl .longjmp .longjmp: +#endif ld %r2,0(%r3) /* restore TOC pointer (not needed) */ ldu %r1,8(%r3) /* restore stack */ ldu %r11,8(%r3) @@ -81,5 +96,8 @@ longjmp: mtcr %r12 /* restore CR */ mr %r3,%r4 /* get return value */ blr/* return */ - - .size .longjmp,.-.longjmp +#if _CALL_ELF == 2 + .size longjmp,.-longjmp +#else + .size longjmp,.-.longjmp +#endif diff --git a/usr/klibc/arch/ppc64/sysstub.ph b/usr/klibc/arch/ppc64/sysstub.ph index 9ee9370..b3f6e38 100644 --- a/usr/klibc/arch/ppc64/sysstub.ph +++ b/usr
Bug#744884: Update severity and tags
Control: severity -1 important Control: tags -1 patch thank you -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744884: 744884 usertags
user debian-powe...@lists.debian.org usertag 744884 ppc64el -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744844: 744884 usertags
Control: user debian-powe...@lists.debian.org Control: usertag -1 ppc64el Apologies for the previous superfluous message incorrectly setting usertags. And thanks for taking the time for a new upstream release. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#744884: 744884 usertags
Control: user debian-powe...@lists.debian.org Control: usertag -1 ppc64el Apologies for the previous superfluous message incorrectly setting usertags. And thanks for taking the time for a new upstream release. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#541172: Any update? the patch fixes the issue
Package: net-tools Control: found -1 net-tools/1.60-25 Hi maintainer, This issue still exists. The patch in message #15 fixes it. Is there any outlook or opinion on putting it in? :) Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747367: src:linux add ppc64el (Little Endian 64-bit PowerPC) as a target for linux-libc-dev
Package: src:linux Version: 3.14.2-1 Severity: wishlist Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el quit Hi maintainers, This patch adds ppc64el minimal bits into the defines files for building the linux-libc-dev package. This is mainly desired for the rebootstrap project, which builds that package straight from debian/rules.gen. Thank you. P.S.: the or1k arch has a similar patch (bug 746309); the patches don't conflict. -- Mauricio Faria de Oliveira IBM Linux Technology Center Index: linux-3.14.2/debian/config/defines === --- linux-3.14.2.orig/debian/config/defines 2014-04-28 11:46:12.0 -0300 +++ linux-3.14.2/debian/config/defines 2014-05-07 18:58:17.0 -0300 @@ -17,6 +17,7 @@ powerpc powerpcspe ppc64 + ppc64el s390 s390x sh4 Index: linux-3.14.2/debian/config/ppc64el/defines === --- /dev/null 1970-01-01 00:00:00.0 + +++ linux-3.14.2/debian/config/ppc64el/defines 2014-05-07 19:01:44.0 -0300 @@ -0,0 +1,4 @@ +[base] +kernel-arch: powerpc +featuresets: +# empty
Bug#747367: thanks
Thank you ;) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751796: Patch for dh-autoreconf on gnutls26
Package: src:gnutls26 Version: 2.12.23-16 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Hi maintainers, This patch adds support for dh-autoreconf on gnutls26. Please consider incorporating it for an upload; it would greatly help the Debian ppc64el port and new ports. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center Index: gnutls26-2.12.23/debian/control === --- gnutls26-2.12.23.orig/debian/control +++ gnutls26-2.12.23/debian/control @@ -9,7 +9,8 @@ Build-Depends: debhelper (= 9), libgcrypt11-dev (= 1.4.0), zlib1g-dev, cdbs (= 0.4.93), gtk-doc-tools, texinfo (= 4.8), libtasn1-6-dev, autotools-dev, datefudge, - libp11-kit-dev (= 0.11) [!or1k], pkg-config, chrpath + libp11-kit-dev (= 0.11) [!or1k], pkg-config, chrpath, + dh-autoreconf, automake1.11 Build-Conflicts: libgnutls-dev Standards-Version: 3.9.5 Vcs-Git: git://anonscm.debian.org/pkg-gnutls/gnutls.git -b gnutls26-master Index: gnutls26-2.12.23/debian/rules === --- gnutls26-2.12.23.orig/debian/rules +++ gnutls26-2.12.23/debian/rules @@ -3,6 +3,10 @@ include /usr/share/cdbs/1/rules/debhelper.mk include /usr/share/cdbs/1/class/autotools.mk +include /usr/share/cdbs/1/rules/autoreconf.mk + +export AUTOMAKE = automake-1.11 +export ACLOCAL = aclocal-1.11 DEB_CONFIGURE_EXTRA_FLAGS = --enable-ld-version-script --enable-cxx \ --without-lzo --disable-guile \
Bug#751796: reason for automake/aclocal 1.11
Just for the record, automake/aclocal 1.11 is needed as stuff in gnutls26 generates warnings (treated as errors) on newer, 1.14: autoreconf: running: automake --add-missing --copy --force-missing automake: warnings are treated as errors configure.ac:41: warning: The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged. configure.ac:41: You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead, configure.ac:41: and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files. configure.ac:33: installing 'build-aux/compile' /usr/share/automake-1.14/am/ltlibrary.am: warning: 'libgnutls.la': linking libtool libraries using a non-POSIX /usr/share/automake-1.14/am/ltlibrary.am: archiver requires 'AM_PROG_AR' in 'configure.ac' [... snip, similar repetitions ... ] autoreconf: automake failed with exit status: 1 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751822: Fix FTBFS on ppc64el (test-suite + python binding)
Package: src:libprelude
Version: 1.0.0-1.0.0-11.2
Severity: normal
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Hi,
These 2 patches address build failures of libprelude on ppc64el.
May you please consider incorporating them into an upload?
Thank you!
1) ppc64el-isnan-tests-fix-for-little-endian-PowerPC.patch
This patch is upstream at gnulib as of May 30th, 2014
(commit e962c07c0c8bb18f9a5969cbf1ddb01d0fe4f55c).
It picks the subset applicable to files carried by libprelude.
It fixes this test-suite error:
PASS: test-isnand-nolibm
PASS: test-isnanf-nolibm
../../test-driver: line 107: 20059 Aborted $@
$log_file 21
FAIL: test-isnanl-nolibm
2) python-libprelude-prefix.patch
This patch makes sure bindings/python/setup.py uses '/usr'
as prefix, since it can vary (occurence of '/usr/local' below).
If the prefix is different then /usr, a build failure occurs
because of a hardcoded '/usr/lib' in override_dh_auto_install:
[...]
debian/rules binary
dh binary --with=quilt,python2,autoreconf
[...]
debian/rules override_dh_auto_install
[...]
dh_auto_install; \
rm -rf debian/tmp/usr/lib/python*; \
find debian/tmp-python-libprelude/usr/lib -name *.la -delete;
\
mv debian/tmp-python-libprelude/usr/lib/* debian/tmp/usr/lib/
[...]
find: `debian/tmp-python-libprelude/usr/lib': No such file or directory
mv: cannot stat ‘debian/tmp-python-libprelude/usr/lib/*’: No such file
or directory
make[1]: *** [override_dh_auto_install] Error 1
[...]
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
Index: libprelude-1.0.0/bindings/python/Makefile.am
===
--- libprelude-1.0.0.orig/bindings/python/Makefile.am
+++ libprelude-1.0.0/bindings/python/Makefile.am
@@ -9,7 +9,7 @@
CC=$(CXX) $(PYTHON) setup.py build
install-exec-hook:
- $(PYTHON) setup.py install `test -n $(DESTDIR) echo --root $(DESTDIR)`
+ $(PYTHON) setup.py install `test -n $(DESTDIR) echo --root $(DESTDIR)` --prefix /usr
uninstall-hook:
$(PYTHON) setup.py uninstall `test -n $(DESTDIR) echo --root $(DESTDIR)`
curl 'http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=patch;h=e962c07c0c8bb18f9a5969cbf1ddb01d0fe4f55c' \
| filterdiff \
--strip=1 \
--addoldprefix='a/libmissing/' \
--addnewprefix='b/libmissing/' \
-i '*/tests/test-isnanl.h' \
-i '*/tests/test-signbit.c' \
'ppc64el-isnan-tests-fix-for-little-endian-PowerPC.patch'
--- a/libmissing/tests/test-isnanl.h
+++ b/libmissing/tests/test-isnanl.h
@@ -51,6 +51,15 @@ main ()
/* A bit pattern that is different from a Quiet NaN. With a bit of luck,
it's a Signalling NaN. */
{
+#if defined __powerpc__ LDBL_MANT_DIG == 106
+/* This is PowerPC double double, a pair of two doubles. Inf and Nan are
+ represented as the corresponding 64-bit IEEE values in the first double;
+ the second is ignored. Manipulate only the first double. */
+#undef NWORDS
+#define NWORDS \
+ ((sizeof (double) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
+#endif
+
memory_long_double m;
m.value = NaNl ();
# if LDBL_EXPBIT0_BIT 0
--- a/libmissing/tests/test-signbit.c
+++ b/libmissing/tests/test-signbit.c
@@ -151,6 +151,16 @@ test_signbitl ()
#define NWORDS \
((sizeof (long double) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
typedef union { long double value; unsigned int word[NWORDS]; } memory_long_double;
+
+#if defined __powerpc__ LDBL_MANT_DIG == 106
+/* This is PowerPC double double, a pair of two doubles. Inf and Nan are
+ represented as the corresponding 64-bit IEEE values in the first double;
+ the second is ignored. Manipulate only the first double. */
+#undef NWORDS
+#define NWORDS \
+ ((sizeof (double) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
+#endif
+
memory_long_double m;
m.value = zerol / zerol;
# if LDBL_EXPBIT0_BIT 0
Bug#751917: ghostscript: add ppc64el to symbols file
Package: src:ghostscript Version: 9.05~dfsg-8.1 Severity: normal Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Hi maintainers, This patch adds ppc64el to the symbols file. May you please consider it for an upload? Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center Index: ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in === --- ghostscript-9.05~dfsg.orig/debian/libgs__VER__.symbols.in +++ ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in @@ -1,5 +1,5 @@ libgs.so.__VER__ libgs__VER__ #MINVER# #include symbols.common (arch=linux-any)#include symbols.common_linux -(arch=!any-alpha !any-amd64 !any-arm64 !any-ia64 !any-ppc64 !any-s390x !any-sparc64)#include symbols.common_32bit -(arch=any-alpha any-amd64 any-arm64 any-armel any-i386 any-ia64 any-mipsel any-sh3 any-sh4)#include symbols.common_le +(arch=!any-alpha !any-amd64 !any-arm64 !any-ia64 !any-ppc64 !any-ppc64el !any-s390x !any-sparc64)#include symbols.common_32bit +(arch=any-alpha any-amd64 any-arm64 any-armel any-i386 any-ia64 any-mipsel any-ppc64el any-sh3 any-sh4)#include symbols.common_le
Bug#689622: patch for dh-autoreconf
Package: src:libnih Version: 1.0.3-4.2 User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Hi, This trivial patch adds dh-autoreconf to libnih. May you please consider it for an upload? It would greatly help the Debian ppc64el port and new ports. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center Index: libnih-1.0.3/debian/rules === --- libnih-1.0.3.orig/debian/rules 2012-12-31 14:54:25.0 -0200 +++ libnih-1.0.3/debian/rules 2014-06-18 09:52:34.0 -0300 @@ -1,6 +1,6 @@ #!/usr/bin/make -f %: - dh $@ + dh $@ --with autoreconf CFLAGS = -Wall -g -fstack-protector -fPIE Index: libnih-1.0.3/debian/control === --- libnih-1.0.3.orig/debian/control2012-12-31 14:54:25.0 -0200 +++ libnih-1.0.3/debian/control 2014-06-18 09:53:02.0 -0300 @@ -3,7 +3,7 @@ Priority: optional Maintainer: Scott James Remnant sc...@netsplit.com Standards-Version: 3.9.1 -Build-Depends: debhelper (= 8), pkg-config (= 0.22), libdbus-1-dev (= 1.4), libexpat1-dev (= 2.0.0), dbus (= 1.4) +Build-Depends: debhelper (= 8), pkg-config (= 0.22), libdbus-1-dev (= 1.4), libexpat1-dev (= 2.0.0), dbus (= 1.4), dh-autoreconf Vcs-Git: git://git.debian.org/git/collab-maint/libnih.git Vcs-Browser: http://git.debian.org/?p=collab-maint/libnih.git;a=summary Homepage: https://launchpad.net/libnih
Bug#751828: pcre3: FTBFS [ppc64el]: Test failure in common with amd64
Package: src:pcre3
User: debian-powe...@lists.debian.org
Usertags: ppc64el
This bug also affects ppc64el (no JIT).
Documenting the same pattern as comment above, from test-suite.log:
[...]
FAIL: RunTest
=
[...]
Testing 8-bit library
[...]
Test 2: API, errors, internals, and non-Perl stuff (not UTF-8)
--- ./testdata/testoutput2 2012-06-01 14:53:58.0 -0300
+++ testtry 2014-06-18 11:22:44.0 -0300
@@ -5794,13 +5794,16 @@
No match
/a{}/I
-Failed: number too big in {} quantifier at offset 22
+Capturing subpattern count = 0
+No options
+First char = 'a'
+No need char
/(){64294967295}/I
-Failed: number too big in {} quantifier at offset 14
+Failed: regular expression is too large at offset 15
/(){2,4294967295}/I
-Failed: number too big in {} quantifier at offset 15
+Failed: numbers out of order in {} quantifier at offset 15
[...]
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751828: Note about ppc64el, autoreconf
I am looking into this a bit.. it might be something to do with libtool
and/or autoreconf.
The relinking in pcretest (from .libs/pcretest to .libs/lt-pcretest)
seems to create the condition for the failure.
(apologies for reporting in this bug, since the original package does
not do autoreconf.. but I hope reporting and helping investigate might
help, since amd64 sees this.)
Case 0) .libs/pcretest (OK)
$ .libs/pcretest -q ./testdata/testinput2 test-output
$ diff ./testdata/testoutput2 test-output
$
Case 1) .libs/*lt-*pcretest (NOT OK)
$ .libs/lt-pcretest -q ./testdata/testinput2 test-output
$ diff ./testdata/testoutput2 test-output
5797c5797,5800
Failed: number too big in {} quantifier at offset 22
---
Capturing subpattern count = 0
No options
First char = 'a'
No need char
5800c5803
Failed: number too big in {} quantifier at offset 14
---
Failed: regular expression is too large at offset 15
5803c5806
Failed: number too big in {} quantifier at offset 15
---
Failed: numbers out of order in {} quantifier at offset 15
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751828: ppc64el: error happened due to old environment
Package: src:pcre3 On ppc64el, I could verify this error does not happen with more recent packages. I didn't track down exactly what is the change, but it doesn't fail anymore. Maybe the original bug opener could retry after [dist-]upgrade? For the record, with my problematic old environment, the rpath argument to the linker, in relink_command, was necessary to trigger the failure: $ powerpc64le-linux-gnu-gcc \ -Wall -g -O2 -o \ .libs/lt-pcretest pcretest.o pcre_printint.o \ ./.libs/libpcre.so ./.libs/libpcreposix.so \ -Wl,-rpath -Wl,/root/pcre3/pcre3-8.31/.libs # this line. So I would think the problematic old package built something wrong into .libs/. The same command is executed in the new environment, but the test-suite passes with no failures. Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751424: Enable autoreconf for ppc64el
Hi Bill, On 06/22/2014 01:05 PM, Bill Allombert wrote: Thanks for you report! You're welcome. Thanks for looking into this. :) Could you give more detail ? ppc64el is not listed on http://buildd.debian-ports.org so there no log available. I suspect libtool, but I like more information. Sure. IIRC it was not yet on d-p.o for lack of resources there (hardware, I believe), but that would be alleviated with hardware donation once it is available. There is buildd running at Unicamp (also a Debian mirror in Brazil). This is libjpeg8 build log [1]. $ wget ftp://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/libjpeg8_8d-2_ppc64el.build [...] $ grep 'shared libraries' libjpeg8_8d-2_ppc64el.build checking whether the powerpc64le-linux-gnu-gcc -std=gnu99 linker (/usr/bin/ld -m elf64ppc) supports shared libraries... no checking if libtool supports shared libraries... no checking whether to build shared libraries... no $ grep '\.so' libjpeg8_8d-2_ppc64el.build checking dynamic linker characteristics... GNU/Linux ld.so $ Is there a porterbox or an archive ? There is more info about ppc64el and a porterbox on its Debian wiki page [2], which is also listed on db.d.o [3]. You can request access for the system there, or just log-in if you're in db.d.o. Feel free to ping me should you have any issues requesting access to the folks mentioned there. Thanks again, [1] ftp://ftp.unicamp.br/pub/ppc64el/debian/buildd-upstream/build_logs/logs/libjpeg8_8d-2_ppc64el.build [2] https://wiki.debian.org/ppc64el#Development [3] https://db.debian.org/machines.cgi?host=pastel -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752784: aclocal-1.11 warnings with perl = 5.16
Package: src:automake1.11
Version: 1:1.11.6-2
Tags: patch
Hi Eric,
aclocal 1.11 prints this warning with perl = 5.16:
main::scan_file() called too early to check prototype at
/usr/bin/aclocal line 643.
This issue was reported and fixed upstream on automake 1.12.1 [1].
The attached patch is a trivial backport from that fix (changes:
s/spaces/tabs/
on THANKS, and quilt refresh to fix a minor fuzz 1 due to '^L' vs empty
line).
I couldn't find significant differences with the fix applied, on a
particular test
(below), but I would ask the maintainer(s) for a more general
opinion/evaluation,
given my shallow knowledge about the tool.
Thank you.
[1] https://lists.gnu.org/archive/html/bug-automake/2012-05/msg00034.html
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru automake1.11-1.11.6/debian/changelog
automake1.11-1.11.6/debian/changelog
--- automake1.11-1.11.6/debian/changelog2013-06-24 14:35:57.0
-0300
+++ automake1.11-1.11.6/debian/changelog2014-06-25 15:32:49.0
-0300
@@ -1,3 +1,12 @@
+automake1.11 (1:1.11.6-2.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * debian/patches/04-aclocal-function-prototypes.patch: Fix for the warning
message
+'main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 643.'
+with perl = 5.16 (from automake 1.12.1).
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Wed, 25 Jun 2014
15:27:21 -0300
+
automake1.11 (1:1.11.6-2) unstable; urgency=low
* Reupload to unstable with binary package renamed to automake1.11.
diff -Nru
automake1.11-1.11.6/debian/patches/04-aclocal-function-prototypes.patch
automake1.11-1.11.6/debian/patches/04-aclocal-function-prototypes.patch
--- automake1.11-1.11.6/debian/patches/04-aclocal-function-prototypes.patch
1969-12-31 21:00:00.0 -0300
+++ automake1.11-1.11.6/debian/patches/04-aclocal-function-prototypes.patch
2014-06-25 15:36:22.0 -0300
@@ -0,0 +1,136 @@
+Origin: https://lists.gnu.org/archive/html/bug-automake/2012-05/msg00034.html
+From 72ed7e00f847ce1ab3c8d460a5a4dcc06a3c560a Mon Sep 17 00:00:00 2001
+Message-Id:
72ed7e00f847ce1ab3c8d460a5a4dcc06a3c560a.1338205618.git.stefano.lattar...@gmail.com
+From: Stefano Lattarini stefano.lattar...@gmail.com
+Date: Mon, 28 May 2012 13:32:03 +0200
+Subject: [PATCH] aclocal: declare function prototypes, do not use '' in
+ function calls
+
+This change will also fix automake bug#11543 (from a report by Matt
+Burgess).
+
+* aclocal.in: Declare prototypes for almost all functions early, before
+any actual function definition (but omit the prototype for the dynamically
+generated 'search' function). Add prototypes to any function definition.
+Remove '' from function invocations (i.e., simply use func(ARGS..)
+instead of func(ARGS...)).
+* THANKS: Update.
+
+Signed-off-by: Stefano Lattarini stefano.lattar...@gmail.com
+---
+ THANKS |1 +
+ aclocal.in | 42 ++
+ 2 files changed, 35 insertions(+), 8 deletions(-)
+
+Index: automake1.11-1.11.6/THANKS
+===
+--- automake1.11-1.11.6.orig/THANKS
automake1.11-1.11.6/THANKS
+@@ -231,6 +231,7 @@ Martin Waitz t...@admingilde.org
+ Mathias Doreille dorei...@smr.ch
+ Mathias Froehlich m.froehl...@science-computing.de
+ Mathias Hasselmannmathias.hasselm...@gmx.de
++Matt Burgess matt...@linuxfromscratch.org
+ Matt Leachmle...@cygnus.com
+ Matthew D. Langston langs...@slac.stanford.edu
+ Matthias Andree matthias.and...@gmx.de
+Index: automake1.11-1.11.6/aclocal.in
+===
+--- automake1.11-1.11.6.orig/aclocal.in
automake1.11-1.11.6/aclocal.in
+@@ -152,8 +152,34 @@ my $erase_me;
+
+
+
++# Prototypes for all subroutines.
++
++sub unlink_tmp (;$);
++sub xmkdir_p ($);
++sub check_acinclude ();
++sub reset_maps ();
++sub install_file ($$);
++sub list_compare (\@\@);
++sub scan_m4_dirs ($@);
++sub scan_m4_files ();
++sub add_macro ($);
++sub scan_configure_dep ($);
++sub add_file ($);
++sub scan_file ($$$);
++sub strip_redundant_includes (%);
++sub trace_used_macros ();
++sub scan_configure ();
++sub write_aclocal ($@);
++sub usage ($);
++sub version ();
++sub handle_acdir_option ($$);
++sub parse_arguments ();
++sub parse_ACLOCAL_PATH ();
++
++
++
+ # Erase temporary file ERASE_ME. Handle signals.
+-sub unlink_tmp
++sub unlink_tmp (;$)
+ {
+ my ($sig) = @_;
+
+@@ -351,7 +377,7 @@ sub scan_m4_dirs ($@)
+ next if $file eq 'aclocal.m4';
+
+ my $fullfile = File::Spec-canonpath ($m4dir/$file);
+- scan_file ($type, $fullfile, 'aclocal');
++scan_file ($type, $fullfile, 'aclocal');
+ }
+ closedir (DIR
Bug#752784: For the record
Package: src:automake1.11
A few additional comments:
Examples of packages affected (Build-Depends on automake1.11 and
(dh-)?auto(re)?conf)
and its build logs (search for the error message):
gnupg2
https://buildd.debian.org/status/fetch.php?pkg=gnupg2arch=powerpcver=2.0.24-1stamp=1403673415
isl
https://buildd.debian.org/status/fetch.php?pkg=islarch=hurd-i386ver=0.12.2-2stamp=1403743045
openjdk-6
https://buildd.debian.org/status/fetch.php?pkg=openjdk-6arch=mipsver=6b31-1.13.3-1stamp=1397869346
openjdk-7
https://buildd.debian.org/status/fetch.php?pkg=openjdk-7arch=mipsver=7u55-2.4.7-2stamp=1400449158
Difference in results (dh_autoreconf on libjpeg8-8d, without/with
aclocal patched).
negligible difference (commas) on autom4te.cache.
(unstable-ppc64el-sbuild)~/j8# diff -qr libjpeg8-8d
libjpeg8-8d.new_aclocal/
Files libjpeg8-8d/autom4te.cache/requests and
libjpeg8-8d.new_aclocal/autom4te.cache/requests differ
Files libjpeg8-8d/debian/autoreconf.after and
libjpeg8-8d.new_aclocal/debian/autoreconf.after differ
(unstable-ppc64el-sbuild)~/j8# diff
libjpeg8-8d/debian/autoreconf.after
libjpeg8-8d.new_aclocal/debian/autoreconf.after
177c177
f1147bf4900c0f5fc2c19196ef444129 ./autom4te.cache/requests
---
38bd679df2dcf59cf242f0994a61a9a6 ./autom4te.cache/requests
(unstable-ppc64el-sbuild)~/j8# sort libjpeg8-8d/autom4te.cache/requests
a
(unstable-ppc64el-sbuild)~/j8# sort
libjpeg8-8d.new_aclocal/autom4te.cache/requests b
(unstable-ppc64el-sbuild)~/j8# diff a b
45c45
'AC_DEFINE_TRACE_LITERAL' = 1,
---
'AC_DEFINE_TRACE_LITERAL' = 1
113c113
'AC_PROG_NM' = 1,
---
'AC_PROG_NM' = 1
141c141
'AM_NLS' = 1
---
'AM_NLS' = 1,
228c228
'_LT_AC_LANG_RC_CONFIG' = 1
---
'_LT_AC_LANG_RC_CONFIG' = 1,
(unstable-ppc64el-sbuild)~/j8#
Patch creation steps:
( echo 'Origin:
https://lists.gnu.org/archive/html/bug-automake/2012-05/msg00034.html';
wget ftp://lists.gnu.org/bug-automake/2012-05 -O - \
| sed -n '/^From
72ed7e00f847ce1ab3c8d460a5a4dcc06a3c560a/,/^1.7.9.5/p' \
| sed -e '/^diff.*THANKS$/,/^diff/ { /^[ +]M/ { s/\( \)\{2,17\}/\t/g
} }'
)
aclocal-declare-function-prototypes-do-not-use-ampersand-in-function-calls.patch
quilt import -P 04-aclocal-function-prototypes.patch
aclocal-declare-function-prototypes-do-not-use-ampersand-in-function-calls.patch
quilt push
quilt refresh
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751424: Enable autoreconf for ppc64el
Hi Bill, Thanks for the thought provoking questions. Did ou get them also ? [...] Yes, I did get them. I assumed they were harmless/just warnings because dh-autoreconf finished with success and the package test-suite passed. But then.. [...] Do you know what they mean ? Well, now I do. Since you asked, I investigated them a bit.. and that assumption looks correct. This message is just a warning, harmless: main::scan_file() called too early to check prototype at /usr/bin/aclocal-1.11 line 643. It was fixed upstream on automake 1.12.1, but not on 1.11 (unnoticed on Debian as automake1.11 has the test-suite disabled). Just in case, I submitted #752784, but the difference in dh-autoreconf's result with/ without the fix is effectively null (see its message 10). These messages from libtoolize are harmless too: libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'. libtoolize: copying file `./ltmain.sh' libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac and libtoolize: rerunning libtoolize, to keep the correct libtool macros in-tree. libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am. If you implement the suggested considerations from libtoolize, it will just copy the libtool macros as individual files in the m4/ dir. If you don't (as it is), it will just copy the contents of those files in aclocal.m4 (next e-mail) -- with identical results. Since both cases work fine, and dh_autoreconf_clean will clean-up that output anyway, I would not bother with carrying a new patch only for silencing a warning from libtoolize (and creating empty m4/ dir, so to avoid an aclocal error due to '-I m4/', populated by libtoolize later). For your convenience, I attached that patch, nonetheless. I hope this clarifies those questions. Would the patch(es) be good to go, then? Thanks! -- Mauricio Faria de Oliveira IBM Linux Technology Center --- libjpeg8-8d/Makefile.am +++ libjpeg8-8d.libtoolize/Makefile.am @@ -5,6 +5,9 @@ # This file is written by Bob Friesenhahn, Guido Vollbeding # +# For libtoolize/aclocal +ACLOCAL_AMFLAGS = -I m4 + # Sources to build library LIBSOURCES = jaricom.c jcapimin.c jcapistd.c jcarith.c jccoefct.c jccolor.c \ jcdctmgr.c jchuff.c jcinit.c jcmainct.c jcmarker.c jcmaster.c \ --- libjpeg8-8d/configure.ac +++ libjpeg8-8d.libtoolize/configure.ac @@ -10,6 +10,9 @@ AC_INIT([libjpeg], [8.4.0]) # Directory where autotools helper scripts lives. AC_CONFIG_AUX_DIR([.]) +# Directory where libtool macros scripts lives. +AC_CONFIG_MACRO_DIR([m4]) + # Generate configuration headers. AC_CONFIG_HEADERS([jconfig.h:jconfig.cfg])
Bug#751424: Enable autoreconf for ppc64el
Details, for reference:
On 06/26/2014 12:20 PM, Mauricio Faria de Oliveira wrote:
[...]
If you don't (as it is), it will just copy the contents of those files
in aclocal.m4 (next e-mail) -- with identical results.
dh_autoreconf as before (no aclocal macros/include on m4 dir):
(unstable-ppc64el-sbuild)~/j8/libjpeg8-8d# dh_autoreconf
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 643.
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: Consider adding `AC_CONFIG_MACRO_DIR([m4])' to configure.ac
and
libtoolize: rerunning libtoolize, to keep the correct libtool macros
in-tree.
libtoolize: Consider adding `-I m4' to ACLOCAL_AMFLAGS in Makefile.am.
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 643.
(unstable-ppc64el-sbuild)~/j8/libjpeg8-8d#
dh_autoreconf with libtoolize considerations (aclocal macros/include on
m4 dir):
(unstable-ppc64el-sbuild)~/j8/libjpeg8-8d.libtoolize# dh_autoreconf
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 643.
libtoolize: putting auxiliary files in AC_CONFIG_AUX_DIR, `.'.
libtoolize: copying file `./ltmain.sh'
libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'.
libtoolize: copying file `m4/libtool.m4'
libtoolize: copying file `m4/ltoptions.m4'
libtoolize: copying file `m4/ltsugar.m4'
libtoolize: copying file `m4/ltversion.m4'
libtoolize: copying file `m4/lt~obsolete.m4'
main::scan_file() called too early to check prototype at
/usr/bin/aclocal-1.11 line 643.
(unstable-ppc64el-sbuild)~/j8/libjpeg8-8d.libtoolize#
diff between both cases produces equivalent result:
- configure{.ac,} and Makefile.{am,in} differ due to including the
libtoolize considerations
- aclocal.m4 no longer 'includes' the files which are now in the (new)
m4/ dir
- autom4te.cache and autoreconf.{before,after} differ due to the
differences above
unstable-ppc64el-sbuild)~/j8# diff -qr libjpeg8-8d
libjpeg8-8d.libtoolize/
Files libjpeg8-8d/Makefile.am and libjpeg8-8d.libtoolize/Makefile.am
differ
Files libjpeg8-8d/Makefile.in and libjpeg8-8d.libtoolize/Makefile.in
differ
Files libjpeg8-8d/aclocal.m4 and libjpeg8-8d.libtoolize/aclocal.m4
differ
Files libjpeg8-8d/autom4te.cache/output.0 and
libjpeg8-8d.libtoolize/autom4te.cache/output.0 differ
Files libjpeg8-8d/autom4te.cache/output.1 and
libjpeg8-8d.libtoolize/autom4te.cache/output.1 differ
Only in libjpeg8-8d.libtoolize/autom4te.cache: output.2
Files libjpeg8-8d/autom4te.cache/requests and
libjpeg8-8d.libtoolize/autom4te.cache/requests differ
Files libjpeg8-8d/autom4te.cache/traces.0 and
libjpeg8-8d.libtoolize/autom4te.cache/traces.0 differ
Files libjpeg8-8d/autom4te.cache/traces.1 and
libjpeg8-8d.libtoolize/autom4te.cache/traces.1 differ
Only in libjpeg8-8d.libtoolize/autom4te.cache: traces.2
Files libjpeg8-8d/configure and libjpeg8-8d.libtoolize/configure differ
Files libjpeg8-8d/configure.ac and libjpeg8-8d.libtoolize/configure.ac
differ
Files libjpeg8-8d/debian/autoreconf.after and
libjpeg8-8d.libtoolize/debian/autoreconf.after differ
Files libjpeg8-8d/debian/autoreconf.before and
libjpeg8-8d.libtoolize/debian/autoreconf.before differ
Only in libjpeg8-8d.libtoolize/: m4
(unstable-ppc64el-sbuild)~/j8#
- aclocal.m4 previously 'included' the files which are now in the (new)
m4/ dir -- equivalent functionality:
(unstable-ppc64el-sbuild)~/j8# ls -1 libjpeg8-8d.libtoolize/m4/*
libjpeg8-8d.libtoolize/m4/libtool.m4
libjpeg8-8d.libtoolize/m4/ltoptions.m4
libjpeg8-8d.libtoolize/m4/ltsugar.m4
libjpeg8-8d.libtoolize/m4/ltversion.m4
libjpeg8-8d.libtoolize/m4/lt~obsolete.m4
(unstable-ppc64el-sbuild)~/j8# for file in libjpeg8-8d.libtoolize/m4/*;
do fgrep $(head -n1 $file) libjpeg8-8d/aclocal.m4; done
# libtool.m4 - Configure libtool for the host system. -*-Autoconf-*-
# Helper functions for option handling.-*- Autoconf
-*-
# ltsugar.m4 -- libtool m4 base layer.
-*-Autoconf-*-
# ltversion.m4 -- version numbers -*- Autoconf -*-
# lt~obsolete.m4 -- aclocal satisfying obsolete definitions.
-*-Autoconf-*-
(unstable-ppc64el-sbuild)~/j8#
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750481: Patch for updating libtool (reconf)
Package: src:db5.3
Version: 5.3.28-4
Tags: patch
Hi,
Thanks for the first fix attempt. It helped a /lot/ in understanding
how reconf should be done here.
The package still failed to build as before. After playing for a while,
I added a few changes on top of those in 5.3.28-4, and now the package
is building properly.
For the record, the first fix didn't build shares libraries because it
didn't actually modify dist/aclocal.m4, as libtoolize was not run in
dist/, and it also didn't modify files lang/sql/sqlite files, needed
for libdb5.3-sql{,-dev}.
The attached patch fixes both issues, finishing the build successfully.
I will send another e-mail with some documentation.
May you please consider incorporating it in another upload?
Thank you,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru db5.3-5.3.28/debian/changelog db5.3-5.3.28/debian/changelog
--- db5.3-5.3.28/debian/changelog 2014-06-23 09:36:32.0 -0300
+++ db5.3-5.3.28/debian/changelog 2014-06-26 20:06:49.0 -0300
@@ -1,3 +1,14 @@
+db5.3 (5.3.28-4.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Run libtoolize in dist/ (to actually update dist/aclocal.m4)
+ * Run libtoolize and autoconf in lang/sql/sqlite/ (to build sqlite shared
libraries),
+with autoconf performed by dist/s_config (patch:
008-autoconf-in-lang-sql-sqlite).
+ * Accordingly, update the clean and override_dh_auto_configure targets.
+ * Small fixes to the test-file/dir/exist operators and rmdir '-f' argument.
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 26 Jun 2014
19:50:04 -0300
+
db5.3 (5.3.28-4) unstable; urgency=medium
* Add fix for ppc 64K pages needed for OpenLDAP (Courtesy of Cedric Le
Goater)
diff -Nru db5.3-5.3.28/debian/patches/008-autoconf-in-lang-sql-sqlite.patch
db5.3-5.3.28/debian/patches/008-autoconf-in-lang-sql-sqlite.patch
--- db5.3-5.3.28/debian/patches/008-autoconf-in-lang-sql-sqlite.patch
1969-12-31 21:00:00.0 -0300
+++ db5.3-5.3.28/debian/patches/008-autoconf-in-lang-sql-sqlite.patch
2014-06-26 20:06:49.0 -0300
@@ -0,0 +1,16 @@
+Index: db5.3-5.3.28/dist/s_config
+===
+--- db5.3-5.3.28.orig/dist/s_config
db5.3-5.3.28/dist/s_config
+@@ -35,3 +35,11 @@ rm -rf autom4te.cache
+ chmod 755 configure
+
+ chmod 755 config.guess config.sub install-sh
++
++echo autoconf: running autoconf to build configure (lang/sql/sqlite/)
++cp aclocal.m4 ../lang/sql/sqlite/
++cd ../lang/sql/sqlite/
++rm -f configure
++autoconf
++cd ../../../dist/
++
diff -Nru db5.3-5.3.28/debian/patches/series db5.3-5.3.28/debian/patches/series
--- db5.3-5.3.28/debian/patches/series 2014-06-23 09:36:32.0 -0300
+++ db5.3-5.3.28/debian/patches/series 2014-06-26 20:06:49.0 -0300
@@ -5,3 +5,4 @@
006-mutex_alignment.patch
007-link-sql-libs.patch
mmap_extend-mode-requires-page-aligned-extends.patch
+008-autoconf-in-lang-sql-sqlite.patch
diff -Nru db5.3-5.3.28/debian/rules db5.3-5.3.28/debian/rules
--- db5.3-5.3.28/debian/rules 2014-06-23 09:36:32.0 -0300
+++ db5.3-5.3.28/debian/rules 2014-06-26 20:06:49.0 -0300
@@ -123,22 +123,32 @@
version=$(shell expr `pwd` : '.*-\([0-9.]*\)')
version_major=$(shell expr `pwd` : '.*-\([0-9]*\).[0-9.]*')
-RECONF_FILES=config.hin configure aclocal/libtool.m4 aclocal/ltoptions.m4 \
-aclocal/ltversion.m4 config.guess config.sub install-sh ltmain.sh
+LIBTOOL_AUX_FILES=config.guess config.sub install-sh ltmain.sh
+LIBTOOL_MACROS_FILES=libtool.m4 ltoptions.m4 ltsugar.m4 ltversion.m4
lt~obsolete.m4
+
+RECONF_FILES=dist/config.hin \
+ dist/configure \
+ $(patsubst %,dist/%,$(LIBTOOL_AUX_FILES)) \
+ $(patsubst %,dist/aclocal/%,$(LIBTOOL_MACROS_FILES)) \
+ lang/sql/sqlite/aclocal.m4 \
+ lang/sql/sqlite/configure \
+ $(patsubst %,lang/sql/sqlite/%,$(LIBTOOL_AUX_FILES))
%:
dh $@ --with=autotools-dev $(DH_PLUGINS)
override_dh_auto_configure:
if [ ! -d $(CURDIR)/debian/s_config ]; then \
- mkdir $(CURDIR)/debian/s_config/ $(CURDIR)/debian/s_config/aclocal/; \
+ mkdir -p $(CURDIR)/debian/s_config/dist/aclocal/ \
+ $(CURDIR)/debian/s_config/lang/sql/sqlite/; \
fi
for f in $(RECONF_FILES); do \
- if [ ! $(CURDIR)/debian/s_config/$$f ]; then \
- mv $(CURDIR)/dist/$$f $(CURDIR)/debian/s_config/; \
+ if [ ! -f $(CURDIR)/debian/s_config/$$f ]; then \
+ mv $(CURDIR)/$$f $(CURDIR)/debian/s_config/`dirname $$f`; \
fi; \
done
- libtoolize -cfi
+ cd dist libtoolize -cfi
+ cd lang/sql/sqlite libtoolize -cfi
cd dist ./s_config
ifeq (,$(findstring nocheck,$(DEB_BUILD_OPTIONS)))
JAVACFLAGS=$(JAVACFLAGS) dh_auto_configure -Ddist -Bbuild-test --
$(CONFIGURE_SWITCHES) --enable-test
@@ -152,12 +162,17 @@
dh_auto_clean
Bug#750481: Documentation
' (a few one/two-line changes in test operators in debian/rules) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#750481: Fixed, thanks
Package: src:db5.3 Hi Ondřej, Thanks for the new upload, real quick. :) It helps greatly. I confirm it fixes the issue. (I just built from incoming.d.o, all good.) Best regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751796: gnutls26: dh-autoreconf (patch available)
Hi maintainers, Would you have any news, or comments on the patch attached in this bug? Any feedback is welcome. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751822: libprelude: test-suite fixes
Package: src:libprelude Hi Pierre, Would you have any news, or comments on the patches attached in this bug? Any feedback is welcome. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751917: ghostscript: fix FTBFS on ppc64el (patch available)
Package: src:ghostscript Hi maintainers, Would you have any news, or comments on the patch attached in this bug? Any feedback is welcome. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689622: libnih: fix FTBFS on ppc64el (patch available)
Package: src:libnih Hi Scott, Would you have any news, or comments on the patch attached in this bug? Any feedback is welcome. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752891: systemtap: build on ppc64el
Package: src:systemtap Version: 2.3-2 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Hi Ritesh, This trivial patch adds ppc64el [1] to the arch list in systemtap. May you please consider it for an upload? Thank you, [1] https://wiki.debian.org/ppc64el -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751796: gnutls26: dh-autoreconf (patch available)
Hi Andreas, Thanks for replying. My first thought is that I am a little bit reluctant to add a dependency on an old automake version. The automake maintainers might decide to decruft and drop old versions if possible and I would rather not have gnutls as a blocker. Okay, that is certainly understandable. I will take a look at using a newer automake, and the implied changes/fixes it might need. Would you be OK with carrying a patch for that matter? -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749547: procps: fix FTBFS on ppc64el (new patch available for dh-autoreconf)
Package: src:procps
Version: 1:3.3.9-5
Tags: patch
Hi Craig,
This patch adds dh-autoreconf support on procps, and build-dep on
libnuma-dev for ppc64el too.
It differs from the previously submitted patch (message 5) in 2 points:
- uses /dh --with autoreconf/ syntax (recommended, rather than manually
calling dh_autoreconf{,_clean})
- adds a build-dep on pkg-config (fixes an autoconf error on autoreconf)
With it, the package build finishes successfully, with shared libraries.
An e-mail with details/documentation will follow shortly.
It applies and builds cleanly on top of 1:3.3.9-5.
May you please consider it for an upload?
Thank you,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru procps-3.3.9/debian/changelog procps-3.3.9/debian/changelog
--- procps-3.3.9/debian/changelog 2014-05-27 08:00:28.0 -0300
+++ procps-3.3.9/debian/changelog 2014-06-27 15:37:46.0 -0300
@@ -1,3 +1,11 @@
+procps (1:3.3.9-5.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Run dh-autoreconf (build-dep on pkg-config fixes autoconf error). (Closes:
#749547)
+ * Add libnuma-dev as build-dep for ppc64el.
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Fri, 27 Jun 2014
15:28:06 -0300
+
procps (1:3.3.9-5) unstable; urgency=medium
* Bypass vmstat -p test Closes: #743758
diff -Nru procps-3.3.9/debian/control procps-3.3.9/debian/control
--- procps-3.3.9/debian/control 2014-05-27 08:00:28.0 -0300
+++ procps-3.3.9/debian/control 2014-06-27 15:37:46.0 -0300
@@ -5,7 +5,8 @@
Build-Depends: debhelper (= 9.20120115),
libncurses5-dev, libncursesw5-dev,
dejagnu,
-libnuma-dev [amd64 i386 ia64 mips mipsel powerpc]
+libnuma-dev [amd64 i386 ia64 mips mipsel powerpc ppc64el],
+dh-autoreconf, pkg-config
Standards-Version: 3.9.5
Vcs-Git: git://git.debian.org/collab-maint/procps.git
Vcs-Browser: http://git.debian.org/?p=collab-maint/procps.git;a=summary
diff -Nru procps-3.3.9/debian/rules procps-3.3.9/debian/rules
--- procps-3.3.9/debian/rules 2014-05-27 08:00:28.0 -0300
+++ procps-3.3.9/debian/rules 2014-06-27 15:37:46.0 -0300
@@ -17,7 +17,7 @@
endif
%:
- dh $@
+ dh $@ --with autoreconf
autogen-files := debian/libprocps3.install debian/libprocps3-dev.install \
debian/libprocps3-dev.links
Bug#749547: procps: details of submitted patch
Package: src:procps On 06/27/2014 04:03 PM, Mauricio Faria de Oliveira wrote: An e-mail with details/documentation will follow shortly. Before (without patch): (unstable-ppc64el-sbuild)$ grep 'shared libraries' build.log checking whether the gcc -std=gnu99 linker (/usr/bin/ld -m elf64ppc) supports shared libraries... no checking if libtool supports shared libraries... no checking whether to build shared libraries... no checking whether the g++ linker (/usr/bin/ld -m elf64ppc) supports shared libraries... yes checking whether the g++ linker (/usr/bin/ld -m elf64ppc) supports shared libraries... yes (unstable-ppc64el-sbuild)$ grep '^dh_install:' build.log dh_install: libprocps3 missing files (usr/lib/powerpc64le-linux-gnu/libprocps.so.*), aborting (unstable-ppc64el-sbuild)$ After (with patch): (unstable-ppc64el-sbuild)$ grep 'shared libraries' build.log checking whether the gcc -std=gnu99 linker (/usr/bin/ld) supports shared libraries... yes checking if libtool supports shared libraries... yes checking whether to build shared libraries... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes checking whether the g++ linker (/usr/bin/ld) supports shared libraries... yes (unstable-ppc64el-sbuild)$ [...] (unstable-ppc64el-sbuild)$ dpkg-deb -c libprocps3_3.3.9-5.1_ppc64el.deb | grep '\.so' -rw-r--r-- root/root 80104 2014-06-27 15:38 ./lib/powerpc64le-linux-gnu/libprocps.so.3.0.0 lrwxrwxrwx root/root 0 2014-06-27 15:38 ./lib/powerpc64le-linux-gnu/libprocps.so.3 - libprocps.so.3.0.0 (unstable-ppc64el-sbuild)$ dpkg-deb -c libprocps3-dev_3.3.9-5.1_ppc64el.deb | grep '\.so' lrwxrwxrwx root/root 0 2014-06-27 15:38 ./usr/lib/powerpc64le-linux-gnu/libprocps.so - /lib/powerpc64le-linux-gnu/libprocps.so.3 dh_autoreconf without pkg-config installed (early autoconf error): dh build --with autoreconf dh_testdir dh_autoreconf [...] libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' configure.ac:32: error: possibly undefined macro: AC_MSG_ERROR If this token and others are legitimate, please use m4_pattern_allow. See the Autoconf documentation. configure.ac:48: error: possibly undefined macro: AC_CHECK_HEADERS configure.ac:85: error: possibly undefined macro: AC_INCLUDES_DEFAULT configure.ac:132: error: possibly undefined macro: AC_CHECK_LIB autoreconf: /usr/bin/autoconf failed with exit status: 1 dh_autoreconf: autoreconf -f -i returned exit code 1 make: *** [build] Error 2 dpkg-buildpackage: error: debian/rules build gave error exit status 2 dh_autoreconf with pkg-config installed (successful). note: there's plenty of automake warnings about subdir objects, but they are harmless. I have inspected the output/result differences with git; all good. dh build --with autoreconf dh_testdir dh_autoreconf [...] libtoolize: `AC_PROG_RANLIB' is rendered obsolete by `LT_INIT' Makefile.am:99: warning: source file '$(top_srcdir)/lib/strutils.c' is in a subdirectory, Makefile.am:99: but option 'subdir-objects' is disabled automake: warning: possible forward-incompatibility. automake: At least a source file is in a subdirectory, but the 'subdir-objects' automake: automake option hasn't been enabled. For now, the corresponding output automake: object file(s) will be placed in the top-level directory. However, automake: this behaviour will change in future Automake versions: they will automake: unconditionally cause object files to be placed in the same subdirectory automake: of the corresponding sources. automake: You are advised to start using 'subdir-objects' option throughout your automake: project, to avoid future incompatibilities. Makefile.am:99: warning: source file '$(top_srcdir)/lib/fileutils.c' is in a subdirectory, Makefile.am:99: but option 'subdir-objects' is disabled [ ... many similar warnings ... ] debian/rules override_dh_auto_configure -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752891: systemtap: build on ppc64el
Hi Ritesh,
You seem to have forgotten to attach the patch.
Oops.. Indeed. :-)
Here it goes.
Thanks,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
Index: systemtap-2.3/debian/control
===
--- systemtap-2.3.orig/debian/control
+++ systemtap-2.3/debian/control
@@ -13,7 +13,7 @@
Vcs-Browser: http://git.debian.org/?p=collab-maint/systemtap.git
Package: systemtap
-Architecture: i386 amd64 ia64 s390 powerpc powerpcspe arm armel armeb armhf
+Architecture: i386 amd64 ia64 s390 powerpc powerpcspe ppc64el arm armel armeb armhf
Depends: systemtap-runtime (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
systemtap-common (= ${source:Version}), make
Suggests: systemtap-doc, vim-addon-manager
@@ -46,7 +46,7 @@
Replaces: systemtap ( 0.0.20081220-1)
Breaks: systemtap ( 0.0.20081220-1)
Suggests: systemtap
-Architecture: i386 amd64 ia64 s390 powerpc powerpcspe arm armel armeb armhf
+Architecture: i386 amd64 ia64 s390 powerpc powerpcspe ppc64el arm armel armeb armhf
Depends: ${shlibs:Depends}, ${misc:Depends}, adduser
Description: instrumentation system for Linux (runtime component)
This package contains staprun program that can be used to run
@@ -71,7 +71,7 @@
information about the running Linux system.
Package: systemtap-server
-Architecture: i386 amd64 ia64 s390 powerpc powerpcspe arm armel armeb armhf
+Architecture: i386 amd64 ia64 s390 powerpc powerpcspe ppc64el arm armel armeb armhf
Depends: libnss3-tools, avahi-utils, unzip, zip, systemtap (= ${binary:Version}),
systemtap-client (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends},
net-tools
@@ -86,7 +86,7 @@
information about the running Linux system.
Package: systemtap-client
-Architecture: i386 amd64 ia64 s390 powerpc powerpcspe arm armel armeb armhf
+Architecture: i386 amd64 ia64 s390 powerpc powerpcspe ppc64el arm armel armeb armhf
Depends: avahi-utils, unzip, zip, dnsutils, systemtap-runtime (= ${binary:Version}), ${shlibs:Depends}, ${misc:Depends}
Suggests: systemtap-server
Description: instrumentation system for Linux (client for compile server)
Bug#751424: Enable autoreconf for ppc64el
On 06/28/2014 07:24 AM, Bill Allombert wrote: Would the patch(es) be good to go, then? Yes, thanks for following up. Cool. Thanks for your attention, Bill. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752891: systemtap: build on ppc64el
Hi Ritesh, But does it build on that architecture. Last I checked systemtap was limited on the architectures it supported. Did you successfully build it on ppc64el ? Yes; systemtap 2.3-2 + that patch builds successfully on ppc64el: [...] dpkg-deb: building package `systemtap' in `../systemtap_2.3-2_ppc64el.deb'. dpkg-deb: building package `systemtap-common' in `../systemtap-common_2.3-2_all.deb'. dpkg-deb: building package `systemtap-runtime' in `../systemtap-runtime_2.3-2_ppc64el.deb'. dpkg-deb: building package `systemtap-doc' in `../systemtap-doc_2.3-2_all.deb'. dpkg-deb: building package `systemtap-server' in `../systemtap-server_2.3-2_ppc64el.deb'. dpkg-deb: building package `systemtap-client' in `../systemtap-client_2.3-2_ppc64el.deb'. dpkg-deb: building package `systemtap-sdt-dev' in `../systemtap-sdt-dev_2.3-2_all.deb'. dpkg-genchanges ../systemtap_2.3-2_ppc64el.changes [...] $ echo $? 0 Systemtap has worked on (big-endian) ppc64 for a while on other distros. The (little-endian) ppc64el pieces are being introduced on Debian. :) Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751424: closed by Bill Allombert ballo...@debian.org (Bug#751424: fixed in libjpeg8 8d1-1)
On 06/30/2014 09:36 AM, Debian Bug Tracking System wrote: We believe that the bug you reported is fixed in the latest version of libjpeg8, which is due to be installed in the Debian FTP archive. Confirmed. libjpeg8 8d1-1 (currently in incoming.d.o) builds fine and produces shared libraries on ppc64el. $ dpkg-deb -c libjpeg8_8d1-1_ppc64el.deb | fgrep .so -rw-r--r-- root/root248512 2014-06-30 12:57 ./usr/lib/powerpc64le-linux-gnu/libjpeg.so.8.4.0 lrwxrwxrwx root/root 0 2014-06-30 12:57 ./usr/lib/powerpc64le-linux-gnu/libjpeg.so.8 - libjpeg.so.8.4.0 Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752891: systemtap: build on ppc64el
On 06/30/2014 10:13 AM, Ritesh Raj Sarraf wrote: Systemtap has worked on (big-endian) ppc64 for a while on other distros. The (little-endian) ppc64el pieces are being introduced on Debian. :) Thanks for confirming it. These days Timo is more active on SystemTap, hence I'll wait for him to review and pick for his next upload. Okay, thanks Ritesh. I will wait for Timo's opinion. Regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749547: Re: Bug#749547: procps: fix FTBFS on ppc64el (new patch available for dh-autoreconf)
Hi Craig and John, Thanks to Mauricio and Breno for the patch! Yes, it makes it a lot easier to support ports when someone supplies patches about the problem. Thanks for the upload. It built successfully on ppc64el. Regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751796: gnutls26: dh-autoreconf (patch available)
Hi Andreas,
I will take a look at using a newer automake, and the implied
changes/fixes it might need.
Thank you.
Nicely, only a few minor changes were required.
Would you be OK with carrying a patch for that matter?
Yes, sure. Given that it probably will not be big and gnutls26 does
not get new upstream releases there should not be a maintainance cost.
Cool. I added a patch with more documentation in its description field.
With it applied, gnutls26 builds fine on ppc64el, with no difference
to the packages from powerpc (other than build-id, sure); details below.
Is the attached patch OK for a new upload?
Please note that I will try very hard to get rid of gnutls26 in
jessie.
Ok. I see gnutls28 already runs dh-autoreconf, so it would be OK on
the ppc64el side, AFAICT.
Thank you.
Details:
Comparison of gnutls26's binary packages (powerpc and ppc64el):
$ for arch in powerpc ppc64el; do
mkdir -p contents/$arch
cd $arch
for deb in *.deb; do
dpkg-deb -c $deb
| sed 's,\(powerpc\)\|\(powerpc64le\),GNU_ARCH,g'
| cut -d. -f2-
| sort
../contents/$arch/${deb%%_*}.contents;
done
cd ..;
done
$ diff -r contents/*
diff -r contents/powerpc/libgnutls26-dbg.contents
contents/ppc64el/libgnutls26-dbg.contents
15,20c15,20
/usr/lib/debug/.build-id/b5/
/usr/lib/debug/.build-id/b5/5a9ca34e104923db1e02451bc4279884af6bf1.debug
/usr/lib/debug/.build-id/e3/
/usr/lib/debug/.build-id/e3/2523acc3a59567161fd1048e2d6f1058bfd0c9.debug
/usr/lib/debug/.build-id/ef/
/usr/lib/debug/.build-id/ef/aa8275a54ac989b6b86bf1dc21688b45063446.debug
---
/usr/lib/debug/.build-id/6b/
/usr/lib/debug/.build-id/6b/e3020e7fa04aacce93d5b27639fadf4bb9c580.debug
/usr/lib/debug/.build-id/de/
/usr/lib/debug/.build-id/de/f9f14b8787bbe79f40703f1ae57b46a594e774.debug
/usr/lib/debug/.build-id/f6/
/usr/lib/debug/.build-id/f6/fd796c7c0ec15e54ed16d8bf5bc8d85a85621b.debug
$
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru gnutls26-2.12.23/debian/changelog gnutls26-2.12.23/debian/changelog
--- gnutls26-2.12.23/debian/changelog 2014-05-31 11:14:33.0 -0300
+++ gnutls26-2.12.23/debian/changelog 2014-06-30 15:10:04.0 -0300
@@ -1,3 +1,10 @@
+gnutls26 (2.12.23-16.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Run dh-autoreconf on build; add fixes for automake
(30_fix_automake_oldies.patch). (Closes: #751796)
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Mon, 30 Jun 2014
12:56:42 -0300
+
gnutls26 (2.12.23-16) unstable; urgency=high
* Drop libgnutls26-dbg Conflicts with libgnutls13-dbg, libgnutls28-dbg.
diff -Nru gnutls26-2.12.23/debian/control gnutls26-2.12.23/debian/control
--- gnutls26-2.12.23/debian/control 2014-05-25 03:32:12.0 -0300
+++ gnutls26-2.12.23/debian/control 2014-06-30 15:10:07.0 -0300
@@ -9,7 +9,8 @@
Build-Depends: debhelper (= 9), libgcrypt11-dev (= 1.4.0), zlib1g-dev,
cdbs (= 0.4.93), gtk-doc-tools, texinfo (= 4.8),
libtasn1-6-dev, autotools-dev, datefudge,
- libp11-kit-dev (= 0.11) [!or1k], pkg-config, chrpath
+ libp11-kit-dev (= 0.11) [!or1k], pkg-config, chrpath,
+ dh-autoreconf
Build-Conflicts: libgnutls-dev
Standards-Version: 3.9.5
Vcs-Git: git://anonscm.debian.org/pkg-gnutls/gnutls.git -b gnutls26-master
diff -Nru gnutls26-2.12.23/debian/patches/30_fix_automake_oldies.patch
gnutls26-2.12.23/debian/patches/30_fix_automake_oldies.patch
--- gnutls26-2.12.23/debian/patches/30_fix_automake_oldies.patch
1969-12-31 21:00:00.0 -0300
+++ gnutls26-2.12.23/debian/patches/30_fix_automake_oldies.patch
2014-06-30 15:10:15.0 -0300
@@ -0,0 +1,125 @@
+Description: Fix warnings from automake oldies
+ This patch fixes the following automake warnings (treated as errors) in order
+ to run dh_autoreconf successfully with current versions of automake (e.g.,
1.14.1):
+ - The 'AM_PROG_MKDIR_P' macro is deprecated, and its use is discouraged.
+ You should use the Autoconf-provided 'AC_PROG_MKDIR_P' macro instead,
+ and use '$(MKDIR_P)' instead of '$(mkdir_p)'in your Makefile.am files.
+ - warning: 'lib*.la': linking libtool libraries using a non-POSIX
+ archiver requires 'AM_PROG_AR' in 'configure.ac'
+ while processing Libtool library 'lib*.la'
+ - warning: source file '*' is in a subdirectory,
+ but option 'subdir-objects' is disabled
+Forwarded: not-needed
+Last-Update: 2014-06-30
+Author: Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com
+
+Index: gnutls26-2.12.23/aclocal.m4
+===
+--- gnutls26-2.12.23.orig/aclocal.m4 2013-02-04 06:46:27.0 -0200
gnutls26-2.12.23/aclocal.m42014-06-30 12:36
Bug#753362: libjpeg6b: build with dh-autoreconf
Package: src:libjpeg6b Version: 6b1-4 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Hi Bill, This patch runs dh-autoreconf when building libjpeg6b. It is required for generating shared libraries on ppc64el and probably other new ports as well. It includes a patch to add -Wno-obsolete in AM_INIT_AUTOMAKE, due to ansi2knr being deprecated in automake1.11. (for the reader: reasoning for automake1.11 documented in #751424) Before: $ dpkg-deb -c libjpeg62_6b1-4_ppc64el.deb | fgrep .so $ After: $ dpkg-deb -c libjpeg62_6b1-4.1_ppc64el.deb | fgrep .so -rw-r--r-- root/root167528 2014-06-30 18:21 ./usr/lib/powerpc64le-linux-gnu/libjpeg.so.62.0.0 lrwxrwxrwx root/root 0 2014-06-30 18:21 ./usr/lib/powerpc64le-linux-gnu/libjpeg.so.62 - libjpeg.so.62.0.0 Thanks! -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru libjpeg6b-6b1/debian/changelog libjpeg6b-6b1/debian/changelog --- libjpeg6b-6b1/debian/changelog 2013-12-05 20:43:54.0 -0200 +++ libjpeg6b-6b1/debian/changelog 2014-06-30 18:20:38.0 -0300 @@ -1,3 +1,10 @@ +libjpeg6b (6b1-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Run dh-autoreconf (requires automake1.11 -Wno-obsolete, see automake-Wno-obsolete.patch). + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Mon, 30 Jun 2014 18:18:08 -0300 + libjpeg6b (6b1-4) unstable; urgency=high * Apply upstream patch to fix CVE-2013-6629 and CVE-2013-6630. diff -Nru libjpeg6b-6b1/debian/control libjpeg6b-6b1/debian/control --- libjpeg6b-6b1/debian/control2012-06-02 11:18:18.0 -0300 +++ libjpeg6b-6b1/debian/control2014-06-30 18:05:51.0 -0300 @@ -2,7 +2,7 @@ Maintainer: Bill Allombert ballo...@debian.org Section: graphics Priority: optional -Build-Depends: debhelper (= 5), autotools-dev +Build-Depends: debhelper (= 5), autotools-dev, dh-autoreconf, automake1.11 Standards-Version: 3.9.3 Package: libjpeg62 diff -Nru libjpeg6b-6b1/debian/patches/automake-Wno-obsolete.patch libjpeg6b-6b1/debian/patches/automake-Wno-obsolete.patch --- libjpeg6b-6b1/debian/patches/automake-Wno-obsolete.patch1969-12-31 21:00:00.0 -0300 +++ libjpeg6b-6b1/debian/patches/automake-Wno-obsolete.patch2014-06-30 18:17:36.0 -0300 @@ -0,0 +1,19 @@ +Description: automake 1.11 needs -Wno-obsolete due to ansi2knr (for autoreconf) + or fails with message 'automatic de-ANSI-fication support is deprecated'. +Forwarded: not-needed +Last-Update: 2014-06-30 +Author: Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com + +Index: libjpeg6b-6b1/configure.ac +=== +--- libjpeg6b-6b1.orig/configure.ac2010-05-15 16:28:51.0 -0300 libjpeg6b-6b1/configure.ac 2014-06-30 18:07:36.0 -0300 +@@ -21,7 +21,7 @@ + + # Initialize Automake + # Don't require all the GNU mandated files +-AM_INIT_AUTOMAKE([-Wall -Werror ansi2knr no-dist foreign]) ++AM_INIT_AUTOMAKE([-Wall -Werror -Wno-obsolete ansi2knr no-dist foreign]) + + # Make --enable-silent-rules the default. + # To get verbose build output you may configure diff -Nru libjpeg6b-6b1/debian/patches/series libjpeg6b-6b1/debian/patches/series --- libjpeg6b-6b1/debian/patches/series 2013-12-03 19:54:02.0 -0200 +++ libjpeg6b-6b1/debian/patches/series 2014-06-30 18:06:35.0 -0300 @@ -1,3 +1,4 @@ extern_C-jpeglib.h use-autotools-dev fix-CVE-2013-6629_6630 +automake-Wno-obsolete.patch diff -Nru libjpeg6b-6b1/debian/rules libjpeg6b-6b1/debian/rules --- libjpeg6b-6b1/debian/rules 2013-12-05 08:24:59.0 -0200 +++ libjpeg6b-6b1/debian/rules 2014-06-30 18:05:51.0 -0300 @@ -15,10 +15,14 @@ endif #export DH_VERBOSE=1 +export AUTOMAKE = automake-1.11 +export ACLOCAL = aclocal-1.11 +export AUTOHEADER = true build: build-stamp build-stamp: dh_testdir + dh_autoreconf ./configure --prefix=/usr --mandir=/usr/share/man \ --libdir=/usr/lib/$(DEB_HOST_MULTIARCH) \ --enable-static --enable-shared --enable-maxmem=1024 \ @@ -36,6 +40,7 @@ -rm -f build-stamp stamp-h1 if [ -f Makefile ]; then $(MAKE) clean; fi -rm -f Makefile jconfig.h config.log config.status libtool + dh_autoreconf_clean dh_clean binary-indep:
Bug#751424: closed by Bill Allombert ballo...@debian.org (Bug#751424: fixed in libjpeg8 8d1-1)
On 06/30/2014 12:00 PM, Bill Allombert wrote: Could you check libjpeg6b ? It might need a similar patch. Sure. Indeed; I submitted a patch in #753362. Kind regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753362: libjpeg6b: build with dh-autoreconf
On 07/01/2014 10:09 AM, Bill Allombert wrote:
Is it possible to pass -Wno-obsolete as an argument to automake instead of
patching configure.ac ?
It seems not to be possible. Even with -Wno-obsolete (or its variant)
specified, automake fails with that error.
$ autoreconf -fvi -Wno-obsolete
[...]
autoreconf: running: automake-1.11 --add-missing --copy --force-missing
*--warnings=no-obsolete*
[...]
configure.ac:24: automatic de-ANSI-fication support is deprecated
autoreconf: automake-1.11 failed with exit status: 1
$
$ automake-1.11 *-Wno-obsolete*
[...]
configure.ac:24: automatic de-ANSI-fication support is deprecated
$
I believe the value is re-set when parsing AM_INIT_AUTOMAKE. I looked in
some of automake's perl modules, but couldn't find its right spot.
from Automake/Options.pm:
This packages manages Automake's options and strictness settings.
Options can be either local or global. Local options are set using an
CAUTOMAKE_OPTIONS variable in a FMakefile.am and apply only to
this FMakefile.am. Global options are set from the command line or
passed as an argument to CAM_INIT_AUTOMAKE, they apply to all
FMakefile.ams.
So maybe local options override global options.
Clearly, the original files were generated without patching.
Agreed. I would think it might have happened when ansi2knr was not
yet deprecated, or a local option was used in a Makefile.am, maybe
both.. maybe none. :)
If I got you right, the inconvenience itself seems to be carrying
a patch only for that matter, if an env var/cmdline arg could do.
So, for that, I wouldn't know another option.
On the side of causing no difference compared without -Wno-obsolete,
I can confirm the packages generated in ppc64el (with that patch)
and powerpc are identical in terms of files -- so the patch/option
doesn't affect the expected build output:
$ for dir in ppc64el/ powerpc/; do
cd $dir
mkdir contents
for deb in *.deb; do
dpkg-deb -c $deb
| cut -d. -f2-
| sort
| sed 's,\(powerpc64le\|powerpc\),GNU_ARCH,g'
contents/${deb%%_*};
done
cd .. ;
done
$ diff -r ppc64el/contents/ powerpc/contents/
$ echo $?
0
Would that be OK with the rationale above?
Thank you,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751390: Re: Bug#751390: src:pcre3: use dh-autoreconf to fix FTBFS on ppc64el
Hi Mark and Helmut, Helmut wrote: Please consider reworking the patch to address some of the above. Mark: 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. Erwan wrote: I've reworked the initial patch according to the previous comments: [...] I've added a change into soname.patch to apply changes into configure.ac instead of configure. Would you have any news, or comments on the new patch attached (msg#10), or consider it for a new upload, if you judge it good to go? AFAICT, it has addressed the considerations raised. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749060: klibc: ppc64el needs static binaries as well
Hi maks, On Fri, 23 May 2014 16:47:35 +0200 maximilian attems wrote: I have no problem to merge this for Debian as workaround for now, but this is not the solution. Effort in making shared binary working too is appreciated. It is probably a wrong syscall API. Would you please merge this as a workaround for now? It's been 3 months. The kindness and time of the volunteer effort in debugging this to find a solution is certainly appreciated, but it would be nice to fix the currently-broken initrd on ppc64el without non-Debian patches. I still plan to try to debug it myself for a while, but if it's ok to just go with the patch for now, it would greatly help us. I thought it would come in conveniently in case you'll make a new upstream release for klibc 2.0.4. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
Package: src:xcb-util
Version: 0.3.8-2
Tags: patch
Hi Cyril,
Thanks for looking at this.
at Aurelien's request, I've tried applying your patch and triggering a
build on amd64 in a sid chroot but it failed with:
The build with the patch worked for me, in a amd64 sid chroot.
It built successfully, producing identical package contents.
I am attaching a debdiff for your convenience.
Any chance something was missing on your environment? It doesn't hurt
to ask. :)
This is what I done:
$ sudo debootstrap --arch=amd64 --variant=buildd sid sid.amd64
http://ftp.br.debian.org/debian
(performed 2 package builds w/ dpkg-buildpackage: without and with the
patch)
$ for deb in *.deb; do dpkg-deb -c $deb | cut -d. -f2- | sort
$deb.contents; done
$ diff libxcb-util0_0.3.8-2{,ppc64el1}_amd64.deb.contents
$ echo $?
0
$ diff libxcb-util0-dev_0.3.8-2{,ppc64el1}_amd64.deb.contents
$ echo $?
0
Cheers,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru xcb-util-0.3.8/debian/changelog xcb-util-0.3.8/debian/changelog
--- xcb-util-0.3.8/debian/changelog 2012-02-09 22:42:01.0 -0200
+++ xcb-util-0.3.8/debian/changelog 2014-08-21 15:05:41.0 -0300
@@ -1,3 +1,9 @@
+xcb-util (0.3.8-2ppc64el1) UNRELEASED; urgency=medium
+
+ * Build with dh-autoreconf. Thanks to Breno Henrique Leitao. (Closes:
#748983)
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 21 Aug 2014
14:57:24 -0300
+
xcb-util (0.3.8-2) unstable; urgency=low
* Convert to multi-arch. Thanks to Tom Ellis tom.el...@canonical.com
diff -Nru xcb-util-0.3.8/debian/control xcb-util-0.3.8/debian/control
--- xcb-util-0.3.8/debian/control 2012-02-08 17:40:41.0 -0200
+++ xcb-util-0.3.8/debian/control 2014-08-21 15:05:41.0 -0300
@@ -15,7 +15,8 @@
autotools-dev,
autoconf,
automake,
- xutils-dev
+ xutils-dev,
+ dh-autoreconf
Standards-Version: 3.9.2
Homepage: http://xcb.freedesktop.org
Vcs-Git: git://git.debian.org/pkg-xorg/lib/xcb-util.git
diff -Nru xcb-util-0.3.8/debian/rules xcb-util-0.3.8/debian/rules
--- xcb-util-0.3.8/debian/rules 2012-02-08 17:40:41.0 -0200
+++ xcb-util-0.3.8/debian/rules 2014-08-21 15:05:41.0 -0300
@@ -4,6 +4,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
DEB_DH_MAKESHLIBS_ARGS=-V
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
On 08/21/2014 04:27 PM, Cyril Brulebois wrote: I'm not exactly happy with uploading a change that introduces a FTBFS in conditions that haven't been determined yet. :/ And I can't promise I'll be able to debug this right away since I'm otherwise busy with d-i. Sure. That's certainly understandable. I'm anyway attaching the list of packages installed on one of these chroots, in case it helps someone figure out what the problem is. Ok, thanks. I'll take a look at it. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
Hi Cyril, On 08/21/2014 04:49 PM, Mauricio Faria de Oliveira wrote: I'm anyway attaching the list of packages installed on one of these chroots, in case it helps someone figure out what the problem is. Ok, thanks. I'll take a look at it. I looked at it, reproduced the package list to what was possible, forced things a bit, but still could not reproduce that failure. Details of those points: 1) package list I reproduced the package list you sent to the extent it was possible -- some packages don't exist anymore (boost1.53, python3.3, libgnutls28). Some have been gone for a while now (libgnutls28 is June 5 IIRC), so the failure might be related to an old environment as well. I am attaching the package-list diff between my environment and yours. I can't find anything on it that seems to influence autoreconf programs. 2) differences in CDBS? (forced things a bit) I noticed the build log you pasted have no output for 2 CDBS targets: update-config and reverse-config (/usr/share/cdbs/1/rules/buildcore.mk), My 'debuild -b' build log diffs here: rm -f Doxyfile .gitmodules autogen.sh +for i in ./config.guess ./config.sub ; do \ + if test -e $i.cdbs-orig ; then \ + mv $i.cdbs-orig $i ; \ + fi ; \ +done if test -e debian/autoreconf.before; then \ [...] mkdir -p . +if test -e /usr/share/misc/config.guess ; then \ + for i in ./config.guess ; do \ + if ! test -e $i.cdbs-orig ; then \ + mv $i $i.cdbs-orig ; \ + cp --remove-destination /usr/share/misc/config.guess $i ; \ + fi ; \ + done ; \ +fi +if test -e /usr/share/misc/config.sub ; then \ + for i in ./config.sub ; do \ + if ! test -e $i.cdbs-orig ; then \ + mv $i $i.cdbs-orig ; \ + cp --remove-destination /usr/share/misc/config.sub $i ; \ + fi ; \ + done ; \ +fi dh_autoreconf By reading those build targets' source, the only way I can reproduce that text to be missing (trying to match your build) is by *removing* config.guess/sub. But even with that, autoreconf (and the build) finished successfully: $ rm -f config.guess config.sub $ debuild -b [...] rm -f Doxyfile .gitmodules autogen.sh if test -e debian/autoreconf.before; then \ dh_autoreconf_clean ; \ fi dh_clean rm -f debian/stamp-autotools-files debian/rules build test -x debian/rules mkdir -p . dh_autoreconf libtoolize: putting auxiliary files in `.'. libtoolize: copying file `./ltmain.sh' libtoolize: putting macros in AC_CONFIG_MACRO_DIR, `m4'. libtoolize: copying file `m4/libtool.m4' libtoolize: copying file `m4/ltoptions.m4' libtoolize: copying file `m4/ltsugar.m4' libtoolize: copying file `m4/ltversion.m4' libtoolize: copying file `m4/lt~obsolete.m4' libtoolize: Remember to add `LT_INIT' to configure.ac. configure.ac:10: installing './compile' configure.ac:10: installing './config.guess' configure.ac:10: installing './config.sub' test -f configure || sh ./autogen.sh [...] touch configure-stamp [...] That said (i.e., our builds have the 'same' package list, and the same build log until dh_autoreconf is run), now I ran out of things to try. I would ask you please consider testing the build on another environment -- more closely matching an official build one. .. or to provide me some more clues about your build environment. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center --- mauricfo.packages.list.pkg_ver 2014-08-22 09:27:38.155310189 -0300 +++ packages.list.pkg_ver 2014-08-22 08:55:40.851192806 -0300 @@ -125,0 +126 @@ +libboost-iostreams1.53.0 1.53.0-6+b2 @@ -135 +136 @@ -libcap-ng0:amd64 0.7.4-2 +libcap-ng0:amd64 0.7.4-1 @@ -146 +146,0 @@ -libcryptsetup4:amd64 2:1.6.6-1 @@ -153,0 +154 @@ +libdb5.1:amd64 5.1.29-7 @@ -158 +158,0 @@ -libdevmapper1.02.1:amd64 2:1.02.88-1 @@ -167,2 +167,2 @@ -libegl1-mesa:amd64 10.2.6-1 -libegl1-mesa-drivers:amd64 10.2.6-1 +libegl1-mesa:amd64 10.2.5-1 +libegl1-mesa-drivers:amd64 10.2.5-1 @@ -190 +190 @@ -libgbm1:amd64 10.2.6-1 +libgbm1:amd64 10.2.5-1 @@ -200,3 +200,3 @@ -libgl1-mesa-dri:amd64 10.2.6-1 -libgl1-mesa-glx:amd64 10.2.6-1 -libglapi-mesa:amd64 10.2.6-1 +libgl1-mesa-dri:amd64 10.2.5-1 +libgl1-mesa-glx:amd64 10.2.5-1 +libglapi-mesa:amd64 10.2.5-1 @@ -212,0 +213 @@ +libgnutls28:amd64 3.2.14-1 @@ -257,0 +259 @@ +liblognorm0 0.3.7-1 @@ -271,0 +274 @@ +libmozjs24d 24.5.0esr-1 @@ -291 +294 @@ -libopenvg1-mesa:amd64 10.2.6-1 +libopenvg1-mesa:amd64 10.2.5-1 @@ -315,0 +319,2 @@ +libpython3.3
Bug#749743: qt4-x11: use ppc64el in no_pch_architectures to fix FTBFS on ppc64el
Hi Lisandro,
(Adding William Grant; for the point about 'upstreaming the patch')
On 08/21/2014 10:29 AM, Lisandro Damián Nicanor Pérez Meyer wrote:
Copying ppc64el porters to see if we can speed up this and be able to push qt4
with ppc64el on saturday (hopefully).
Thanks! I believe I can try to help.
I'm attaching a patch that address your points, I believe.
It also handles the symbols files.
With it applied, qt4-x11 builds successfully on ppc64el.
I'll send the build log shortly to BTS [1].
May you please consider/review it for the Saturday upload?
Note: I moved one chunk from ppc64el.patch into the Debian-specific
patch that makes room for it on configure (seemed to be the right place
for that change). If you'd prefer to keep changes only in ppc64el.patch
please apply the attached ...-single-patch.interdiff.
On Sunday 15 June 2014 23:14:37 Lisandro Damián Nicanor Pérez Meyer wrote:
[...]
We have three issues here:
- In the patch [0] *86_64 has been changed to *64 in two lines (in the
middle). I'm really skeptic that this is a good change (if needed at all). And
I need to convince upstream too. Is this really necessary? In case it is, is
there a more precise approach? Like, for example, leaving *86_64 and adding a
new rule for whatever fits ppc64el.
You're right. It's not needed at all. The 'mkspec/qsw/linux-generic-g++'
default seems perfectly fine for ppc64el.
The only difference it has to the previously set 'linux-x86_64-g++'
(heh) is '-m64', which is the default and only-option on ppc64el.
$ diff -U0 mkspecs/qws/linux-{generic,x86_64}-g++
diff -U0 mkspecs/qws/linux-generic-g++/qmake.conf
mkspecs/qws/linux-x86_64-g++/qmake.conf
--- mkspecs/qws/linux-generic-g++/qmake.conf2014-07-23
17:30:59.0 -0300
+++ mkspecs/qws/linux-x86_64-g++/qmake.conf 2014-07-23
17:30:59.0 -0300
@@ -2 +2 @@
-# qmake configuration for building with g++
+# qmake configuration for building with linux-g++
@@ -9,0 +10,4 @@
+# modifications to g++.conf
+QMAKE_CFLAGS+= -m64
+QMAKE_CXXFLAGS += -m64
+
@@ -10,0 +15 @@
+
- The second issue is: who did this patch? It is not mentioned in the bug and
I need that info to properly add a patch for whatever reason.
It's originally from Ubuntu (details in attached patch's ppc64el.patch).
I included DEP-3 headers in ppc64el.patch for that matter and to explain
the patch's changes.
- The first change in the mentioned patch uses ppc64le and not ppc64el, is
that right?
Yes. On Debian it's 'el' and on GNU et al it's 'le'.
(definitely not the first time this question pops up :-)
dpkg's cputable [2]:
# Debian name GNU nameconfig.guess regex Bits
Endianness
ppc64el powerpc64le powerpc64le 64 little
uname:
$ uname -m
ppc64le
Now, about upstreaming the patch: Qt has a CLA in which you *don't* loose your
copyright but just give permission to Digia to use it in it's commercial
product (the code remains FLOSS!). I have two ways of pushing this upstream:
- Find the original coder and beg him to push it to upstream's gerrit instance
(preferred)
- Find the original coder and beg him to publicly state (on a mailing list,
for example) that this patch is licensed under a BSD license, which is less
restrictive.
We don't want to have deltas, so I *really* need your help here.
William,
AFAICT from Ubuntu's qt4-x11 changelog, you seem to be the patch author.
May you please consider the points above?
Only one chunk seems to be required. The 'PLATFORM=qws/' chunk can be
dropped and the UNAME chunk can be moved to another Debian patch.
@@ -3277,7 +3280,7 @@ if [ -z ${CFG_HOST_ARCH} ]; then
fi
CFG_HOST_ARCH=powerpc
;;
-*:*:ppc64)
+*:*:ppc64*)
if [ $OPT_VERBOSE = yes ]; then
echo 64-bit PowerPC (powerpc)
fi
Note: in this *particular* case I might solve this issue by the fact that this
change really doesn't seems copyrighteable because it's just using already
defined stuff, but if we have either of the above situations things get much
much easier.
Agreed.
[1] http://bugs.debian.org/749743
[2] https://anonscm.debian.org/cgit/dpkg/dpkg.git/tree/cputable
Cheers!
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -u qt4-x11-4.8.6+git49-gbc62005+dfsg/debian/changelog
qt4-x11-4.8.6+git49-gbc62005+dfsg/debian/changelog
--- qt4-x11-4.8.6+git49-gbc62005+dfsg/debian/changelog 2014-08-22
12:40:50.0 -0300
+++ qt4-x11-4.8.6+git49-gbc62005+dfsg/debian/changelog 2014-08-22
14:55:30.0 -0300
@@ -2,7 +2,6 @@
* Add support for ppc64el (Closes: #749743)
- ppc64el.patch: add configure support for ppc64el (thanks Ubuntu; minor
changes).
-- 07_trust_dpkg-arch_over_uname-m.diff
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
On 08/22/2014 10:10 AM, Cyril Brulebois wrote: Oh. Since the whole idea was committing stuff to git and uploading, I'm “of course” (at least to me but I should really have mentioned that) building from a “debcheckout xcb-util”. [...] Oops. I didn't get that before. I'm relatively unexperienced. Thanks for mentioning it. I can reproduce the failure now, and will check it soon. cheers, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
Hi Cyril, On 08/22/2014 04:04 PM, Mauricio Faria de Oliveira wrote: I can reproduce the failure now, and will check it soon. Got it. It's just a git submodule missing. I could built xcb-util from git successfully with: $ debcheckout xcb-util $ cd xcb-util $ git submodule update --init # gotcha $ patch -p1 ~/xcb-util-autoreconf-v2.debdiff $ debuild -b May you please verify it, and consider the patch for an upload? Thank you! P.S.: some details of the investigation: $ autoreconf -vi [...] Makefile.am:6: error: 'pkgconfig_DATA' is used but 'pkgconfigdir' is undefined [...] The definition of pkgconfigdir doesn't occur in the git repo, only in the source package: $ diff -qr xcb-util-0.38 xcb-util [...] Only in xcb-util-0.3.8/m4: xcb_util_common.m4 Only in xcb-util-0.3.8/m4: xcb_util_m4_with_include_path.m4 [...] Where those files went? This commit from 'git log m4/' gave a clue: commit 14747e0ef8dfb6668e2bb2e8a6b0c9ef2dace7b3 Author: Gaetan Nadon mems...@videotron.ca Date: Sun Mar 6 17:52:43 2011 -0500 config: use the default xorg .gitignore file This will save future maintenance when module structure/tools change. This patch depends on the util-common-m4 submodule patch in the m4 path Signed-off-by: Gaetan Nadon mems...@videotron.ca Signed-off-by: Arnaud Fontaine ar...@mini-dweeb.org I googled and read this [1, 2] and verified it: $ cat .gitmodules [submodule m4] path = m4 url = git://anongit.freedesktop.org/xcb/util-common-m4.git And done! :) [1] http://lists.x.org/archives/xorg-devel/2011-September/025364.html [2] http://wiki.x.org/wiki/Building_the_X_Window_System/#index6h2 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748983: xcb-util: run dh-autoreconf to update config.{sub, guess} and {libtool, aclocal}.m4
Adding the xcb-util package maintainers. On 08/22/2014 05:11 PM, Mauricio Faria de Oliveira wrote: On 08/22/2014 04:04 PM, Mauricio Faria de Oliveira wrote: I can reproduce the failure now, and will check it soon. Got it. It's just a git submodule missing. [...] $ git submodule update --init# gotcha [...] Where those files went? This commit from 'git log m4/' gave a clue: commit 14747e0ef8dfb6668e2bb2e8a6b0c9ef2dace7b3 [...] This patch depends on the util-common-m4 submodule patch in the m4 path It would be nice to have this documented or automatically done in xcb-util.git, like debian/README, debian/rules, for example. It's understandable that the maintainers are probably aware of that git submodule, but debcheckout didn't retrieve it automatically. It took some time until a non-maintainer could realize it. Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749743: qt4-x11: use ppc64el in no_pch_architectures to fix FTBFS on ppc64el
Hi William, Thanks for the quick reply :) On 08/22/2014 09:54 PM, William Grant wrote: I'm the author of http://launchpadlibrarian.net/159898800/qt4-x11_4%3A4.8.4%2Bdfsg-0ubuntu20_4%3A4.8.4%2Bdfsg-0ubuntu21.diff.gz. I don't know where the '*64*' bits in the attachments here came from. AFAICT, it came from a rebase of that patch at this version [1]. I'm waiting for the CLA stuff to be approved, but once that's sorted out I'll submit it upstream. I hardly thought it seemed copyrightable, but I guess it's easier this way. Cool. So, the upstream point is addressed. Thank you! [1] http://launchpadlibrarian.net/162331250/qt4-x11_4:4.8.4+dfsg-0ubuntu22_4:4.8.5+git192-g085f851+dfsg-2ubuntu1.diff.gz -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)
Hi Andi, On 08/23/2014 06:12 PM, Andreas Barth wrote: If useful I'd be willing to upload this fix as an NMU. As this is a blocker for cython it has some priority, so I would do that tomorrow unless there is a reason not to. Thanks, that would be great. :) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749743: qt4-x11: use ppc64el in no_pch_architectures to fix FTBFS on ppc64el
We believe that the bug you reported is fixed in the latest version of qt4-x11, which is due to be installed in the Debian FTP archive. The build finished successfully on our buildd over the weekend. Thanks a lot, Lisandro. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756403: [Python-modules-team] Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)
Hi Andi, On 08/25/2014 02:43 PM, Andreas Barth wrote: * Julian Taylor (jtaylor.deb...@googlemail.com) [140825 18:37]: I have committed the patch to svn, would need sponsoring. Where could I pull the package from? It's on SVN r30233 [1]. I can get with 'debcheckout python-numpy'. Interesting that, although the patch is there, it is not applied by default. I had to run 'quilt push -a' to get it applied. Thanks! [1] http://anonscm.debian.org/viewvc/python-modules?view=revisionrevision=30233 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756403: [Python-modules-team] Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)
On 08/25/2014 03:33 PM, Mauricio Faria de Oliveira wrote: On 08/25/2014 02:43 PM, Andreas Barth wrote: * Julian Taylor (jtaylor.deb...@googlemail.com) [140825 18:37]: I have committed the patch to svn, would need sponsoring. Where could I pull the package from? It's on SVN r30233 [1]. I can get with 'debcheckout python-numpy'. Interesting that, although the patch is there, it is not applied by default. I had to run 'quilt push -a' to get it applied. just verified, and it then built successfully on ppc64el. :) Thanks, Julian. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#756403: [Python-modules-team] Bug#756403: python-numpy: fix FTBFS on ppc64el (patch available)
Andi, On 08/25/2014 04:58 PM, Andreas Barth wrote: The above means until matplotlib could be otherwise bootstrapped, currently waiting as well for e.g. inkscape - libgnomevfs - g-conf - gtk+3.0. If that is done, I will bootstrap both packages together (and I need to do that anyways, independent whether the packages have a sourceful upload elsewhere or not). If you need another person to help in bootstrapping stuff, feel free to ask me. Not sure it's applicable as I'm not a 'D'eveloper :) but I'm familiar with that process to some extent, as we've bootstrapped it internally. And a /big/ thank-you for all the help you've been providing us. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754213: (no subject)
On 08/26/2014 05:05 AM, Ben Hutchings wrote: The first build failure (requiring __SANE_USERSPACE_TYPES__) appears to be fixed upstream in 3.16. I'll apply the other changes to enable building the linux-tools-* package. Thanks, Ben. That should be sufficient for us, as 3.16 should be landing in sid in some time, I believe (per this discussion + d-i beta on Aug. 13th): To avoid disruption to the installer, I think we should keep 3.14 in unstable until the next installer alpha/beta is out, and then move straight to 3.16. cheers! -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759389: linux: ppc64el: switch to vmlinuz (from vmlinux)
Package: src:linux Version: 3.16-1~exp1 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Hi maintainers, This patch switches the kernel type/image filename on ppc64el to vmlinuz (from vmlinux), and drops a workaround patch. $ dpkg-deb -c linux-image-3.16-trunk-powerpc64le_3.16-1~exp1ppc64el1_ppc64el.deb | fgrep vmlinu -rw-r--r-- root/root 4306765 2014-08-21 20:20 ./boot/vmlinuz-3.16-trunk-powerpc64le $ dpkg-deb -c kernel-image-3.16-trunk-powerpc64le-di_3.16-1~exp1ppc64el1_ppc64el.udeb | fgrep vmlinu -rw-r--r-- root/root 4306765 2014-08-21 20:22 ./boot/vmlinuz The zImage build is available starting with linux 3.16, with the introduction of the '64bit little endian wrapper' patch-set. (FYI, this is also happening in Ubuntu LP #1358920 [1]) The necessary changes for d-i will be submitted shortly (on #754093). May you please consider it for an upload? Thanks! [1] http://bugs.launchpad.net/bugs/1358920 -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru linux-3.16/debian/changelog linux-3.16/debian/changelog --- linux-3.16/debian/changelog 2014-08-09 17:58:13.0 -0300 +++ linux-3.16/debian/changelog 2014-08-21 16:41:39.0 -0300 @@ -1,3 +1,11 @@ +linux (3.16-1~exp1ppc64el1) UNRELEASED; urgency=medium + + * [ppc64el] debian/config/ppc64el/defines: switch to vmlinuz (from vmlinux). + * [ppc64el] debian/patches/debian/ppc64el-disable-zImage.patch: remove patch. +The 'powerpc/boot: 64bit little endian wrapper' patch-set is in linux 3.16. + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 21 Aug 2014 15:25:35 -0300 + linux (3.16-1~exp1) experimental; urgency=medium * New upstream release: http://kernelnewbies.org/Linux_3.16 diff -Nru linux-3.16/debian/config/ppc64el/defines linux-3.16/debian/config/ppc64el/defines --- linux-3.16/debian/config/ppc64el/defines2014-06-16 09:08:35.0 -0300 +++ linux-3.16/debian/config/ppc64el/defines2014-08-21 16:41:46.0 -0300 @@ -4,12 +4,12 @@ kernel-arch: powerpc [build] -image-file: vmlinux +image-file: arch/powerpc/boot/zImage [image] configs: suggests: mkvmlinuz -install-stem: vmlinux +install-stem: vmlinuz [powerpc64le_description] hardware: Little-endian 64-bit PowerPC diff -Nru linux-3.16/debian/patches/debian/ppc64el-disable-zImage.patch linux-3.16/debian/patches/debian/ppc64el-disable-zImage.patch --- linux-3.16/debian/patches/debian/ppc64el-disable-zImage.patch 2014-06-16 09:08:34.0 -0300 +++ linux-3.16/debian/patches/debian/ppc64el-disable-zImage.patch 1969-12-31 21:00:00.0 -0300 @@ -1,49 +0,0 @@ -From: Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com -Date: Wed, 4 Jun 2014 09:06:27 -0300 -Subject: ppc64el: kernel: patch: temporarily disable zImage - -Debian ppc64el will wait for the 'powerpc/boot: 64bit little endian wrapper' -(zImage) patches upstream rather than shipping 32-bit tools for zImage. The -patches are currently in Ben Herrenschmidt's linux-next tree [1]. - -The patches are not being carried over instead of this workaround because, -even without both, the build process does produces vmlinux, only failing for -zImage. So, it's ok to just work-around this for now, as we pick vmlinux. - -The workaround patch just avoids this build error: - - [...] - LD vmlinux - SYSMAP System.map - [...] - WRAParch/powerpc/boot/zImage.pseries - ld: unrecognised emulation mode: elf32ppc - Supported emulations: elf64lppc elf32lppc elf32lppclinux elf32lppcsim - make[6]: *** [arch/powerpc/boot/zImage.pseries] Error 1 - make[5]: *** [zImage] Error 2 - -[1] https://git.kernel.org/cgit/linux/kernel/git/next/linux-next.git/log/?qt=grepq=powerpc%2Fboot -(15 commits with message prefix 'powerpc/boot:' dated of 2014-04-28) - -Signed-off-by: Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com -Index: linux-3.14.2/arch/powerpc/boot/Makefile -=== linux-3.14.2.orig/arch/powerpc/boot/Makefile 2014-05-02 16:52:37.0 -0300 -+++ linux-3.14.2/arch/powerpc/boot/Makefile2014-05-07 09:39:11.0 -0300 -@@ -344,6 +344,15 @@ - $(obj)/%.dtb: $(src)/dts/%.dts FORCE - $(call if_changed_dep,dtc) - -+# Debian ppc64el will wait for the 'powerpc/boot: 64bit little endian wrapper' -+# (zImage) patches upstream rather than shipping 32-bit tools for zImage. -+# This makes the next conditional block to pick vmlinux.strip as image-y. -+ifdef CONFIG_PPC64 -+ifdef CONFIG_CPU_LITTLE_ENDIAN -+image-y := -+endif -+endif -+ - # If there isn't a platform selected then just strip the vmlinux. - ifeq (,$(image-y)) - image-y := vmlinux.strip diff -Nru linux-3.16/debian/patches/series linux-3.16/debian/patches/series --- linux-3.16/debian/patches/series2014-08-07 17:27:15.0 -0300 +++ linux-3.16/debian/patches/series2014-08-21 16:41:31.0
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
Package: src:debian-installer
Tags: patch
Hi,
Would you have any news/comments about the patch attached in this bug?
We would like to switch the kernel on ppc64el to vmlinuz starting with
3.16 (introduction of zImage support for 64el).
I am attaching an interdiff for that, on top of the previous patch,
and a full debdiff for your convenience.
I could successfully build d-i on ppc64el w/ those changes (plus adding
a build-dep on grub-ieee1275-bin, apparently missed, for grub-mknetdir),
on the debdiff.
$ tar tf debian-installer-images_20140802ppc64el1_ppc64el.tar.gz |
fgrep vmlinu
./installer-ppc64el/20140802ppc64el1/images/cdrom/vmlinuz
./installer-ppc64el/20140802ppc64el1/images/netboot/debian-installer/ppc64el/vmlinuz
The respective bug on the linux source package has been filled on
Debian #759389 (and Ubuntu LP #1358920).
Thanks!
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -u b/build/config/ppc64el.cfg b/build/config/ppc64el.cfg
--- b/build/config/ppc64el.cfg
+++ b/build/config/ppc64el.cfg
@@ -3,10 +3,10 @@
MKLIBS = mklibs-copy
KERNELMAJOR = 2.6
-BASEVERSION = 3.14-1
+BASEVERSION = 3.16-1
KERNELVERSION = $(BASEVERSION)-powerpc64le
KERNEL_FLAVOUR = di
-KERNELNAME = vmlinux
+KERNELNAME = vmlinuz
KERNELIMAGEVERSION = $(KERNELVERSION)
GRUB_CFG_CDROM = boot/ppc64el/grub-cdrom.cfg
@@ -26,11 +26,11 @@
$(TEMP_CD_TREE)/ppc/chrp \
$(TEMP_CD_TREE)/install
- cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinux
+ cp $(TEMP_KERNEL) $(TEMP_CD_TREE)/install/vmlinuz
cp $(TEMP_INITRD) $(TEMP_CD_TREE)/install/initrd.gz
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_TREE)/boot/grub/grub.cfg
@@ -47,7 +47,7 @@
$(TEMP_CD_INFO_DIR)/ppc/chrp
bootvars-subst \
- KERNEL /install/vmlinux \
+ KERNEL /install/vmlinuz \
INITRD /install/initrd.gz \
$(GRUB_CFG_CDROM) $(TEMP_CD_INFO_DIR)/boot/grub/grub.cfg
grub-mkimage -O powerpc-ieee1275 -p '(ieee1275/cdrom)/boot/grub' \
@@ -65,7 +65,7 @@
cp $(TEMP_KERNEL) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)
bootvars-subst \
- KERNEL $(NETBOOT_PATH)/vmlinux \
+ KERNEL $(NETBOOT_PATH)/vmlinuz \
INITRD $(NETBOOT_PATH)/initrd.gz \
$(GRUB_CFG_NETBOOT) $(TEMP_NETBOOT_DIR)/$(NETBOOT_PATH)/grub.cfg
if [ -n $(SPLASH_PNG) ]; then \
diff -Nru debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg
debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
--- debian-installer-20140802/build/boot/ppc64el/grub-cdrom.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/boot/ppc64el/grub-cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,11 @@
+set timeout=-1
+
+menuentry Install {
+ linux ${KERNEL} -- quiet
+ initrd ${INITRD}
+}
+
+menuentry Rescue mode {
+ linux ${KERNEL} rescue/enable=true -- quiet
+ initrd ${INITRD}
+}
diff -Nru debian-installer-20140802/build/config/ppc64el/cdrom.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
--- debian-installer-20140802/build/config/ppc64el/cdrom.cfg1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/cdrom.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,8 @@
+MEDIA_TYPE = CD-ROM
+
+TARGET = $(INITRD) $(KERNEL) $(DEBIAN_CD_INFO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-KERNEL = kernel for use with mkisofs to build a CD
+MANIFEST-INITRD = initrd for use with mkisofs to build a CD
+MANIFEST-DEBIAN_CD_INFO = mkisofs config files for CD
diff -Nru debian-installer-20140802/build/config/ppc64el/netboot.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
--- debian-installer-20140802/build/config/ppc64el/netboot.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el/netboot.cfg
2014-08-26 22:50:39.0 +
@@ -0,0 +1,9 @@
+MEDIA_TYPE = netboot image
+
+NETBOOT_DIR_TARGETS = $(TEMP_INITRD) $(TEMP_KERNEL)
+TARGET = $(NETBOOT_DIR) $(NETBOOT_TAR) $(MINIISO)
+EXTRANAME = $(MEDIUM)/
+
+MANIFEST-NETBOOT_DIR = boot directory for tftp server
+MANIFEST-NETBOOT_TAR = tarball of boot directory
+MANIFEST-MINIISO = tiny CD image that boots the netboot installer
diff -Nru debian-installer-20140802/build/config/ppc64el.cfg
debian-installer-20140802ppc64el1/build/config/ppc64el.cfg
--- debian-installer-20140802/build/config/ppc64el.cfg 1970-01-01
00:00:00.0 +
+++ debian-installer-20140802ppc64el1/build/config/ppc64el.cfg 2014-08-26
22:57:13.0 +
@@ -0,0 +1,76 @@
+MEDIUM_SUPPORTED = netboot cdrom
+
+MKLIBS = mklibs-copy
+
+KERNELMAJOR = 2.6
+BASEVERSION = 3.16-1
+KERNELVERSION = $(BASEVERSION)-powerpc64le
Bug#754093: debian-installer: ppc64el: ping / vmlinuz
On 08/26/2014 08:32 PM, Cyril Brulebois wrote: and thanks for both the bug report and the patch. Sure; my pleasure. Mauricio Faria de Oliveiramauri...@linux.vnet.ibm.com (2014-08-26): Would you have any news/comments about the patch attached in this bug? I'll rather let Aurelien comment on ppc64el patches. (Also, some bits could probably be shared between powerpc and ppc64el?) I'm not familiar w/ the approach/decision the original author(s) took about it, nor am familiar w/ the broader scope of d-i, so I'd like to defer the sharing question if possible. :) (I have only guesses about the lack of sharing because pcp64el is not actually/can't be a flavor of powerpc). I can try to find more info if needed. We would like to switch the kernel on ppc64el to vmlinuz starting with 3.16 (introduction of zImage support for 64el). 3.16 is soon going to be the default anyway, as soon as it's uploaded to unstable and built on all architectures. Yup. I just mentioned that to justify the base version bump to 3.16 on the patch, without that version being on sid yet. :) Thanks again, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759389: linux: ppc64el: switch to vmlinuz (from vmlinux)
On 08/27/2014 04:42 AM, Aurelien Jarno wrote: Thanks, I have just committed this patch, it will be in the next upload. Great! Thanks, Aurelien. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759482: coin3: build with autoreconf
Package: src:coin3 Version: 3.1.4~abc9f50-7 User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Hi, I know the autoreconf idea has been already tried and reverted [1], but I'd be willing to help in getting that working. I understand it might require changes to upstream code as well, so I'd ask the maintainers for some help/assistance, since they're more experienced on this package and its upstream development. Ok, let's move on. Error 0) simacros is missing (fix suggested) The first failure on autoreconf are lots of undefined m4 macros, because the m4_includes on the end of aclocal.m4 are wiped out by aclocal. Additionally, their path doesn't exist. They require coin3d/simacros to be pulled in. So, it can be fixed by downloading a copy of simacros (suggestion: git submodule), and adding something like this (obviously w/a different path) on configure.ac: AC_CONFIG_MACROS_DIR[(../simacros/cfg/m4)] Fixed. Let's go to the next error. Error 1) library naming Many automake errors like this: src/3ds/Makefile.am:53: error: 'format3ds.lst' is not a standard library name src/3ds/Makefile.am:53: did you mean 'libformat3ds.a'? src/3ds/Makefile.am: error: object '3ds-dummy.$(OBJEXT)' created both with libtool and without [...] This probably can be fixed with _LDFLAGS = -module, as suggested in automake's documentation [2]. I didn't have success w/ this, although I didn't try hard, as it would be nice to get a confirmation from maintainers that this was worth pursuing, or maybe there's a better way. Any help like instructions/suggestions/debugging/fixing this would be greatly appreciated. :) Thanks! [1] http://anonscm.debian.org/cgit/debian-science/packages/coin3.git/commit/?id=194c31add297f0693682f7521048c207e78bad8b [2] http://www.gnu.org/software/automake/manual/html_node/Libtool-Modules.html -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759500: python-apt: fix FTBFS (test_pep8) with pep8 = 1.5
Package: src:python-apt Version: 0.9.3.8 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Hi, This patch adds E129 to --ignore in 'tests/test_pep8.py', as pep8 1.5 introduced the following [1], and E125 was already there. 1.5 (2014-03-26) Changes: Report E129 instead of E125 for visually indented line with same indent as next logical line. (Issue #126) Thus fixing this test-suite error: /«PKGBUILDDIR»/tests/../tests/old/test_enhances.py:14:21: E129 visually indented line with same indent as next logical line [...] FAIL: test_pep8 (test_pep8.PackagePep8TestCase) It can be seen currently on build logs of ppc64el [2] and s390, as these archs have attempted to build python-apt after Debian's pep8 moved from 1.4.6 to 1.5.7 (23 Jul): pep8 (1.5.7-1) unstable; urgency=medium [ David Watson ] * New upstream release. (Closes: #754985) [...] -- David Watson dwat...@debian.org Wed, 23 Jul 2014 10:04:53 +0100 I'd think other archs would see this error too on a next build. With the patch, the test pass successfully on python 2.7 and 3.4: (sid-ppc64el-sbuild)$ python2.7 tests/test_all.py -v PackagePep8TestCase [tests] Running on 2.7.8 (default, Aug 26 2014, 22:15:24) [GCC 4.9.1] Using library_dir: '/root/python-apt-0.9.3.8/build/lib.linux-ppc64le-2.7'test_pep8 (test_pep8.PackagePep8TestCase) ... ok -- Ran 1 test in 1.511s OK (sid-ppc64el-sbuild)$ python3.4 tests/test_all.py -v PackagePep8TestCase [tests] Running on 3.4.1+ (default, Aug 21 2014, 11:23:41) [GCC 4.9.1] Using library_dir: '/root/python-apt-0.9.3.8/build/lib.linux-ppc64le-3.4'test_pep8 (test_pep8.PackagePep8TestCase) ... ok -- Ran 1 test in 1.526s OK Thanks. P.S.: I'm debugging the other test failure too (test_add_key_from_server_mitm), in case you'd like to wait and make a single upload including both fixes. That should be submitted soon. [1] https://pypi.python.org/pypi/pep8 [2] https://buildd.debian.org/status/fetch.php?pkg=python-aptarch=ppc64elver=0.9.3.8stamp=1408742227 -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru python-apt-0.9.3.8/debian/changelog python-apt-0.9.3.8ppc64el1/debian/changelog --- python-apt-0.9.3.8/debian/changelog 2014-06-30 08:32:24.0 -0300 +++ python-apt-0.9.3.8ppc64el1/debian/changelog 2014-08-27 16:15:14.0 -0300 @@ -1,3 +1,9 @@ +python-apt (0.9.3.8ppc64el1) UNRELEASED; urgency=medium + + * tests/test_pep8.py: --ignore E129 too (fix FTBFS with pep8 = 1.5) + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Wed, 27 Aug 2014 16:09:14 -0300 + python-apt (0.9.3.8) unstable; urgency=medium * pep8 fixes to fix autopkgtest failure with the most recent diff -Nru python-apt-0.9.3.8/tests/test_pep8.py python-apt-0.9.3.8ppc64el1/tests/test_pep8.py --- python-apt-0.9.3.8/tests/test_pep8.py 2014-06-30 08:32:24.0 -0300 +++ python-apt-0.9.3.8ppc64el1/tests/test_pep8.py 2014-08-27 16:16:50.0 -0300 @@ -16,8 +16,10 @@ # E126 continuation line over-indented for hanging indent # E127 continuation line over-indented for visual indent # E128 continuation line under-indented for visual indent + # E129 continuation line does not distinguish itself from + # next logical line # E265 block comment should start with '# ' - --ignore=E125,E126,E127,E128,E265, + --ignore=E125,E126,E127,E128,E129,E265, --exclude, build,tests/old, --repeat, py_dir]) if res != 0:
Bug#755342: python-apt: patch for 1 FTBFS on #759500
Package: src:python-apt Please note a patch for another current test-suite failure reported on #759500. Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755342: python-apt: fix FTBFS: tests failures
Source: src:python-apt Version: 0.9.3.8 Tags: patch Hi, The error reported was introduced with gnupg 1.4.18, specifically by upstream commit 'Screen keyserver responses' (5230304349490f31aa64ee2b69a8a2bc06bf7816). The attached patch fixes this bug (update for gnupg 1.4.18) and #759500 (update for pep8 1.5.7). May you please consider it for an upload? Thank you! Explanation Details: -- gnupg commit 'Screen keyserver responses' makes gpg to fail earlier than before when fingerprint verification fails, thus raising a different exception in '_add_key_from_keyserver' (apt/auth.py), so the test for which exception it raises needs to be updated. Test PASS (without commit 'Screen keyserver responses') $ python2.7 tests/test_all.py -q TestAuthKeys [tests] Running on 2.7.8 (default, Aug 26 2014, 22:15:24) [GCC 4.9.1] Using library_dir: '/[...]/build/lib.linux-ppc64le-2.7'-- Ran 6 tests in 1.844s OK Test FAIL (with commit 'Screen keyserver responses') (note the different string printed in AssertionError) $ python2.7 tests/test_all.py -q TestAuthKeys [tests] Running on 2.7.8 (default, Aug 26 2014, 22:15:24) [GCC 4.9.1] Using library_dir: '/[...]/build/lib.linux-ppc64le-2.7'== FAIL: test_add_key_from_server_mitm (test_auth.TestAuthKeys) Verify that the key fingerprint is verified after download -- Traceback (most recent call last): File /[...]/tests/test_auth.py, line 216, in test_add_key_from_server_mitm cm.exception) AssertionError: recv from 'hkp://localhost:19192' failed for '0101010178F7FE5C3E65D8AF8B48AD6246925553' -- Ran 6 tests in 1.779s FAILED (failures=1) With patch applied: $ python2.7 tests/test_all.py -q TestAuthKeys [tests] Running on 2.7.8 (default, Aug 26 2014, 22:15:24) [GCC 4.9.1] Using library_dir: '/[...]/build/lib.linux-ppc64le-2.7'-- Ran 6 tests in 1.793s OK $ python3.4 tests/test_all.py -q TestAuthKeys [tests] Running on 3.4.1+ (default, Aug 21 2014, 11:23:41) [GCC 4.9.1] Using library_dir: '/[...]/build/lib.linux-ppc64le-3.4'-- Ran 6 tests in 1.778s OK Relevant piece from 'apt/auth.py': # download the key to a temp keyring first res = subprocess.call(gpg_default_options + [ --secret-keyring, tmp_secret_keyring, --keyring, tmp_keyring, --keyserver, keyserver, --recv, keyid, ]) if res != 0: raise AptKeyError(recv from '%s' failed for '%s' % ( keyserver, keyid)) [...] [...] [...] if got_fingerprint != signing_key_fingerprint: raise AptKeyError( Fingerprints do not match, not importing: '%s' != '%s' % ( Excerpt from build log (attached): set -e; for python in python2.7 python3.4 ; do \ $python tests/test_all.py -q || [ linux = hurd ]; \ done; [tests] Running on 2.7.8 (default, Aug 26 2014, 22:15:24) [GCC 4.9.1] Using library_dir: '/[...]/build/lib.linux-ppc64le-2.7'WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file WARNING: Failed to read mirror file -- Ran 88 tests in 14.182s OK -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru python-apt-0.9.3.8/debian/changelog python-apt-0.9.3.8ppc64el2/debian/changelog --- python-apt-0.9.3.8/debian/changelog 2014-06-30 08:32:24.0 -0300 +++ python-apt-0.9.3.8ppc64el2/debian/changelog 2014-08-27 21:30:44.0 -0300 @@ -1,3 +1,14 @@ +python-apt (0.9.3.8ppc64el2) UNRELEASED; urgency=medium + + * tests/test_pep8.py: --ignore E129 too (fix FTBFS with pep8 = 1.5) +(Closes: #759500) + * tests/test_auth.py: update 'test_add_key_from_server_mitm' for gnupg 1.4.18, +which fail differently/earlier when 'fingerprints do not match' since commit +'Screen keyserver responses' (5230304349490f31aa64ee2b69a8a2bc06bf7816). +(Closes: #755342) + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Wed, 27 Aug 2014 16:09:14 -0300 + python-apt (0.9.3.8) unstable; urgency=medium * pep8 fixes to fix autopkgtest failure with the most recent diff -Nru python-apt-0.9.3.8/tests
Bug#759500: python-apt: fix FTBFS (test_pep8) with pep8 = 1.5
On 08/27/2014 04:26 PM, Mauricio Faria de Oliveira wrote: P.S.: I'm debugging the other test failure too (test_add_key_from_server_mitm), in case you'd like to wait and make a single upload including both fixes. That should be submitted soon. Submitted on #755342. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759550: ruby-ffi: (tracking bug) fix FTBFS on ppc64el (variadic arguments call)
Package: src:ruby-ffi Version: 1.9.3debian-2 Tags: patch pending User: debian-powe...@lists.debian.org Usertags: ppc64el Hi, Antonio. This bug is just to track the test-suite failure on ppc64el due to variadic arguments call, so we can put a bug number on wanna-build. I see you already committed a patch for that on debian source repository [1], to be released at your convenience. Building from that commit (debcheckout) builds successfully on ppc64el. (build log attached) Thanks, [1] http://anonscm.debian.org/cgit/pkg-ruby-extras/ruby-ffi.git/commit/?id=e963c03845fa40c3761940ad9cc4ef620487d2c0 -- Mauricio Faria de Oliveira IBM Linux Technology Center ruby-ffi_1.9.3debian-3_ppc64el.build.xz Description: application/xz
Bug#754213: (no subject)
Package: src:linux Hi Ben, On 08/26/2014 05:05 AM, Ben Hutchings wrote: The first build failure (requiring __SANE_USERSPACE_TYPES__) appears to be fixed upstream in 3.16. [...] I'm still hitting that w/ 3.16 (linux-tools from trunk, plus .orig from 3.16~rc7~exp1 or upstream 3.16.1 -- not usual, but I believe it was supposed to work). May you please point where/commit/excerpt you see this fixed? I could only find a related commit for MIPS [1], but nothing for powerpc. Thanks! Build log excerpt: gcc -include real-lsb-32/types.h -I/root/linux-tools-3.16/include -S -o real-lsb-32/devicetable-offsets.s /root/linux-tools-3.16/scripts/mod/devicetable-offsets.c In file included from ./real-lsb-32/types.h:1:0, from command-line:0: /root/linux-tools-3.16/include/linux/types.h:149:9: error: unknown type name 'u32' typedef u32 dma_addr_t; ^ /root/linux-tools-3.16/include/linux/types.h:165:9: error: unknown type name 'u32' typedef u32 phys_addr_t; ^ Makefile.real:16: recipe for target 'real-lsb-32/devicetable-offsets.s' failed [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=f4b3aa7cd9d32407670e67238c5ee752bb98f481 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#720689: cernlib: fix FTBFS with GNU make 3.82+ (patch available)
Package: src:cernlib
Version: 20061220+dfsg3-4
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Hi,
The attached patch (trivial) fixes the issue w/ debian.control.new.
It was suggested/provided by Michael Tautschnig on a previous message,
and I'am attaching a debdiff w/ it for your convenience.
I can confirm the comparison of debian/control{ , .new} is now passing.
Currently it would fail as in [1]
Thanks!
[1]
https://buildd.debian.org/status/fetch.php?pkg=cernlibarch=ppc64elver=20061220%2Bdfsg3-4stamp=1408774563
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru cernlib-20061220+dfsg3/debian/cernlib-debian.mk
cernlib-20061220+dfsg3/debian/cernlib-debian.mk
--- cernlib-20061220+dfsg3/debian/cernlib-debian.mk 2013-08-24
06:16:07.0 -0300
+++ cernlib-20061220+dfsg3/debian/cernlib-debian.mk 2014-08-28
10:16:21.0 -0300
@@ -177,7 +177,7 @@
-chmod a+x $(ADDONDIR)/scripts/[a-z]*
debian/control.new: $(wildcard debian/control.d/*.control)
- cat $^ $@
+ cat $(sort $^) $@
debian/control: debian/control.new
cp -f $ $@
diff -Nru cernlib-20061220+dfsg3/debian/changelog
cernlib-20061220+dfsg3/debian/changelog
--- cernlib-20061220+dfsg3/debian/changelog 2013-08-24 06:16:07.0
-0300
+++ cernlib-20061220+dfsg3/debian/changelog 2014-08-28 10:22:37.0
-0300
@@ -1,3 +1,12 @@
+cernlib (20061220+dfsg3-4ppc64el1) UNRELEASED; urgency=medium
+
+ * Fix 'debian/control.new' for GNU make 3.82+ (Closes: #720689)
+Thanks Michael Tautschnig. New versions of GNU make don't 'sort' the output
+of 'wildcard' anymore. This is reported in the following GNU make announce:
+https://lists.gnu.org/archive/html/info-gnu/2010-07/msg00023.html
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 28 Aug 2014
10:03:28 -0300
+
cernlib (20061220+dfsg3-4) unstable; urgency=low
* cernlib-base-dev: depends on dpkg-dev to fix Multiarch support.
Bug#720689: cernlib: build successful on ppc64el
Package: src:cernlib FYI, the build w/ the mentioned patch finishes succesfully on ppc64el. (log attached) -- Mauricio Faria de Oliveira IBM Linux Technology Center cernlib-20061220+dfsg3-ppc64el1_ppc64el.build.xz Description: application/xz
Bug#752415: mozjs: fix FTBFS on ppc64el: add to symbols file (patch available)
Package: src:mozjs
Version: 1.8.5-1.0.0+dfsg-4.2
Tags: patch
Hi,
I'm attaching an updated patch for current mozjs on sid, which
fails to build on ppc64el [1].
May you please consider it for an upload?
With it applied the package builds successfully:
[...]
dh_makeshlibs
-O--sourcedirectory=/root/mozjs-1.8.5-1.0.0\+dfsg/js/src
dh_shlibdeps -O--sourcedirectory=/root/mozjs-1.8.5-1.0.0\+dfsg/js/src
[...]
dpkg-buildpackage: full upload (original source is included)
Thanks!
[1]
https://buildd.debian.org/status/fetch.php?pkg=mozjsarch=ppc64elver=1.8.5-1.0.0%2Bdfsg-4.2stamp=1408831880
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru mozjs-1.8.5-1.0.0+dfsg/debian/changelog
mozjs-1.8.5-1.0.0+dfsg/debian/changelog
--- mozjs-1.8.5-1.0.0+dfsg/debian/changelog 2014-08-23 17:54:37.0
-0300
+++ mozjs-1.8.5-1.0.0+dfsg/debian/changelog 2014-08-28 12:27:19.0
-0300
@@ -1,3 +1,9 @@
+mozjs (1.8.5-1.0.0+dfsg-4.2ppc64el1) UNRELEASED; urgency=medium
+
+ * Add ppc64el to symbols file (thanks Fernando Seiti Furusato) (Closes:
#752415)
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 28 Aug 2014
12:25:57 -0300
+
mozjs (1.8.5-1.0.0+dfsg-4.2) unstable; urgency=medium
* Non-maintainer upload.
diff -Nru mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols
mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols
--- mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols 2014-04-02
15:00:53.0 -0300
+++ mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols 2014-08-28
12:25:44.0 -0300
@@ -1,4 +1,4 @@
-# SymbolsHelper-Confirmed: 1.8.5-1.0.0+dfsg amd64 armel armhf hurd-i386 i386
ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc s390 s390x sparc
+# SymbolsHelper-Confirmed: 1.8.5-1.0.0+dfsg amd64 armel armhf hurd-i386 i386
ia64 kfreebsd-amd64 kfreebsd-i386 mips mipsel powerpc ppc64el s390 s390x sparc
libmozjs185.so.1.0 libmozjs185-1.0 #MINVER#
(arch=armhf)InjectJaegerReturn@Base 1.8.5-1.0.0+dfsg
JS_AddArgumentFormatter@Base 1.8.5-1.0.0+dfsg
@@ -529,16 +529,16 @@
(arch=armhf)JaegerThrowpoline@Base 1.8.5-1.0.0+dfsg
(arch=armhf)JaegerTrampoline@Base 1.8.5-1.0.0+dfsg
(arch=armhf)JaegerTrampolineReturn@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64
!s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base
1.8.5-1.0.0+dfsg
- (arch=amd64 arm64 ia64 kfreebsd-amd64
s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base
1.8.5-1.0.0+dfsg
+ (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64 !ppc64el
!s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base
1.8.5-1.0.0+dfsg
+ (arch=amd64 arm64 ia64 kfreebsd-amd64 ppc64el
s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base
1.8.5-1.0.0+dfsg
_Z14js_DateGetDateP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z14js_DateGetYearP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z14js_DateIsValidP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z14js_IntervalNowv@Base 1.8.5-1.0.0+dfsg
_Z15js_DateGetHoursP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z15js_DateGetMonthP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64
!s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
- (arch=amd64 arm64 ia64 kfreebsd-amd64
s390x)_Z15js_FindPropertyP9JSContextlPP8JSObjectS3_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
+ (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64 !ppc64el
!s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
+ (arch=amd64 arm64 ia64 kfreebsd-amd64 ppc64el
s390x)_Z15js_FindPropertyP9JSContextlPP8JSObjectS3_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
_Z15js_IsTypedArrayP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z16js_CloseIteratorP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z16js_IsArrayBufferP8JSObject@Base 1.8.5-1.0.0+dfsg
@@ -546,8 +546,8 @@
_Z16js_ValueToSourceP9JSContextRKN2js5ValueE@Base 1.8.5-1.0.0+dfsg
_Z17js_DateGetMinutesP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z17js_DateGetSecondsP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
- (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64
!s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
- (arch=amd64 arm64 ia64 kfreebsd-amd64
s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectlPS2_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
+ (arch=!amd64 !arm64 !ia64 !kfreebsd-amd64 !ppc64el
!s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
+ (arch=amd64 arm64 ia64 kfreebsd-amd64 ppc64el
s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectlPS2_PP10JSProperty@Base
1.8.5-1.0.0+dfsg
_Z17js_ObjectIsRegExpP8JSObject@Base 1.8.5-1.0.0+dfsg
(subst)_Z18JS_StructuredCloneP9JSContext{uint64_t}P{uint64_t}PFP8JSObjectS0_P23JSStructuredCloneReaderjjPvEPK26JSStructuredCloneCallbacksS6_@Base
1.8.5-1.0.0+dfsg
Bug#752415: mozjs: add ppc64el to symbols files
title 752415 mozjs: add ppc64el symbols (fix FTBFS) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#752415: mozjs: add ppc64el to symbols files
retitle 752415 mozjs: add ppc64el symbols (fix FTBFS) thanks -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754213: (no subject)
Package: linux-tools Tags: patch Hi Ben, On 08/28/2014 03:00 PM, Ben Hutchings wrote: I thought this would do it: commit d944c4eebcf4c0d5e5d9728fec110cbf0047ad7f Ok, I just checked and it really didn't do it on this case. :-/ AFAICT, this bug really needs -D__SANE_USERSPACE_TYPES__. Details below. I am attaching a patch w/ the previous fix, for your convenience. May you please consider it for commit, if you agree it's a proper fix? Details: That commit [1] does '#define __SANE_USERSPACE_TYPES__' on a types.h that gets no '#include' by the files related to this bug. The definition was added in 'tools/include/linux/types.h', but the only 'types.h' used are: $ gcc $GCC_ARGS -E -dD | fgrep types.h | cut -d'' -f2 | sort -u ./real-lsb-32/types.h [...]/linux-tools-3.16~rc7/include/linux/types.h [...]/linux-tools-3.16~rc7/include/uapi/linux/types.h /usr/include/asm-generic/posix_types.h /usr/include/linux/posix_types.h /usr/include/powerpc64le-linux-gnu/asm/posix_types.h /usr/include/powerpc64le-linux-gnu/asm/types.h $ So, in order to get 'int-ll64.h' (not 'int-l64.h), and thus 'u32' to be defined, that extra define is needed: $ gcc $GCC_ARGS -E -dD \ | grep u32 | grep -v __u32 typedef u32 dma_addr_t; typedef u32 phys_addr_t; $ $ gcc $GCC_ARGS -E -dD \ -D__SANE_USERSPACE_TYPES__ \ | grep u32 | grep -v __u32 typedef unsigned int u32; typedef u32 dma_addr_t; typedef u32 phys_addr_t; $ I'll send more details/demonstration/debugging on another e-mail. Thanks! [1] https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/tools/include/linux/types.h?id=d944c4eebcf4c0d5e5d9728fec110cbf0047ad7f -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru linux-tools-3.16~rc7/debian/build/scripts/mod/Makefile.real linux-tools-3.16/debian/build/scripts/mod/Makefile.real --- linux-tools-3.16~rc7/debian/build/scripts/mod/Makefile.real 2013-06-03 10:19:37.0 -0300 +++ linux-tools-3.16/debian/build/scripts/mod/Makefile.real 2014-08-28 17:42:57.0 -0300 @@ -6,6 +6,17 @@ include $(top_srcdir)/debian/build/Makefile.inc +DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU) + +ifneq (,$(filter powerpc64 ppc64el,$(DEB_HOST_ARCH_CPU))) + # Fix include/linux/types.h:148:1: error: unknown type name 'u32'. + # (#747151 #754213) + # See linux commits: + # asm/types.h: Remove include/asm-generic/int-l64.h + # powerpc: Add __SANE_USERSPACE_TYPES__ to asm/types.h for LL64 + CFLAGS += -D__SANE_USERSPACE_TYPES__ +endif + modpost.real-$(TYPE): file2alias.real-$(TYPE).o modpost.real-$(TYPE).o sumversion.real-$(TYPE).o $(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^ diff -Nru linux-tools-3.16~rc7/debian/changelog linux-tools-3.16/debian/changelog --- linux-tools-3.16~rc7/debian/changelog 2014-07-29 17:11:10.0 -0300 +++ linux-tools-3.16/debian/changelog 2014-08-28 17:49:09.0 -0300 @@ -1,9 +1,11 @@ -linux-tools (3.16-1) UNRELEASED; urgency=medium +linux-tools (3.16-1ppc64el1) UNRELEASED; urgency=medium * New upstream release [ Mauricio Faria de Oliveira ] * [ppc64el] Build linux-tools binary package (Closes: #754213) + * [ppc64el, ppc64] Build with -D__SANE_USERSPACE_TYPES__ on scripts/mod +(partially fixes #747151, for ppc64/ppc64el but not for alpha) -- Ben Hutchings b...@decadent.org.uk Sat, 23 Aug 2014 17:50:42 -0700
Bug#754213: (no subject)
On 08/28/2014 06:13 PM, Mauricio Faria de Oliveira wrote: I'll send more details/demonstration/debugging on another e-mail. The failure: make[6]: Entering directory '/root/linux-tools/linux-tools-3.16~rc7/debian/build/scripts/mod' gcc -include real-lsb-32/types.h -I/root/linux-tools/linux-tools-3.16~rc7/include -S -o real-lsb-32/devicetable-offsets.s /root/linux-tools/linux-tools-3.16~rc7/scripts/mod/devicetable-offsets.c In file included from ./real-lsb-32/types.h:1:0, from command-line:0: /root/linux-tools/linux-tools-3.16~rc7/include/linux/types.h:149:9: error: unknown type name 'u32' typedef u32 dma_addr_t; ^ /root/linux-tools/linux-tools-3.16~rc7/include/linux/types.h:165:9: error: unknown type name 'u32' typedef u32 phys_addr_t; ^ Makefile.real:16: recipe for target 'real-lsb-32/devicetable-offsets.s' failed make[6]: *** [real-lsb-32/devicetable-offsets.s] Error 1 For debugging purposes, we'll use the preprocessor output (-E) with macro definitions (-dD); i.e., -gcc -include real-lsb-32/types.h -I/root/linux-tools/linux-tools-3.16~rc7/include -S -o real-lsb-32/devicetable-offsets.s /root/linux-tools/linux-tools-3.16~rc7/scripts/mod/devicetable-offsets.c +gcc -include real-lsb-32/types.h -I/root/linux-tools/linux-tools-3.16~rc7/include -E -dD /root/linux-tools/linux-tools-3.16~rc7/scripts/mod/devicetable-offsets.c Now let's go check/test with the definion of __SANE_USERSPACE_TYPES__. - step 0) Reproduce the error: (the environment used ahead) $ cd /root/linux-tools/linux-tools-3.16~rc7/debian/build/scripts/mod $ GCC_ARGS='-include real-lsb-32/types.h -I/root/linux-tools/linux-tools-3.16~rc7/include /root/linux-tools/linux-tools-3.16~rc7/scripts/mod/devicetable-offsets.c' $ gcc $GCC_ARGS -S -o /dev/null In file included from ./real-lsb-32/types.h:1:0, from command-line:0: /root/linux-tools/linux-tools-3.16~rc7/include/linux/types.h:149:9: error: unknown type name 'u32' typedef u32 dma_addr_t; ^ /root/linux-tools/linux-tools-3.16~rc7/include/linux/types.h:165:9: error: unknown type name 'u32' typedef u32 phys_addr_t; ^ $ echo $? 1 Done. - step 1) Verify fix by -D__SANE_USERSPACE_TYPES__ $ gcc -D__SANE_USERSPACE_TYPES__ $GCC_ARGS -S -o /dev/null $ echo $? 0 - step 2) Verify that __SANE_USERSPACE_TYPES__ is defined, as in that patch: $ grep SANE_USERSPACE_TYPES ../../../../tools/include/linux/types.h #define __SANE_USERSPACE_TYPES__/* For PPC64, to get LL64 types */ Ok, it's there. - step 3) But why that fails? Because but that file/definition is not included by the file failing: $ gcc $GCC_ARGS -E -dD | grep SANE_USERSPACE_TYPES $ So, 'int-l64.h' is taken... $ gcc $GCC_ARGS -E -dD | grep 'int-l.*64.h' # 1 /usr/include/asm-generic/int-l64.h 1 3 4 # 9 /usr/include/asm-generic/int-l64.h 3 4 # 12 /usr/include/asm-generic/int-l64.h 2 3 4 ... and no 'u32' is defined: $ gcc $GCC_ARGS -E -dD | grep u32 | grep -v __u32 typedef u32 dma_addr_t; typedef u32 phys_addr_t; - step 4) How does -D__SANE_USERSPACE_TYPES__ fix that? It makes 'int-ll64.h' to be taken... $ gcc -D__SANE_USERSPACE_TYPES__ $GCC_ARGS -E -dD | grep 'int-l.*64.h' # 1 /root/linux-tools/linux-tools-3.16~rc7/include/asm-generic/int-ll64.h 1 3 4 # 1 /root/linux-tools/linux-tools-3.16~rc7/include/uapi/asm-generic/int-ll64.h 1 3 4 # 9 /root/linux-tools/linux-tools-3.16~rc7/include/uapi/asm-generic/int-ll64.h 3 4 # 12 /root/linux-tools/linux-tools-3.16~rc7/include/uapi/asm-generic/int-ll64.h 2 3 4 # 11 /root/linux-tools/linux-tools-3.16~rc7/include/asm-generic/int-ll64.h 2 3 4 ... and thus 'u32' is defined: $ gcc -D__SANE_USERSPACE_TYPES__ $GCC_ARGS -E -dD | grep u32 | grep -v __u32 typedef unsigned int u32; typedef u32 dma_addr_t; typedef u32 phys_addr_t; And gcc is happy. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754093: debian-installer: ppc64el: do NOT switch to vmlinu*z*
Hi, Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com: We would like to switch the kernel on ppc64el to vmlinuz starting with 3.16 (introduction of zImage support for 64el). Please do NOT apply the vmlinu*z* patch. Just ignore it. Some of the ppc64el target platforms can only boot vmlinu*x* (no support for compressed kernels). Really sorry for taking your time. (the build-dep on grub-ieee1275-bin is still needed, as explained) -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#759389: linux: ppc64el: do NOT switch to vmlinu*z*
Hi Aurelien, On 08/27/2014 04:42 AM, Aurelien Jarno wrote: Thanks, I have just committed this patch, it will be in the next upload. I have to ask you to please revert the vmlinu*z* patch. Some of the ppc64el target platforms can only boot vmlinu*x* (no support for compressed kernels). Really sorry for taking your time. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745075: marked as done (aspell: Please use autoreconf)
On 08/07/2014 06:36 PM, Debian Bug Tracking System wrote: Source: aspell Source-Version: 0.60.7~20110707-1.1 We believe that the bug you reported is fixed in the latest version of aspell, which is due to be installed in the Debian FTP archive. Thank you, Manuel. The new package built fine on ppc64el. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751917: ghostscript: add ppc64el to symbols file (patch available)
found 751917 ghostscript/9.05~dfsg-9 severity 751917 important thanks Hi Michael and maintainers, May you please consider this trivial patch (attached) for an upload? It would significantly help the ppc64el port to have ghostscript working, as it's an important build-dep for tens of packages. I have updated its changelog to apply on the version that Michael recently released on sid. Thank you for your attention, -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru ghostscript-9.05~dfsg/debian/changelog ghostscript-9.05~dfsg/debian/changelog --- ghostscript-9.05~dfsg/debian/changelog 2014-08-08 12:00:13.0 -0300 +++ ghostscript-9.05~dfsg/debian/changelog 2014-08-12 12:22:05.0 -0300 @@ -1,3 +1,9 @@ +ghostscript (9.05~dfsg-9ppc64el1) UNRELEASED; urgency=medium + + * Add ppc64el to symbols file. (Closes: #751917) + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Tue, 12 Aug 2014 12:22:00 -0300 + ghostscript (9.05~dfsg-9) unstable; urgency=medium * Update my email address. diff -Nru ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in --- ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in2014-04-06 23:32:39.0 -0300 +++ ghostscript-9.05~dfsg/debian/libgs__VER__.symbols.in2014-08-12 12:21:43.0 -0300 @@ -1,5 +1,5 @@ libgs.so.__VER__ libgs__VER__ #MINVER# #include symbols.common (arch=linux-any)#include symbols.common_linux -(arch=!any-alpha !any-amd64 !any-arm64 !any-ia64 !any-ppc64 !any-s390x !any-sparc64)#include symbols.common_32bit -(arch=any-alpha any-amd64 any-arm64 any-armel any-i386 any-ia64 any-mipsel any-sh3 any-sh4)#include symbols.common_le +(arch=!any-alpha !any-amd64 !any-arm64 !any-ia64 !any-ppc64 !any-ppc64el !any-s390x !any-sparc64)#include symbols.common_32bit +(arch=any-alpha any-amd64 any-arm64 any-armel any-i386 any-ia64 any-mipsel any-ppc64el any-sh3 any-sh4)#include symbols.common_le
Bug#751822: Fix FTBFS on ppc64el (test-suite + python binding)
Hi Andreas, On 08/14/2014 02:24 PM, Andreas Metzler wrote: this patch looks strange. Can you show how to reproduce this issue? This kind of bug cannot be ppc64el specific and I do not see it at ix86. Yes, indeed strange. I've realized it some weeks later, but missed trying a bit more. I'll try to reproduce/understand it again and ping back. Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751822: Fix FTBFS on ppc64el (test-suite + python binding)
Hi Andreas,
On 08/14/2014 02:24 PM, Andreas Metzler wrote:
this patch looks strange. Can you show how to reproduce this issue?
I wrote:
I'll try to reproduce/understand it again and ping back.
Got it; it was due to building the package as a privileged user.
(thus passing setup.py's is_system_wide_install() test, due to
write-access on /usr/lib/python*/dist-packages)
The package builds fine on a normal/unprivileged sbuild build,
just with the test-suite patch.
I see you already made a uploaded w/ that patch for delayed/10.
Thanks, that will make it.
In case you'd prefer to put in a patch w/ DEP-3 headers and stuff,
I'm attaching one for your convenience.
Thanks again, and best regards.
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru libprelude-1.0.0/debian/changelog libprelude-1.0.0/debian/changelog
--- libprelude-1.0.0/debian/changelog 2014-08-05 17:29:12.0 +
+++ libprelude-1.0.0/debian/changelog 2014-08-15 16:29:33.0 +
@@ -1,3 +1,9 @@
+libprelude (1.0.0-11.3ppc64el1) UNRELEASED; urgency=medium
+
+ * Fix libmissing/ test-suite on ppc64el (ppc64el-fix-gnulib-tests.patch)
(Closes: #751822)
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Thu, 14 Aug 2014
18:06:04 -0300
+
libprelude (1.0.0-11.3) unstable; urgency=low
* Non-maintainer upload.
diff -Nru libprelude-1.0.0/debian/patches/ppc64el-fix-gnulib-tests.patch
libprelude-1.0.0/debian/patches/ppc64el-fix-gnulib-tests.patch
--- libprelude-1.0.0/debian/patches/ppc64el-fix-gnulib-tests.patch
1970-01-01 00:00:00.0 +
+++ libprelude-1.0.0/debian/patches/ppc64el-fix-gnulib-tests.patch
2014-08-15 16:28:09.0 +
@@ -0,0 +1,55 @@
+Subject: [PATCH] isfinite, isinf, isnan tests: fix for little-endian PowerPC
+Origin: backport,
http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commit;h=e962c07c0c8bb18f9a5969cbf1ddb01d0fe4f55c
+Forwarded: https://www.prelude-ids.org/issues/556
+Author: Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com
+Last-Update: 2014-08-14
+
+This patch is a trivial backport (subset) of the upstream patch; it just
removes
+the files that don't exist in libprelude (not required).
+
+ curl
'http://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=patch;h=e962c07c0c8bb18f9a5969cbf1ddb01d0fe4f55c'
\
+ | filterdiff \
+ --strip=1 \
+ --addoldprefix='a/libmissing/' \
+ --addnewprefix='b/libmissing/' \
+ -i '*/tests/test-isnanl.h' \
+ -i '*/tests/test-signbit.c' \
+ ppc64el-fix-gnulib-tests.patch
+
+--- a/libmissing/tests/test-isnanl.h
b/libmissing/tests/test-isnanl.h
+@@ -51,6 +51,15 @@ main ()
+ /* A bit pattern that is different from a Quiet NaN. With a bit of luck,
+ it's a Signalling NaN. */
+ {
++#if defined __powerpc__ LDBL_MANT_DIG == 106
++/* This is PowerPC double double, a pair of two doubles. Inf and Nan
are
++ represented as the corresponding 64-bit IEEE values in the first
double;
++ the second is ignored. Manipulate only the first double. */
++#undef NWORDS
++#define NWORDS \
++ ((sizeof (double) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
++#endif
++
+ memory_long_double m;
+ m.value = NaNl ();
+ # if LDBL_EXPBIT0_BIT 0
+--- a/libmissing/tests/test-signbit.c
b/libmissing/tests/test-signbit.c
+@@ -151,6 +151,16 @@ test_signbitl ()
+ #define NWORDS \
+ ((sizeof (long double) + sizeof (unsigned int) - 1) / sizeof (unsigned
int))
+ typedef union { long double value; unsigned int word[NWORDS]; }
memory_long_double;
++
++#if defined __powerpc__ LDBL_MANT_DIG == 106
++/* This is PowerPC double double, a pair of two doubles. Inf and Nan
are
++ represented as the corresponding 64-bit IEEE values in the first
double;
++ the second is ignored. Manipulate only the first double. */
++#undef NWORDS
++#define NWORDS \
++ ((sizeof (double) + sizeof (unsigned int) - 1) / sizeof (unsigned int))
++#endif
++
+ memory_long_double m;
+ m.value = zerol / zerol;
+ # if LDBL_EXPBIT0_BIT 0
diff -Nru libprelude-1.0.0/debian/patches/series
libprelude-1.0.0/debian/patches/series
--- libprelude-1.0.0/debian/patches/series 2014-05-25 13:58:53.0
+
+++ libprelude-1.0.0/debian/patches/series 2014-08-15 16:28:09.0
+
@@ -5,3 +5,4 @@
request_REUSEADDR_before_bind.patch
test-poll_add_sleep_after_write.patch
keep-atfork-symbol.patch
+ppc64el-fix-gnulib-tests.patch
Bug#751917: ghostscript: add ppc64el to symbols file (patch available)
Hi Andreas and Jonas, On 08/17/2014 08:10 AM, Jonas Smedegaard wrote: Quoting Andreas Barth (2014-08-17 11:32:51) * Mauricio Faria de Oliveira (mauri...@linux.vnet.ibm.com) [140817 09:31]: May you please consider this trivial patch (attached) for an upload? I'm willing to upload the fix, is it ok if I NMU this package? Thanks, that'd be nice! Thank you very much for the quick upload. The package builds fine now! Best regards, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749060: klibc: ppc64el needs static binaries as well
Package: src:klibc Version: 2.0.3-1 Severity: normal Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el Hi, The ppc64el port needs klibc's static binaries, like ppc64. This patch enables the ARCH=ppc64 make env var in debian/rules, in order for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I initially thought that wouldn't be needed due to the ARCH=ppc64 definition on some Kbuild files, but it seems that is not used in some make targets for the binaries (probably why, even though, there was an ARCH=ppc64 definition already in place..). The result was shared binaries being picked, and some of them segfault. With this patch I can get a functional initramfs and non-segfaulting binaries in '/usr/lib/klibc/bin/*' (exception: 'kinit.shared', the only'.shared' file there). Unfortunately this fix didn't make the first ppc64el bug/patch for klibc (#744884); I only happened to notice this more recently. Apologies for the additional effort. Thanks, -- Mauricio Faria de Oliveira IBM Linux Technology Center Index: klibc-2.0.3/debian/rules === --- klibc-2.0.3.orig/debian/rules +++ klibc-2.0.3/debian/rules @@ -33,7 +33,7 @@ ifeq ($(DEB_HOST_ARCH),sh4) DEB_MAKE_ENVVARS := ARCH=sh endif -ifeq ($(DEB_HOST_ARCH),ppc64) +ifneq (,$(findstring $(DEB_HOST_ARCH),ppc64 ppc64el)) DEB_MAKE_ENVVARS := ARCH=ppc64 endif
Bug#749060: klibc: ppc64el needs static binaries as well
Hi maks, Adding Anton in CC (who submitted klibc ppc64le support upstream [1]), in case he can help. The ppc64el port needs klibc's static binaries, like ppc64. This segfaulting is a bug in klibc that needs investigation. This patch enables the ARCH=ppc64 make env var in debian/rules, in order for 'debian/patches/ppc64-static.patch' to take effect on ppp64el too. I have no problem to merge this for Debian as workaround for now, but this is not the solution. [...] I agree. Thanks for accepting to carry the workaround for ppc64el too. [...] Effort in making shared binary working too is appreciated. It is probably a wrong syscall API. Unfortunately I don't find myself in klibc expertise area. I can try, but maybe it's not the effective way forward (not sure I'd be able to devote the effort/time that I personally would like to). Hopefully others can contribute in that more significantly. :) Thank you. [1] http://www.zytor.com/pipermail/klibc/2013-December/003518.html -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#749060: klibc: ppc64el needs static binaries as well
On 05/23/2014 01:08 PM, Thorsten Glaser wrote: Give me a machine, and if I find any time (not very likely but still), I'll have a look at it. I fixed most arches, except Itanic (but that one's asm is just *too* strange) anyway. ssh-rsa B3NzaC1yc2EBIwAAASEAmE/kae2OppreGbHl/45N56/d1IhXYQsc95ydk8UQuoOKd6e/+MRzwwcKz37v/VZX1co9knQECn8Pk+URARq7KChTvi2blM0T7Aqj140NVf6XTKxwx6uJpmgeOGLcGOxmgFjYkfcdMPPuejwJBpt+8fdFeKsDcKfD2oibXN7v11zngjSortJhhObsNpkfrJRKQRESudMv9+NSdty020iFw7r+P3vXZQcGlDt14iLcJplYwHW3KqcAs2Hfc9mA/p8BraMg9HwGprSiuqI25lmZFvaX3IcCtmH36blxTYgEDmfUcDZonlHP7dpxyzg4pHtuYyXzxPMl0yDHqJ7jWVzUecXYzji4aVIxaDVWRlkfrohRYD6Gzo+lAEo3a6TVstgr t...@odem.66h.42h.de Sure; thank you very much. There's a development guest available [1]. I'll put you in touch with the guy who adds SSH keys in, on a separate e-mail. [1] https://wiki.debian.org/ppc64el#Development_machines -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751390: src:pcre3: use dh-autoreconf to fix FTBFS on ppc64el
On 07/01/2014 12:51 PM, Helmut Grohne wrote: Thanks for the ping (and CCing me). You're welcome. I believe that all major concerns raised by me are addressed in the updated patch. The following documentary concerns apply: * There is still no changelog entry. * The patches added or updated have not been updated with Last-Modified headers according to DEP-3. Oh, indeed. I missed those. For timezone differences, I suspect Erwan would be offline by now. I am attaching a new patch addressing your 2 points above, with proper credit to Erwan and Ubuntu. Mark Baker may have a different view and is the one in charge. Okay. I shall retry the patch in rebootstrap, but would prefer it being applied to pcre3 in sid directly. Yes, and it would help us with /d/ebootstrap too. :) Thank you again for your review and comments, -- Mauricio Faria de Oliveira IBM Linux Technology Center diff -Nru pcre3-8.31/debian/changelog pcre3-8.31/debian/changelog --- pcre3-8.31/debian/changelog 2014-04-23 17:00:42.0 -0300 +++ pcre3-8.31/debian/changelog 2014-07-01 13:11:19.0 -0300 @@ -1,3 +1,12 @@ +pcre3 (1:8.31-5.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Fix FTBFS on ppc64el (patches by Ubuntu, collection by Erwan Prioul); Closes: 751390 +- Build with dh-autoreconf (requires update to soname.patch) +- Disable JIT on ppc64el (no_jit_ppc64el.patch) + + -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Tue, 01 Jul 2014 13:07:49 -0300 + pcre3 (1:8.31-5) unstable; urgency=medium * Previous attempt at detecting JIT support didn't work when cross diff -Nru pcre3-8.31/debian/control pcre3-8.31/debian/control --- pcre3-8.31/debian/control 2013-01-03 18:27:02.0 -0200 +++ pcre3-8.31/debian/control 2014-07-01 13:11:14.0 -0300 @@ -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 diff -Nru pcre3-8.31/debian/patches/no_jit_ppc64el.patch pcre3-8.31/debian/patches/no_jit_ppc64el.patch --- pcre3-8.31/debian/patches/no_jit_ppc64el.patch 1969-12-31 21:00:00.0 -0300 +++ pcre3-8.31/debian/patches/no_jit_ppc64el.patch 2014-07-01 13:11:14.0 -0300 @@ -0,0 +1,19 @@ +Description: Disable JIT on ppc64el, needs explicit porting to ELFv2. +Author: Adam Conrad adcon...@ubuntu.com +Last-Update: 2014-07-01 + +--- 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__) diff -Nru pcre3-8.31/debian/patches/series pcre3-8.31/debian/patches/series --- pcre3-8.31/debian/patches/series2012-09-13 15:51:33.0 -0300 +++ pcre3-8.31/debian/patches/series2014-07-01 13:11:14.0 -0300 @@ -4,3 +4,4 @@ pcregrep.1-patch soname.patch bug1287 +no_jit_ppc64el.patch diff -Nru pcre3-8.31/debian/patches/soname.patch pcre3-8.31/debian/patches/soname.patch --- pcre3-8.31/debian/patches/soname.patch 2012-09-13 15:48:44.0 -0300 +++ pcre3-8.31/debian/patches/soname.patch 2014-07-01 13:11:14.0 -0300 @@ -1,23 +1,21 @@ From: Mark Baker m...@mnb.org.uk Description: Change soname to what debian use -Index: pcre3-8.31/configure +Last-Update: 2014-07-01 + +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
Bug#753362: libjpeg6b: build with dh-autoreconf
On 07/01/2014 11:38 AM, Bill Allombert wrote: On Tue, Jul 01, 2014 at 10:58:17AM -0300, Mauricio Faria de Oliveira wrote: Clearly, the original files were generated without patching. Agreed. I would think it might have happened when ansi2knr was not yet deprecated, or a local option was used in a Makefile.am, maybe both.. maybe none. :) According to the embedded comments, the files were generated by 1.11.1. Ok, so that matches the first option; de-ANSI-fication was deprecated slightly afterwards, in automake 1.11.*2*: [...] this change should end up into 1.11.2, [1] $ fgrep de-ANSI-fication automake-1.11.*/NEWS automake-1.11.1/NEWS:* Automatic de-ANSI-fication cleaned up. automake-1.11.2/NEWS: - The Automake support for automatic de-ANSI-fication will be removed in automake-1.11.2/NEWS:* Automatic de-ANSI-fication cleaned up. If I got you right, the inconvenience itself seems to be carrying a patch only for that matter, if an env var/cmdline arg could do. So, for that, I wouldn't know another option. Would that be OK with the rationale above? I am concerned that, if we cannot rebuild the files from the upstream source without patching, we cannot trust future versions of autoconf/automake to process our patched code correctly. This leads to a huge maintainance cost. That's certainly understandable. Nonetheless, I'd think the problem is not tied to future versions only, but old ones too; 1.11.x seems old already (2009/2012). Anything = 1.11.2 would fail for de-ANSI-fication. Interestingly, that thread also mentions libjpeg8c was affected, and then 8*d* (next version) introduced -Wno-obsolete in configure.ac. So I'd think they also chose to stick no -Wno-obsolete rather than removing ansi2knr on libjpeg8; and then libjpeg*9* actually removed it. Now, well, AFAICT there are not many options, since: 1) automake 1.11.x releases finished 2) automake 1.11.2+ only handle de-ANSI-fication with -Wno-obsolete 2) automake 1.12.x releases don't handle de-ANSI-fication 3) libjpeg6 releases finished So autoreconf on libjpeg6 is tied to 1.11.x, and it would require -Wno-obsolete (adopted on libjpeg8 from 8c to 8d). Sure enough, I would be happy to provide a patch that only updates the minimum required pieces for building on ppc64el, and not doing autoreconf at all. (the other way around :) What is your take on that? Thanks! [1] http://lists.gnu.org/archive/html/automake/2011-06/msg7.html -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753537: mpclib3: build with dh-autoreconf (fixes FTBFS on ppc64el)
Package: src:mpclib3
Version: 1.0.1-1
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
User: debian-de...@lists.debian.org
Usertags: autoreconf
Hi Laurent,
This trivial patch enables dh-autoreconf on mpclib3.
May you please consider incorporating it in a new upload?
This fixes a FTBFS on ppc64el:
dh_install: libmpc-dev missing files (usr/lib/*/libmpc.so), aborting
Producing shared libraries:
$ dpkg-deb -c libmpc3_1.0.1-1.1_ppc64el.deb | fgrep .so
-rw-r--r-- root/root105440 2014-07-02 18:10
./usr/lib/powerpc64le-linux-gnu/libmpc.so.3.0.0
lrwxrwxrwx root/root 0 2014-07-02 18:10
./usr/lib/powerpc64le-linux-gnu/libmpc.so.3 - libmpc.so.3.0.0
The built packages have the same contents as the powerpc port:
(built debs in ppc64el/, downloaded powerpc debs in powerpc/)
$ for arch in ppc64el powerpc; do
cd $arch
mkdir contents
for deb in *.deb; do
dpkg-deb -c $deb
| cut -d. -f2-
| sed 's,powerpc\(64le\)\?,GNU_ARCH,g'
| sort
contents/${deb%%_*};
done
cd ..;
done
$ diff -r ppc64el/contents/ powerpc/contents
$
Thank you,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru mpclib3-1.0.1/debian/changelog mpclib3-1.0.1/debian/changelog
--- mpclib3-1.0.1/debian/changelog 2014-07-02 18:17:28.0 -0300
+++ mpclib3-1.0.1/debian/changelog 2014-07-02 18:17:28.0 -0300
@@ -1,3 +1,10 @@
+mpclib3 (1.0.1-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * Build with dh-autoreconf (requires svnversion).
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Wed, 02 Jul 2014
18:06:39 -0300
+
mpclib3 (1.0.1-1) unstable; urgency=low
* New upstream release (closes: #696696).
diff -Nru mpclib3-1.0.1/debian/control mpclib3-1.0.1/debian/control
--- mpclib3-1.0.1/debian/control2014-07-02 18:17:28.0 -0300
+++ mpclib3-1.0.1/debian/control2014-07-02 18:17:28.0 -0300
@@ -1,7 +1,7 @@
Source: mpclib3
Priority: extra
Maintainer: Laurent Fousse lfou...@debian.org
-Build-Depends: debhelper (= 7), autotools-dev, libmpfr-dev, libgmp-dev
+Build-Depends: debhelper (= 7), autotools-dev, libmpfr-dev, libgmp-dev,
dh-autoreconf, subversion
Standards-Version: 3.8.4
Section: libs
Homepage: http://www.multiprecision.org/mpc/
diff -Nru mpclib3-1.0.1/debian/rules mpclib3-1.0.1/debian/rules
--- mpclib3-1.0.1/debian/rules 2014-07-02 18:17:28.0 -0300
+++ mpclib3-1.0.1/debian/rules 2014-07-02 18:17:28.0 -0300
@@ -36,12 +36,7 @@
config.status: configure
dh_testdir
# Add here commands to configure the package.
-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 \
--libdir=\$${prefix}/lib/$(DEB_HOST_MULTIARCH) \
--mandir=\$${prefix}/share/man \
@@ -70,6 +65,7 @@
[ ! -f Makefile ] || $(MAKE) distclean
rm -f config.sub config.guess
+ dh_autoreconf_clean
dh_clean
install: build
Bug#751796: closed by Andreas Metzler ametz...@debian.org (Bug#751796: fixed in gnutls26 2.12.23-17)
On 07/03/2014 03:06 PM, Debian Bug Tracking System wrote: #751796: Patch for dh-autoreconf on gnutls26 It has been closed by Andreas Metzler ametz...@debian.org. Thanks for the upload, it builds successfully on ppc64el. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753362: libjpeg6b: build with dh-autoreconf
On 07/05/2014 01:36 PM, Bill Allombert wrote: On Tue, Jul 01, 2014 at 02:52:41PM -0300, Mauricio Faria de Oliveira wrote: [...] That's certainly understandable. Nonetheless, I'd think the problem is not tied to future versions only, but old ones too; 1.11.x seems old already (2009/2012). Anything = 1.11.2 would fail for de-ANSI-fication. It establishes that automake developers are willing to break the API in minor releases. This is a very bad sign. Yes. I think that change is a bit weird for minor releases too. [...] 3) libjpeg6 releases finished [...] 3) is wrong :) Thanks for correcting me :) I admit I may have not read enough about it, just some skimming over ijg.org and libjpeg.sf.net. But anyway, I have applied your patch since it is the best fix all-round. Thanks again for your effort, Glad to contribute. The package now builds properly on ppc64el: Package: libjpeg62 Source: libjpeg6b Version: 6b2-1 [..] -rw-r--r-- root/root170072 2014-07-05 22:09 ./usr/lib/powerpc64le-linux-gnu/libjpeg.so.62.0.0 Thank you. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754146: gettext: fix FTBFS on ppc64el with autoreconf or libtool patch (provided)
Package: src:gettext Version: 0.18.3.2-3 Tags: patch User: debian-powe...@lists.debian.org Usertags: ppc64el User: debian-de...@lists.debian.org Usertags: autoreconf Hi Santiago, Either of the attached patches fix a FTBFS on ppc64el due to shared libraries not being built (due to old libtool.m4/configure script). Would you please consider one of them for an upload? One is a simple patch (fixes only ppc64el). The other is a more complete dh-autoreconf thing (fixes ppc64el and other new arches, but uses dh_, which AFAICT the package is not using, but does build successfully). With either of them applied, the contents of the built packages (i.e., dpkg-deb -c) are equivalent to those of powerpc packages (i.e., no diff in file listings, accounting for GNU arch name difference). Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center gettext-autoreconf.debdiff.gz Description: GNU Zip compressed data gettext-ppc64el-libtool.debdiff.gz Description: GNU Zip compressed data
Bug#754213: linux-tools: build on ppc64el
Package: src:linux-tools
Version: 3.14-1
Tags: patch
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Hi maintainers,
The attached patch adds support for ppc64el in linux-tools.
(I ommitted the output of the 'debian/control' target)
Would you please consider it for an upload?
Among other things, it includes defining '__SANE_USERSPACE_TYPES__' on
ppc64 and ppc64el, in order to fix the build failure reported at
#747151 (more details there).
With it applied, the built packages have equivalent contents to amd64,
accounting for the /usr/lib{,64} difference. I could run 'perf stat':
# perf_3.14 stat sleep 1
Performance counter stats for 'sleep 1':
0.542034 task-clock (msec) #0.001 CPUs
utilized
1 context-switches #0.002 M/sec
0 cpu-migrations#0.000 K/sec
49 page-faults #0.090 M/sec
2266748 cycles#4.182 GHz
454072 stalled-cycles-frontend # 20.03% frontend
cycles idle
1604224 stalled-cycles-backend# 70.77% backend
cycles idle
556703 instructions #0.25 insns per
cycle
#2.88 stalled cycles
per insn
not counted branches
not counted branch-misses
1.001009786 seconds time elapsed
# echo $?
0
Thank you,
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
diff -Nru linux-tools-3.14/debian/build/scripts/mod/Makefile.real
linux-tools-3.14/debian/build/scripts/mod/Makefile.real
--- linux-tools-3.14/debian/build/scripts/mod/Makefile.real 2013-06-03
10:19:37.0 -0300
+++ linux-tools-3.14/debian/build/scripts/mod/Makefile.real 2014-07-08
14:56:40.0 -0300
@@ -6,6 +6,16 @@
include $(top_srcdir)/debian/build/Makefile.inc
+DEB_HOST_ARCH_CPU := $(shell dpkg-architecture -qDEB_HOST_ARCH_CPU)
+
+ifneq (,$(filter powerpc64 ppc64el,$(DEB_HOST_ARCH_CPU)))
+ # Fix include/linux/types.h:148:1: error: unknown type name 'u32'.
+ # See linux commits:
+ # asm/types.h: Remove include/asm-generic/int-l64.h
+ # powerpc: Add __SANE_USERSPACE_TYPES__ to asm/types.h for LL64
+ CFLAGS += -D__SANE_USERSPACE_TYPES__
+endif
+
modpost.real-$(TYPE): file2alias.real-$(TYPE).o modpost.real-$(TYPE).o
sumversion.real-$(TYPE).o
$(CC) $(CFLAGS) $(LDFLAGS) -o $@ $^
diff -Nru linux-tools-3.14/debian/build/tools/perf/Makefile
linux-tools-3.14/debian/build/tools/perf/Makefile
--- linux-tools-3.14/debian/build/tools/perf/Makefile 2014-03-19
20:56:58.0 -0300
+++ linux-tools-3.14/debian/build/tools/perf/Makefile 2014-07-08
14:49:28.0 -0300
@@ -21,6 +21,8 @@
KERNEL_ARCH_PERF = powerpc
else ifeq ($(DEB_HOST_ARCH_CPU),powerpc64)
KERNEL_ARCH_PERF = powerpc
+else ifeq ($(DEB_HOST_ARCH_CPU),ppc64el)
+ KERNEL_ARCH_PERF = powerpc
else ifeq ($(DEB_HOST_ARCH_CPU),s390)
KERNEL_ARCH_PERF = s390
else ifeq ($(DEB_HOST_ARCH_CPU),s390x)
diff -Nru linux-tools-3.14/debian/changelog linux-tools-3.14/debian/changelog
--- linux-tools-3.14/debian/changelog 2014-04-28 13:46:25.0 -0300
+++ linux-tools-3.14/debian/changelog 2014-07-08 14:53:00.0 -0300
@@ -1,3 +1,13 @@
+linux-tools (3.14-1.1) UNRELEASED; urgency=medium
+
+ * Non-maintainer upload.
+ * ppc64el/ppc64: fix FTBFS on linux 3.14 (build/scripts/mod/Makefile.real).
+ * ppc64el: set KERNEL_ARCH_PERF (build/tools/perf/Makefile).
+ * ppc64el: build linux-tools (rules.real, control.main.in).
+ * ppc64el: add build-dep on libnuma-dev (templates/control.source.in).
+
+ -- Mauricio Faria de Oliveira mauri...@linux.vnet.ibm.com Tue, 08 Jul 2014
14:41:13 -0300
+
linux-tools (3.14-1) unstable; urgency=medium
* New upstream release
diff -Nru linux-tools-3.14/debian/rules.real linux-tools-3.14/debian/rules.real
--- linux-tools-3.14/debian/rules.real 2013-10-18 21:12:53.0 -0300
+++ linux-tools-3.14/debian/rules.real 2014-07-08 14:45:31.0 -0300
@@ -9,7 +9,7 @@
VERSION_DEBIAN_FULL := $(shell dpkg-parsechangelog | sed -ne 's,^Version:
*\(.*\)$$,\1,p')
binary-arch: install-kbuild install-usbip
-ifneq ($(filter alpha amd64 armel armhf hppa i386 powerpc ppc64 s390 s390x sh4
sparc sparc64,$(DEB_BUILD_ARCH)),)
+ifneq ($(filter alpha amd64 armel armhf hppa i386 powerpc ppc64 ppc64el s390
s390x sh4 sparc sparc64,$(DEB_BUILD_ARCH)),)
binary-arch: install-tools
endif
diff -Nru linux-tools-3.14/debian/templates/control.main.in
linux-tools-3.14/debian/templates/control.main.in
--- linux-tools-3.14/debian/templates/control.main.in 2013-09-24
21:18:33.0 -0300
+++ linux-tools-3.14/debian/templates/control.main.in 2014-07-08
14:31:14.0 -0300
@@ -7,7 +7,7 @@
Package: linux-tools-@version@
Section: devel
Bug#747151: Explanation for the error, other patch available for ppc64/ppc64el.
Package: src:linux-tools
Version: 3.14-1
User: debian-powe...@lists.debian.org
Usertags: ppc64el
Hi,
I looked at this for a while, in order to fix for ppc64el. A patch for
fixing this was submitted as part of #754213.
In short:
Using 'int-ll64.h' (which defines u32/u64/et al) in userspace on ppc64
requires defining __SANE_USERSPACE_TYPES__, introduced in commit [4].
Rationale:
-
This build failure
make[6]: Entering directory `/«PKGBUILDDIR»/debian/build/scripts/mod'
gcc -include real-lsb-32/types.h -I/«PKGBUILDDIR»/include -S -o
real-lsb-32/devicetable-offsets.s
/«PKGBUILDDIR»/scripts/mod/devicetable-offsets.c
In file included from ./real-lsb-32/types.h:1:0,
from command-line:0:
/«PKGBUILDDIR»/include/linux/types.h:148:1: error: unknown type name
'u32'
typedef u32 dma_addr_t;
^
occurs because of a change in the asm/int-{l,ll}64.h logic between
3.13 and 3.14.
(ppc64 build on with linux-libc-dev 3.13 succeeds [1] but 3.14 fails
[2])
The file 'int-l64.h' which defined non-double-underscore u32/u64 was
removed in commit [3] ('asm/types.h: Remove include/asm-generic
/int-l64.h') for *kernelspace*.
For *userspace*, the commits mentions this:
For backwards compatibility, alpha, ia64, mips64, and
powerpc64 still use int-l64.h in userspace.
but 'include/*uapi*/asm-generic/int-l64.h' defines double-underscore
__u32/__u64 (for userspace data type exportation, double-underscore)
The non-double-underscore definition u32/u64 is in 'int-*ll*64.h'.
Now, for ppc64, there a flag just for that (__SANE_USERSPACE_TYPES__),
which was introduced in [4] ('powerpc: Add__SANE_USERSPACE_TYPES__ to
asm/types.h for LL64'):
[...] Some user programs (e.g. kvmtool) may actually
want LL64, so this patch adds a check for
__SANE_USERSPACE_TYPES__ so
that, if defined, int-ll64.h is included instead.
[...]
#if !defined(__SANE_USERSPACE_TYPES__)
[line breaks added for clarity]
defined(__powerpc64__)
!defined(__KERNEL__)
# include asm-generic/int-l64.h
#else
# include asm-generic/int-ll64.h
#endif
It is used by perf (for example) [4] ('perf tools, powerpc: Fix compile
warnings in tests/attr.c').
I didn't find anything similar for alpha, unfortunately.
Links:
-
[1] ppc64 build log: linux-tools with linux-libc-dev_3.13.5-1 (successful)
http://buildd.debian-ports.org/status/fetch.php?pkg=linux-toolsarch=ppc64ver=3.13.6-1stamp=1395302858
[2] ppc64 build log: linux-tools with linux-libc-dev_3.14.2-1 (failure)
http://buildd.debian-ports.org/status/fetch.php?pkg=linux-toolsarch=ppc64ver=3.14-1stamp=1399098596
[3] asm/types.h: Remove include/asm-generic/int-l64.h
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/include/asm-generic/int-l64.h?id=0c79a8e29b5fcbcbfd611daf9d500cfad8370fcf
[4] powerpc: Add __SANE_USERSPACE_TYPES__ to asm/types.h for LL64
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/arch/powerpc/include/asm/types.h?id=2c9c6ce0199a4d252e20c531cfdc9d24e39235c0
[5] perf tools, powerpc: Fix compile warnings in tests/attr.c
https://git.kernel.org/cgit/linux/kernel/git/stable/linux-stable.git/commit/?id=e3541ec75219819d3235f80125a1a75d798ff6e1
--
Mauricio Faria de Oliveira
IBM Linux Technology Center
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#689622: libnih: ping (patch available)
Package: src:libnih Hi Scott, Sorry about pinging you directly, but this one is relatively important, as libnih is part of debootstrap (minbase variant). Fixing this would greatly help the ppc64el port with the few pieces left for a clean debootstrap. Thanks for your attention. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#753537: mpclib3: ping
Package: src:mpclib3 Hi Laurent. Would you have any news or comments about the patch in this bug? This one is relatively important, as mpclib3 is part of debootstrap. Thank you, -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751390: pcre3: ping
Package: src:pcre3 Hi Mark, We believe the patch submitted in message #44 [1] addressed all points raised. Would you have any news or comments about it, or consider it for upload? This is relatively important for ppc64el, as it is part of debootstrap. Thanks again, [1] http://bugs.debian.org/751390#44 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#748855: thanks
Package: src:libusb Thanks for the upload. I missed replying earlier. -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751822: libprelude: ping / fix FTBFS on ppc64el (patch available)
Package: src:libprelude Hi Pierre, Sorry about pinging you directly. Would you have any updates here? The patches provided in message #5 [1] fix the problem reported. Thanks! [1] https://bugs.debian.org/751822#5 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#751917: ghostscript: [ping] fix FTBFS on ppc64el (patch available)
Package: src:ghostscript Hi, Any updates/comments? The patch provided in message #5 [1] fixes the problem reported. Thank you, [1] https://bugs.debian.org/751917#5 -- Mauricio Faria de Oliveira IBM Linux Technology Center -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
