Bug#759825: audtty: FTBFS: main.c:20:31: fatal error: audacious/audctrl.h: No such file or directory
Hello, Chris. Do you still plan to do this upload? I can send an NMU, but I am not a DD, so the process will be slower. Thanks! -- Fernando Seiti Furusato IBM Linux Technology Center signature.asc Description: OpenPGP digital signature
Bug#845082: numexpr FTBFS on ppc64el: test failures
X-Debbugs-Cc: gin...@debian.org, bren...@br.ibm.com On 11/29/2016 03:18 PM, Fernando Seiti Furusato wrote: > Also I had to consider a ci failure on appveyor, that is why I also > included a verification for msvc version on the PR. By the way, it has been merged upstream. signature.asc Description: OpenPGP digital signature
Bug#845082: numexpr FTBFS on ppc64el: test failures
Hello. At first I tried to fix that with round(). Problem is round() returns the same type as the argument so the cast happens anyway. I would recommend using the latest version, with llround(), which returns long long. Also I had to consider a ci failure on appveyor, that is why I also included a verification for msvc version on the PR. Regards. -- Fernando Seiti Furusato IBM Linux Technology Center signature.asc Description: OpenPGP digital signature
Bug#845082: numexpr FTBFS on ppc64el: test failures
Hello.
It is noticeable that it fails on a 3^3 array operation.
On "scalar" operations, it doesn't show the same behavior.
Like so:
$ python3.5
Python 3.5.2+ (default, Nov 3 2016, 11:10:16)
[GCC 6.2.0 20161027] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import numexpr as ne
>>> a=[3]
>>> b=[3]
>>> ne.evaluate("a ** b") # array operation
array([26], dtype=int64)
>>> ne.evaluate("3 ** 3") # scalar operation
array(27, dtype=int32)
$ python
Python 2.7.12+ (default, Nov 4 2016, 17:04:30)
[GCC 6.2.0 20161027] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import numexpr as ne
>>> a=[3]
>>> b=[3]
>>> ne.evaluate("a ** b")
array([26])
>>> ne.evaluate("3 ** 3")
array(27, dtype=int32)
I am not sure if it fails with other values as well.
I will keep looking.
Regards
--
Fernando Seiti Furusato
IBM Linux Technology Center
signature.asc
Description: OpenPGP digital signature
Bug#843691: glibc: FTBFS on ppc64el: Error: operand out of range
Source: glibc Version: 2.24-5 Severity: serious Hello, glibc is failing to build on ppc64el, on sid with the following: .../sysdeps/powerpc/powerpc64/power6/memset.S: Assembler messages: .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range (5 is not between 0 and 1) .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: operand out of range (128 is not between 0 and 31) .../sysdeps/powerpc/powerpc64/power6/memset.S:254: Error: missing operand This was an attempt with sbuild with sid. It initially built on the same version on buildd, 20 days ago or so, but the failure was also observed on cross-compilation. Thanks. Fernando
Bug#730903: mutrace: FTBFS: b-d on libiberty-dev instead of binutils-dev No such file or directory
Hello. Actually, this works, not replacing build-deps, but adding libiberty-dev in addition to binutils-dev. With that and adding -I/usr/include/libiberty as suggested by YunQiang Su, the package built in a clean chroot (using sbuild). I produced a debdiff which does the aforementioned, attached here. Thanks and regards. Fernando diff -u mutrace-0.2.0/Makefile.am mutrace-0.2.0/Makefile.am --- mutrace-0.2.0/Makefile.am +++ mutrace-0.2.0/Makefile.am @@ -86,7 +86,8 @@ -ldl \ "-static -lbfd" libmutrace_backtrace_symbols_la_CFLAGS = \ - $(PTHREAD_CFLAGS) + $(PTHREAD_CFLAGS) \ + -I/usr/include/libiberty mutrace: mutrace.in Makefile sed -e 's,@PACKAGE_STRING\@,$(PACKAGE_STRING),g' \ diff -u mutrace-0.2.0/debian/changelog mutrace-0.2.0/debian/changelog --- mutrace-0.2.0/debian/changelog +++ mutrace-0.2.0/debian/changelog @@ -1,3 +1,12 @@ +mutrace (0.2.0-2.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * debian/control: include libiberty-dev to build-depends + * debian/patches/libiberty.patch: includes -I/usr/include/libiberty to +Makefile.am + + -- Fernando Seiti Furusato <ferse...@br.ibm.com> Thu, 12 May 2016 09:40:17 -0400 + mutrace (0.2.0-2) unstable; urgency=low * Link statically against bfd, LP: #875928 diff -u mutrace-0.2.0/debian/control mutrace-0.2.0/debian/control --- mutrace-0.2.0/debian/control +++ mutrace-0.2.0/debian/control @@ -4,7 +4,7 @@ Maintainer: Riku Voipio <riku.voi...@linaro.org> Standards-Version: 3.9.1 Homepage: http://0pointer.de/blog/projects/mutrace.html -Build-Depends: debhelper (>=8), automake, autoconf, libtool, binutils-dev +Build-Depends: debhelper (>=8), automake, autoconf, libtool, binutils-dev, libiberty-dev Package: mutrace Architecture: any --- mutrace-0.2.0.orig/patches/libiberty.patch +++ mutrace-0.2.0/patches/libiberty.patch @@ -0,0 +1,14 @@ +Index: mutrace-0.2.0/Makefile.am +=== +--- mutrace-0.2.0.orig/Makefile.am mutrace-0.2.0/Makefile.am +@@ -86,7 +86,8 @@ libmutrace_backtrace_symbols_la_LIBADD = + -ldl \ + "-static -lbfd" + libmutrace_backtrace_symbols_la_CFLAGS = \ +- $(PTHREAD_CFLAGS) ++ $(PTHREAD_CFLAGS) \ ++ -I/usr/include/libiberty + + mutrace: mutrace.in Makefile + sed -e 's,@PACKAGE_STRING\@,$(PACKAGE_STRING),g' \ only in patch2: unchanged: --- mutrace-0.2.0.orig/patches/series +++ mutrace-0.2.0/patches/series @@ -0,0 +1 @@ +libiberty.patch
Bug#708459: cairo-5c: FTBFS: make[3]: *** [check-TESTS] Error 1
Source: cairo-5c Followup-For: Bug #708459 user debian-powe...@lists.debian.org usertags 708459 + ppc64el thanks This also affects ppc64el architecture. I recently tried to build it and there are more tests failing. The full log (although a little old) can be found at: https://buildd.debian.org/status/fetch.php?pkg=cairo-5c=ppc64el=1.8.1=1410483854 Thanks. Fernando
Bug#822379: hidrd FTBFS on several platforms
Source: hidrd Followup-For: Bug #822379 Hi. I could verify that, at least on ppc64el, it is related to optimization. When forcing the compilation flag -O0, it does not fail to build. I still have not figured out the cause of this though, but it is a starting point just in case. Regards. Fernando
Bug#725536: libapache2-mod-authn-yubikey: FTBFS: make[1]: *** No rule to make target `../../apache228-install/build/special.mk'. Stop.
Source: libapache2-mod-authn-yubikey Followup-For: Bug #725536 Hello. This also occurs on ppc64el and probably on other architectures that did not need to rebuild (Some are installed for ~1k days, for instance). A solution that I found for this was to import some of the *mk files to the package. This and fixing the Makefile to use those files allowed the package to build. I tested it on ppc64el and amd64 and it built successfully. The modifications I made are in the patch attached as well as some comments on them. Regards. diff -Nru libapache2-mod-authn-yubikey-1.0/debian/changelog libapache2-mod-authn-yubikey-1.0/debian/changelog --- libapache2-mod-authn-yubikey-1.0/debian/changelog 2013-07-10 05:58:36.0 -0400 +++ libapache2-mod-authn-yubikey-1.0/debian/changelog 2016-04-27 13:50:18.0 -0400 @@ -1,3 +1,12 @@ +libapache2-mod-authn-yubikey (1.0-1.2) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Imported build/rules.mk build/special.mk and build/config_vars.mk from +apache2 to fix ftbfs + * Fixed Makefile to use the right directory + + -- Fernando Seiti Furusato <ferse...@br.ibm.com> Wed, 27 Apr 2016 13:47:49 -0400 + libapache2-mod-authn-yubikey (1.0-1.1) unstable; urgency=low * Non-maintainer upload. diff -Nru libapache2-mod-authn-yubikey-1.0/debian/patches/fix-ftbfs.patch libapache2-mod-authn-yubikey-1.0/debian/patches/fix-ftbfs.patch --- libapache2-mod-authn-yubikey-1.0/debian/patches/fix-ftbfs.patch 1969-12-31 19:00:00.0 -0500 +++ libapache2-mod-authn-yubikey-1.0/debian/patches/fix-ftbfs.patch 2016-04-27 13:49:29.0 -0400 @@ -0,0 +1,422 @@ +Index: libapache2-mod-authn-yubikey-1.0/Makefile +=== +--- libapache2-mod-authn-yubikey-1.0.orig/Makefile libapache2-mod-authn-yubikey-1.0/Makefile +@@ -4,9 +4,9 @@ + ## + + builddir=. +-top_srcdir=../../apache228-install +-top_builddir=../../apache228-install +-include ../../apache228-install/build/special.mk ++top_srcdir=. ++top_builddir=. ++include ./build/special.mk + + # the used tools + APXS=apxs +Index: libapache2-mod-authn-yubikey-1.0/build/rules.mk +=== +--- /dev/null libapache2-mod-authn-yubikey-1.0/build/rules.mk +@@ -0,0 +1,245 @@ ++# Licensed to the Apache Software Foundation (ASF) under one or more ++# contributor license agreements. See the NOTICE file distributed with ++# this work for additional information regarding copyright ownership. ++# The ASF licenses this file to You under the Apache License, Version 2.0 ++# (the "License"); you may not use this file except in compliance with ++# the License. You may obtain a copy of the License at ++# ++# http://www.apache.org/licenses/LICENSE-2.0 ++# ++# Unless required by applicable law or agreed to in writing, software ++# distributed under the License is distributed on an "AS IS" BASIS, ++# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. ++# See the License for the specific language governing permissions and ++# limitations under the License. ++# ++# ++# The build environment was originally provided by Sascha Schumann. ++ ++include $(top_builddir)/build/config_vars.mk ++ ++# Combine all of the flags together in the proper order so that ++# the user-defined flags can always override the configure ones, if needed. ++# Note that includes are listed after the flags because -I options have ++# left-to-right precedence and CPPFLAGS may include user-defined overrides. ++# The "MOD_" prefixed variable are provided to allow modules to insert their ++# (per-subdirectory) settings through definitions in modules.mk, with highest ++# precedence. ++# ++ALL_CFLAGS = $(MOD_CFLAGS) $(EXTRA_CFLAGS) $(NOTEST_CFLAGS) $(CFLAGS) ++ALL_CPPFLAGS = $(DEFS) $(INTERNAL_CPPFLAGS) $(MOD_CPPFLAGS) $(EXTRA_CPPFLAGS) $(NOTEST_CPPFLAGS) $(CPPFLAGS) ++ALL_CXXFLAGS = $(MOD_CXXFLAGS) $(EXTRA_CXXFLAGS) $(NOTEST_CXXFLAGS) $(CXXFLAGS) ++ALL_LDFLAGS = $(MOD_LDFLAGS) $(EXTRA_LDFLAGS) $(NOTEST_LDFLAGS) $(LDFLAGS) ++ALL_LIBS = $(MOD_LIBS) $(EXTRA_LIBS) $(NOTEST_LIBS) $(LIBS) ++ALL_INCLUDES = $(MOD_INCLUDES) $(INCLUDES) $(EXTRA_INCLUDES) ++ ++# Compile commands ++ ++BASE_CC = $(CC) $(ALL_CFLAGS) $(ALL_CPPFLAGS) $(ALL_INCLUDES) ++BASE_CXX = $(CXX) $(ALL_CXXFLAGS) $(ALL_CPPFLAGS) $(ALL_INCLUDES) ++ ++COMPILE = $(BASE_CC) $(PICFLAGS) ++CXX_COMPILE = $(BASE_CXX) $(PICFLAGS) ++ ++SH_COMPILE = $(LIBTOOL) --mode=compile $(BASE_CC) $(SHLTCFLAGS) -c $< && touch $@ ++SH_CXX_COMPILE = $(LIBTOOL) --mode=compile $(BASE_CXX) $(SHLTCFLAGS) -c $< && touch $@ ++ ++LT_COMPILE = $(LIBTOOL) --mode=compile $(COMPILE) $(LTCFLAGS) -c $< && touch $@ ++LT_CXX_COMPILE = $(LIBTOOL) --mode=compile $(CXX_COMPILE) $(LTCFLAGS) -c $< && touch $@ ++ ++# Link-related commands ++ ++LINK = $(LIBTOOL) --mode=link $(CC) $(ALL_CFLAGS) $(PILDFLAGS
Bug#807511: cpqarrayd: DNBFS (was: Re: failed ppc64el build of cpqarrayd 2.3-4)
Source: cpqarrayd Version: 2.3-4 Followup-For: Bug #807511 Hello. I have been trying to fiture out this failure with cpqarrayd on ppc64el. Since it is a conflict on the types definition, I worked around it by patching the linux package downloaded to the source tree. The result is the debdiff attached. It is a very ugly workaround, but it works. The build finishes with no errors on ppc64el and I also tested it on amd64 to make sure it does not affected it. It is a ppc64el specific one, ie, does not work for ppc or ppc64 BE. Thanks! diff -Nru cpqarrayd-2.3/debian/changelog cpqarrayd-2.3/debian/changelog --- cpqarrayd-2.3/debian/changelog 2015-08-08 06:55:01.0 + +++ cpqarrayd-2.3/debian/changelog 2016-02-10 11:05:07.0 + @@ -1,3 +1,10 @@ +cpqarrayd (2.3-4.1) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Patch to fix ftbfs on ppc64el + + -- Fernando Seiti Furusato <ferse...@br.ibm.com> Wed, 10 Feb 2016 11:04:55 + + cpqarrayd (2.3-4) unstable; urgency=medium * Make build agnostic of kernel major version number (Closes: #791618). diff -Nru cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch --- cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch 1970-01-01 00:00:00.0 + +++ cpqarrayd-2.3/debian/patches/linux-types-ppc64el.patch 2016-02-10 11:04:16.0 + @@ -0,0 +1,63 @@ +diff -purN a/debian/linux/linux-source-4.3/include/linux/types.h b/debian/linux/linux-source-4.3/include/linux/types.h +--- a/debian/linux/linux-source-4.3/include/linux/types.h 2016-02-09 17:42:39.476237208 + b/debian/linux/linux-source-4.3/include/linux/types.h 2016-02-09 17:44:30.950788014 + +@@ -9,20 +9,22 @@ + #define DECLARE_BITMAP(name,bits) \ + unsigned long name[BITS_TO_LONGS(bits)] + ++#if defined(__PPC64__) && defined(__LITTLE_ENDIAN__) ++#define u32 __u32 ++#define u64 __u64 ++#endif ++ + typedef __u32 __kernel_dev_t; + +-typedef __kernel_fd_set fd_set; +-typedef __kernel_dev_t dev_t; ++ + typedef __kernel_ino_t ino_t; + typedef __kernel_mode_t mode_t; + typedef unsigned short umode_t; +-typedef __u32 nlink_t; + typedef __kernel_off_t off_t; + typedef __kernel_pid_t pid_t; + typedef __kernel_daddr_t daddr_t; + typedef __kernel_key_t key_t; + typedef __kernel_suseconds_t suseconds_t; +-typedef __kernel_timer_t timer_t; + typedef __kernel_clockid_t clockid_t; + typedef __kernel_mqd_t mqd_t; + +@@ -41,9 +43,16 @@ typedef __kernel_old_uid_t old_uid_t; + typedef __kernel_old_gid_t old_gid_t; + #endif /* CONFIG_UID16 */ + ++#if !defined(__PPC64__) && !defined(__LITTLE_ENDIAN__) ++typedef __kernel_fd_set fd_set; ++typedef __kernel_dev_t dev_t; ++typedef __u32 nlink_t; ++typedef __kernel_timer_t timer_t; ++ + #if defined(__GNUC__) + typedef __kernel_loff_t loff_t; + #endif ++#endif /* ppc64el */ + + /* + * The following typedefs are also protected by individual ifdefs for +@@ -126,6 +135,7 @@ typedef __s64 int64_t; + * + * blkcnt_t is the type of the inode's block count. + */ ++#if !defined(__PPC64__) && !defined(__LITTLE_ENDIAN__) + #ifdef CONFIG_LBDAF + typedef u64 sector_t; + typedef u64 blkcnt_t; +@@ -133,6 +143,7 @@ typedef u64 blkcnt_t; + typedef unsigned long sector_t; + typedef unsigned long blkcnt_t; + #endif ++#endif + + /* + * The type of an index into the pagecache. diff -Nru cpqarrayd-2.3/debian/rules cpqarrayd-2.3/debian/rules --- cpqarrayd-2.3/debian/rules 2015-08-08 06:43:54.0 + +++ cpqarrayd-2.3/debian/rules 2016-02-10 11:03:55.0 + @@ -34,6 +34,7 @@ mkdir debian/linux cd debian/linux && tar xvf /usr/src/$(KSRC).tar.xz touch unpack-stamp + patch -p1 < $(CURDIR)/debian/patches/linux-types-ppc64el.patch config.status: configure unpack dh_testdir
Bug#759848: babel: FTBFS: configure.ac:76: error: required file 'config/compile' not found
Source: babel Version: 1.4.0.dfsg-8.2 Followup-For: Bug #759848 Hello. The problem above can be solved by adding usage of dh-autoreconf to debian/rules. Since it runs in more than one directory it would be also necessary to add an 'autoreconf' file to debian. This can be seen on the debdiff attached. Although dh-autoreconf fixes the particular problem reported in this bug, the build breaks at another point. Here is the tail of the log: > libtool: compile: gfortran -DHAVE_CONFIG_H -I. -I../../../runtime/sidl > -I../../../runtime/sidl -g -O2 -c sidl_string_array.f90 -o > sidl_string_array.o >/dev/null 2>&1 > rm -f sidl_string_array.f90 sidl_string_array.tmp > gcc -E -traditional -DHAVE_CONFIG_H -I. -I../../../runtime/sidl > -I../../../runtime/sidl \ > -P -o sidl_BaseClass.tmp -x c `test -f 'sidl_BaseClass.F90' || echo > './'`sidl_BaseClass.F90 > sidl_BaseClass.F90:200:0: error: detected recursion whilst expanding macro > "bool" > ! out bool retval > ^ > sidl_BaseClass.F90:217:0: error: detected recursion whilst expanding macro > "bool" > ! out bool retval > ^ > sidl_BaseClass.F90:352:0: error: detected recursion whilst expanding macro > "bool" > ! out bool retval > ^ > sidl_BaseClass.F90:366:0: error: detected recursion whilst expanding macro > "bool" > ! out bool retval > ^ > sidl_BaseClass.F90:380:0: error: detected recursion whilst expanding macro > "bool" > ! in bool enable > ^ > make[4]: *** [sidl_BaseClass.lo] Error 1 > make[3]: *** [all-recursive] Error 1 > Makefile:1451: recipe for target 'sidl_BaseClass.lo' failed > make[4]: Leaving directory '/«PKGBUILDDIR»/lib/sidlstubs/F90' > Makefile:545: recipe for target 'all-recursive' failed > make[3]: Leaving directory '/«PKGBUILDDIR»/lib/sidlstubs' > make[2]: *** [all-recursive] Error 1 > Makefile:606: recipe for target 'all-recursive' failed > make[2]: Leaving directory '/«PKGBUILDDIR»/lib' > make[1]: *** [all-recursive] Error 1 > make: *** [stamp-build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > Makefile:604: recipe for target 'all-recursive' failed > make[1]: Leaving directory '/«PKGBUILDDIR»' > debian/rules:19: recipe for target 'stamp-build' failed I do not know what could be causin this. Regards. Fernando diff -Nru babel-1.4.0.dfsg/debian/autoreconf babel-1.4.0.dfsg/debian/autoreconf --- babel-1.4.0.dfsg/debian/autoreconf 1969-12-31 19:00:00.0 -0500 +++ babel-1.4.0.dfsg/debian/autoreconf 2016-02-10 11:56:43.0 -0500 @@ -0,0 +1,2 @@ +. +./runtime diff -Nru babel-1.4.0.dfsg/debian/changelog babel-1.4.0.dfsg/debian/changelog --- babel-1.4.0.dfsg/debian/changelog 2013-05-26 15:33:17.0 -0400 +++ babel-1.4.0.dfsg/debian/changelog 2016-02-10 11:56:57.00000 -0500 @@ -1,3 +1,10 @@ +babel (1.4.0.dfsg-8.3) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Replaced various autotools usage by dh-autoreconf + + -- Fernando Seiti Furusato <ferse...@br.ibm.com> Wed, 10 Feb 2016 11:56:47 -0500 + babel (1.4.0.dfsg-8.2) unstable; urgency=low * Non-maintainer upload. diff -Nru babel-1.4.0.dfsg/debian/control babel-1.4.0.dfsg/debian/control --- babel-1.4.0.dfsg/debian/control 2013-05-26 15:29:56.0 -0400 +++ babel-1.4.0.dfsg/debian/control 2016-02-10 11:56:43.0 -0500 @@ -3,8 +3,8 @@ Priority: extra Maintainer: "Adam C. Powell, IV" <hazel...@debian.org> Standards-Version: 3.9.1 -Build-Depends: debhelper (>= 5), gfortran, libltdl-dev, libtool, - automake, autoconf, libxml2-dev, default-jdk-builddep | java-gcj-compat-dev, +Build-Depends: debhelper (>= 5), gfortran, libltdl-dev, dh-autoreconf, + libxml2-dev, default-jdk-builddep | java-gcj-compat-dev, fastjar, gcj-jdk | gjdoc, libxerces2-java, libgetopt-java, libxalan2-java, python-all-dev (>= 2.6.6-3~), python-numpy Build-Conflicts: libparsifal-dev diff -Nru babel-1.4.0.dfsg/debian/rules babel-1.4.0.dfsg/debian/rules --- babel-1.4.0.dfsg/debian/rules 2013-05-26 15:30:28.0 -0400 +++ babel-1.4.0.dfsg/debian/rules 2016-02-10 11:56:43.0 -0500 @@ -6,14 +6,7 @@ stamp-configure: dh_testdir - (cd runtime && libtoolize --force) - (cd runtime && aclocal) - (cd runtime && automake) - (cd runtime && autoconf) - libtoolize --force - aclocal - automake - autoconf + dh_autoreconf JNI_INCLUDES=-I/usr/lib/jvm/java-gcj/include \ PYTHON=python ./configure --prefix=/usr touch $@ @@ -54,6 +47,7 @@ # This is left by a quilt push/pop sequence rm -rf .pc rm -f stamp-configure stamp-build* + dh_autoreconf_clean dh_clean install: build $(PYOTHERS:%=install-python%)
Bug#755336: libexpect-php5: FTBFS: php_expect.h:33:17: fatal error: tcl.h: No such file or directory
user debian-powe...@lists.debian.org usertags 755336 + ppc64el thanks Hi. Sergei's suggestion is still applicable from what I could see. Also for ppc64el, which is failing to build from source on buildd. https://buildd.debian.org/status/fetch.php?pkg=libexpect-php5=ppc64el=0.3.1-1=1453506765 Thanks! -- Fernando Seiti Furusato IBM Linux Technology Center
Bug#805121: kumofs: FTBFS on ppc64el: ICE
Package: kumofs Followup-For: Bug #805121 Hi. I have also reported this issue on github, although there was no activity on it yet. https://github.com/etolabo/kumofs/issues/27 Please, add details if you think it is needed. Thanks. Fernando
Bug#802410: openais: FTBFS: error: corosync/coroipc_types.h: No such file or directory
Source: openais Version: 1.1.4-4.2 Followup-For: Bug #802410 It also fails on ppc64el and other architectures FWIW: https://buildd.debian.org/status/package.php?p=openais=sid This seems to be a problem with the dependency on corosync-dev. Newest version of corosync does not ship the file in question, coroipc_types.h. An easy way to fix this would be to restrict build-dep on the specific version that still has that file. The problem would be that sid repository does not seem to have the binary of the previous version available (at least for ppc64el). The patch attached ilustrates what I tried to explain above. Regards. Fernando diff -Nru openais-1.1.4/debian/changelog openais-1.1.4/debian/changelog --- openais-1.1.4/debian/changelog 2014-07-03 21:44:36.0 -0400 +++ openais-1.1.4/debian/changelog 2015-11-30 11:35:06.0 -0500 @@ -1,3 +1,11 @@ +openais (1.1.4-4.3) UNRELEASED; urgency=medium + + * Non-maintainer upload. + * Set version of libcorosync-dev and added corosync-dev package to the +latest one that contain coroipc_types.h. + + -- Fernando Seiti Furusato <ferse...@br.ibm.com> Mon, 30 Nov 2015 11:34:04 -0500 + openais (1.1.4-4.2) unstable; urgency=low * Non-maintainer upload. diff -Nru openais-1.1.4/debian/control openais-1.1.4/debian/control --- openais-1.1.4/debian/control 2014-06-06 05:56:34.0 -0400 +++ openais-1.1.4/debian/control 2015-11-30 11:33:58.0 -0500 @@ -5,7 +5,7 @@ Uploaders: Martin Loschwitz <madk...@debian.org>, Bastian Blank <wa...@debian.org>, Frederik Schüler <f...@debian.org>, Guido Günther <a...@sigxcpu.org> Standards-Version: 3.9.2 -Build-Depends: debhelper (>> 5), libcorosync-dev (>= 1.1.0), pkg-config, groff, dh-autoreconf +Build-Depends: debhelper (>> 5), libcorosync-dev (>= 1.1.0), libcorosync-dev (<= 1.4.6-1.1), corosync-dev (>= 1.1.0), corosync-dev (<= 1.4.6-1.1), pkg-config, groff, dh-autoreconf Vcs-Git: git://git.debian.org/debian-ha/openais.git Vcs-Browser: http://git.debian.org/?p=debian-ha/openais.git;a=summary
Bug#779551: (no subject)
Followup-For: Bug #779551 Source: devtodo Version: 0.1.20-6 X-Debbugs-Cc: cont...@bugs.debian.org Dear Maintainer et al, This package also ftbfs on ppc64el due to the same reason reported here and in bug #723964. So I have created a patch which fixes both, by: - adding dh-autoreconf utilization to debian/rules - adding dependency on libtool-bin to debian/control. The debdiff is attached. Regards. Fernando -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) diff -Nru devtodo-0.1.20/debian/changelog devtodo-0.1.20/debian/changelog --- devtodo-0.1.20/debian/changelog 2012-06-19 01:38:36.0 + +++ devtodo-0.1.20/debian/changelog 2015-03-17 12:27:49.0 + @@ -1,3 +1,11 @@ +devtodo (0.1.20-6ppc64el1) UNRELEASED; urgency=medium + + * debian/control: added dh-autoreconf as build-dep, removed its dependencies +and added libtool-bin to fix ftbfs. + * debian/rules: added usage of dh-autoreconf + + -- Fernando Seiti Furusato ferse...@br.ibm.com Tue, 17 Mar 2015 12:26:35 + + devtodo (0.1.20-6) unstable; urgency=low * fix SYNOPSIS spelling in manpage (Closes: #534236) diff -Nru devtodo-0.1.20/debian/control devtodo-0.1.20/debian/control --- devtodo-0.1.20/debian/control 2012-06-19 01:32:57.0 + +++ devtodo-0.1.20/debian/control 2015-03-17 12:26:01.0 + @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Ryan Niebur r...@debian.org -Build-Depends: debhelper (= 7.2), autotools-dev, libreadline-dev, libncurses-dev, bash-completion, automake, autoconf, libtool, dpkg-dev (= 1.16.1~) +Build-Depends: debhelper (= 7.2), dh-autoreconf, libreadline-dev, libncurses-dev, bash-completion, libtool-bin, dpkg-dev (= 1.16.1~) Standards-Version: 3.9.3 Vcs-Git: git://git.debian.org/git/collab-maint/devtodo.git Vcs-Browser: http://git.debian.org/?p=collab-maint/devtodo.git;a=summary diff -Nru devtodo-0.1.20/debian/rules devtodo-0.1.20/debian/rules --- devtodo-0.1.20/debian/rules 2012-06-19 01:28:47.0 + +++ devtodo-0.1.20/debian/rules 2015-03-17 12:26:20.0 + @@ -7,15 +7,13 @@ destdir=$(CURDIR)/debian/devtodo/ override_dh_auto_configure: + dh_autoreconf dh_auto_configure -- CFLAGS=$(CFLAGS) CPPFLAGS=$(CPPFLAGS) CXXFLAGS=$(CXXFLAGS) LDFLAGS=$(LDFLAGS) build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp build-stamp: - ln -sf /usr/share/misc/config.sub config.sub - ln -sf /usr/share/misc/config.guess config.guess - autoreconf dh build touch build-stamp @@ -24,6 +22,7 @@ dh_auto_build clean: + dh_autoreconf_clean dh clean install: build
Bug#723964: devtodo: FTBFS: required file './compile' not found
Source: devtodo Followup-For: Bug #723964 Hello. The package also fails to build from source due to a missing build-dep (see bug #779551). Using the same approach as Gregor on his first patch, I just added a build-dep on libtool-bin. I also removed some dependencies that are not needed, since they are dependencies of dh-autoreconf anyway. I sent the same patch to #779551. Regards. Fernando -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) diff -Nru devtodo-0.1.20/debian/changelog devtodo-0.1.20/debian/changelog --- devtodo-0.1.20/debian/changelog 2012-06-19 01:38:36.0 + +++ devtodo-0.1.20/debian/changelog 2015-03-17 12:27:49.0 + @@ -1,3 +1,11 @@ +devtodo (0.1.20-6ppc64el1) UNRELEASED; urgency=medium + + * debian/control: added dh-autoreconf as build-dep, removed its dependencies +and added libtool-bin to fix ftbfs. + * debian/rules: added usage of dh-autoreconf + + -- Fernando Seiti Furusato ferse...@br.ibm.com Tue, 17 Mar 2015 12:26:35 + + devtodo (0.1.20-6) unstable; urgency=low * fix SYNOPSIS spelling in manpage (Closes: #534236) diff -Nru devtodo-0.1.20/debian/control devtodo-0.1.20/debian/control --- devtodo-0.1.20/debian/control 2012-06-19 01:32:57.0 + +++ devtodo-0.1.20/debian/control 2015-03-17 12:26:01.0 + @@ -2,7 +2,7 @@ Section: utils Priority: optional Maintainer: Ryan Niebur r...@debian.org -Build-Depends: debhelper (= 7.2), autotools-dev, libreadline-dev, libncurses-dev, bash-completion, automake, autoconf, libtool, dpkg-dev (= 1.16.1~) +Build-Depends: debhelper (= 7.2), dh-autoreconf, libreadline-dev, libncurses-dev, bash-completion, libtool-bin, dpkg-dev (= 1.16.1~) Standards-Version: 3.9.3 Vcs-Git: git://git.debian.org/git/collab-maint/devtodo.git Vcs-Browser: http://git.debian.org/?p=collab-maint/devtodo.git;a=summary diff -Nru devtodo-0.1.20/debian/rules devtodo-0.1.20/debian/rules --- devtodo-0.1.20/debian/rules 2012-06-19 01:28:47.0 + +++ devtodo-0.1.20/debian/rules 2015-03-17 12:26:20.0 + @@ -7,15 +7,13 @@ destdir=$(CURDIR)/debian/devtodo/ override_dh_auto_configure: + dh_autoreconf dh_auto_configure -- CFLAGS=$(CFLAGS) CPPFLAGS=$(CPPFLAGS) CXXFLAGS=$(CXXFLAGS) LDFLAGS=$(LDFLAGS) build: build-arch build-indep build-arch: build-stamp build-indep: build-stamp build-stamp: - ln -sf /usr/share/misc/config.sub config.sub - ln -sf /usr/share/misc/config.guess config.guess - autoreconf dh build touch build-stamp @@ -24,6 +22,7 @@ dh_auto_build clean: + dh_autoreconf_clean dh clean install: build
Bug#723789: FTBFS: dpkg-shlibdeps: error: couldn't find library libparsifal-1.0.0.so
Source: babel Tags: patch Followup-For: Bug #723789 User: debian-powe...@lists.debian.org Usertags: ppc64el Hello sirs. Maybe it would be more practical if it used dh_autoreconf, instead of plain autoreconf command, wouldn't it? Anyway, when you set the package to run autoreconf, the Makefile.in files are re-generated, and the patch named debian/patches/banish-rpath.patch loses its effect. So the rpath comes back and the binary looks for the .so objects which were dropped in the past. Looking at the changelog in d/changelog, I see parsifal is set to use only static libs. So, in the patch below, I include a -static flag to parsifal's LDFLAGS. That way, the package builds through to the end -- although with warnings. I also included some flags to unset bool and vector when compiling some files, because those keywords were causing conflict due to macros with the same name. It would also be interesting to fix the clean target, because it is not cleaning the build tree completely. Unfortunately I was not able to do so. In conclusion, I know this is not ideal, but here is a debdiff in which: - I included the usage of dh_autoreconf (with a debian/autoreconf file, since there are more directories to be updated by autoreconf) - There are 2 files within debian/patches. One is to use the flags -Ubool and -Uvector so there is no confusion with the gcc macros. Another is to include the flag -static to Makefile.am, so Makefile.in and subsequent autotools files can be generated without having to patch Makefile.in. Please have a look and let me know if what you think. Thanks and regards. Fernando -- System Information: Debian Release: jessie/sid APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: ppc64el (ppc64le) Kernel: Linux 3.13-1-powerpc64le (SMP w/16 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: sysvinit (via /sbin/init) diff -Nru babel-1.4.0.dfsg/debian/autoreconf babel-1.4.0.dfsg/debian/autoreconf --- babel-1.4.0.dfsg/debian/autoreconf 1970-01-01 00:00:00.0 + +++ babel-1.4.0.dfsg/debian/autoreconf 2015-02-04 15:33:25.0 + @@ -0,0 +1,2 @@ +. +runtime diff -Nru babel-1.4.0.dfsg/debian/changelog babel-1.4.0.dfsg/debian/changelog --- babel-1.4.0.dfsg/debian/changelog 2013-05-26 19:33:17.0 + +++ babel-1.4.0.dfsg/debian/changelog 2015-02-04 16:11:53.0 + @@ -1,3 +1,12 @@ +babel (1.4.0.dfsg-8.2ppc64el1) UNRELEASED; urgency=medium + + * d/patches/ubool-uvector.patch: this is to circumvent a problem with some +defined macros, which cause conflict with the keywords bool and vector. + * d/patches/static.patch: using flag -static within parsifal Makefile.am as +to follow changelog entry in 1.4.0.dfsg-1 to use static lib only. + + -- Fernando Seiti Furusato ferse...@br.ibm.com Wed, 04 Feb 2015 16:07:42 + + babel (1.4.0.dfsg-8.2) unstable; urgency=low * Non-maintainer upload. diff -Nru babel-1.4.0.dfsg/debian/control babel-1.4.0.dfsg/debian/control --- babel-1.4.0.dfsg/debian/control 2013-05-26 19:29:56.0 + +++ babel-1.4.0.dfsg/debian/control 2015-02-04 16:17:15.0 + @@ -3,8 +3,8 @@ Priority: extra Maintainer: Adam C. Powell, IV hazel...@debian.org Standards-Version: 3.9.1 -Build-Depends: debhelper (= 5), gfortran, libltdl-dev, libtool, - automake, autoconf, libxml2-dev, default-jdk-builddep | java-gcj-compat-dev, +Build-Depends: debhelper (= 5), gfortran, libltdl-dev, dh-autoreconf, + libxml2-dev, default-jdk-builddep | java-gcj-compat-dev, fastjar, gcj-jdk | gjdoc, libxerces2-java, libgetopt-java, libxalan2-java, python-all-dev (= 2.6.6-3~), python-numpy Build-Conflicts: libparsifal-dev diff -Nru babel-1.4.0.dfsg/debian/patches/series babel-1.4.0.dfsg/debian/patches/series --- babel-1.4.0.dfsg/debian/patches/series 2010-01-31 20:48:41.0 + +++ babel-1.4.0.dfsg/debian/patches/series 2015-02-04 16:04:08.0 + @@ -7,3 +7,5 @@ no-manuals.patch sidlx-pointer.patch sh4-support.patch +ubool-uvector.patch +static.patch diff -Nru babel-1.4.0.dfsg/debian/patches/static.patch babel-1.4.0.dfsg/debian/patches/static.patch --- babel-1.4.0.dfsg/debian/patches/static.patch 1970-01-01 00:00:00.0 + +++ babel-1.4.0.dfsg/debian/patches/static.patch 2015-02-04 16:13:31.0 + @@ -0,0 +1,13 @@ +This patch sets -static flag to parsifal linker since the package no longer +provides parsifal shared libs. +--- a/runtime/libparsifal/src/Makefile.am b/runtime/libparsifal/src/Makefile.am +@@ -12,7 +12,7 @@ + libparsifal_la_SOURCES = $(CSOURCES) + + ## RELEASE gets AC_SUBST'ed value from configure.ac: +-libparsifal_la_LDFLAGS = -no-undefined -release @RELEASE@ ++libparsifal_la_LDFLAGS = -no-undefined -release -static @RELEASE@ + + ## target include directory (/usr/include by default): + library_includedir=$(includedir)/libparsifal diff -Nru babel-1.4.0.dfsg/debian/patches/ubool
