Bug#801489: htmlcxx: FTBFS on ppc64: Update symbols to build on ppc64
Source: htmlcxx Version: 0.85-3.4 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: https://buildd.debian.org/status/package.php?p=htmlcxx=sid https://buildd.debian.org/status/fetch.php?pkg=htmlcxx=ppc64=0.85-3.4=1442123463 Please update symbols of debian/libcss-parser-pp0v5.symbols. Here is a patch attached that was checked building succeeded. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd htmlcxx-0.85.orig/debian/libcss-parser-pp0v5.symbols htmlcxx-0.85/debian/libcss-parser-pp0v5.symbols --- htmlcxx-0.85.orig/debian/libcss-parser-pp0v5.symbols 2015-08-16 22:43:07.0 +0900 +++ htmlcxx-0.85/debian/libcss-parser-pp0v5.symbols 2015-10-11 15:46:17.671766720 +0900 @@ -31,12 +31,12 @@ (optional)_ZNSt6vectorIN7htmlcxx3CSS6Parser8SelectorESaIS3_EED1Ev@Base 0.83 (optional)_ZNSt6vectorIN7htmlcxx3CSS6Parser8SelectorESaIS3_EED2Ev@Base 0.83 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7htmlcxx3CSS6Parser9AttributeEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE24_M_get_insert_unique_posERS7_@Base 0.85 - (arch-bits=64|arch=!s390x)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7htmlcxx3CSS6Parser9AttributeEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISC_ERS7_@Base 0.85 + (arch-bits=64|arch=!ppc64 !s390x)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7htmlcxx3CSS6Parser9AttributeEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISC_ERS7_@Base 0.85 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7htmlcxx3CSS6Parser9AttributeEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE7_M_copyINSI_11_Alloc_nodeEEEPSt13_Rb_tree_nodeISC_EPKSM_SN_RT_@Base 0.85 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_N7htmlcxx3CSS6Parser9AttributeEESt10_Select1stISC_ESt4lessIS5_ESaISC_EE8_M_eraseEPSt13_Rb_tree_nodeISC_E@Base 0.85 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE24_M_get_insert_unique_posERS7_@Base 0.85 - (arch-bits=64|arch=!s390x)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 0.85 + (arch-bits=64|arch=!ppc64 !s390x)_ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorIS8_ERS7_@Base 0.85 _ZNSt8_Rb_treeINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEESt4pairIKS5_S5_ESt10_Select1stIS8_ESt4lessIS5_ESaIS8_EE8_M_eraseEPSt13_Rb_tree_nodeIS8_E@Base 0.85 _ZNSt8_Rb_treeISt6vectorIN7htmlcxx3CSS6Parser8SelectorESaIS4_EESt4pairIKS6_St3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS3_9AttributeESt4lessISF_ESaIS7_IKSF_SG_St10_Select1stISN_ESH_IS6_ESaISN_EE24_M_get_insert_unique_posERS8_@Base 0.85 - (arch-bits=64|arch=!s390x)_ZNSt8_Rb_treeISt6vectorIN7htmlcxx3CSS6Parser8SelectorESaIS4_EESt4pairIKS6_St3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS3_9AttributeESt4lessISF_ESaIS7_IKSF_SG_St10_Select1stISN_ESH_IS6_ESaISN_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISN_ERS8_@Base 0.85 + (arch-bits=64|arch=!ppc64 !s390x)_ZNSt8_Rb_treeISt6vectorIN7htmlcxx3CSS6Parser8SelectorESaIS4_EESt4pairIKS6_St3mapINSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEENS3_9AttributeESt4lessISF_ESaIS7_IKSF_SG_St10_Select1stISN_ESH_IS6_ESaISN_EE29_M_get_insert_hint_unique_posESt23_Rb_tree_const_iteratorISN_ERS8_@Base 0.85 free_rulesets@Base 0.83
Bug#801445: liblog4ada: FTBFS on ppc64: Update symbols to build on ppc64
Source: liblog4ada Version: liblog4ada_1.2-5 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: https://buildd.debian.org/status/package.php?p=liblog4ada=sid https://buildd.debian.org/status/fetch.php?pkg=liblog4ada=ppc64=1.2-5=1442122723 Please add files of debian/liblog4ada1.symbols.ppc64. Here is a patch attached that was checked building succeeded. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd liblog4ada-1.2.orig/debian/liblog4ada1.symbols.ppc64 liblog4ada-1.2/debian/liblog4ada1.symbols.ppc64 --- liblog4ada-1.2.orig/debian/liblog4ada1.symbols.ppc64 1970-01-01 09:00:00.0 +0900 +++ liblog4ada-1.2/debian/liblog4ada1.symbols.ppc64 2015-10-10 17:04:40.322944137 +0900 @@ -0,0 +1 @@ +#include "liblog4ada1.symbols.ppc64el"
Bug#801423: mono: FTBFS on ppc64: Update symbols to build on ppc64
Source: mono Version: 4.0.4.1+dfsg-1 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: https://buildd.debian.org/status/package.php?p=mono=experimental https://buildd.debian.org/status/fetch.php?pkg=mono=ppc64=4.0.4.1%2Bdfsg-1=1442131975 Please add files of debian/libmonoboehm-2.0-1.symbols.ppc64 and debian/libmonosgen-2.0-1.symbols.ppc64. Here is a patch attached that was checked building succeeded. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd mono-4.0.4.1+dfsg.orig/debian/libmonoboehm-2.0-1.symbols.ppc64 mono-4.0.4.1+dfsg/debian/libmonoboehm-2.0-1.symbols.ppc64 --- mono-4.0.4.1+dfsg.orig/debian/libmonoboehm-2.0-1.symbols.ppc64 1970-01-01 09:00:00.0 +0900 +++ mono-4.0.4.1+dfsg/debian/libmonoboehm-2.0-1.symbols.ppc64 2015-09-07 19:21:41.0 +0900 @@ -0,0 +1 @@ +#include "libmonoboehm-2.0-1.symbols.powerpc" diff -Nurd mono-4.0.4.1+dfsg.orig/debian/libmonosgen-2.0-1.symbols.ppc64 mono-4.0.4.1+dfsg/debian/libmonosgen-2.0-1.symbols.ppc64 --- mono-4.0.4.1+dfsg.orig/debian/libmonosgen-2.0-1.symbols.ppc64 1970-01-01 09:00:00.0 +0900 +++ mono-4.0.4.1+dfsg/debian/libmonosgen-2.0-1.symbols.ppc64 2015-09-07 19:21:41.0 +0900 @@ -0,0 +1 @@ +#include "libmonosgen-2.0-1.symbols.powerpc"
Bug#800823: hdf5: FTBFS on ppc64: Update symbols to build on ppc64
Source: hdf5 Version: 1.8.15-patch1+docs-4 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: https://buildd.debian.org/status/package.php?p=hdf5=sid Please update symbols of debian/libhdf5-10.symbols, debian/libhdf5-mpich-10.symbols, and debian/libhdf5-openmpi-10.symbols. Here is a patch attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-10.symbols hdf5-1.8.15-patch1+docs/debian/libhdf5-10.symbols --- hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-10.symbols 2015-08-15 06:33:48.0 +0900 +++ hdf5-1.8.15-patch1+docs/debian/libhdf5-10.symbols 2015-10-04 00:06:00.809918409 +0900 @@ -2076,19 +2076,19 @@ H5T__conv_ldouble_double@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_float@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_int@HDF5_SERIAL_1.8.7 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_llong@HDF5_SERIAL_1.8.7 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_llong@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_long@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_schar@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_short@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_uchar@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_uint@HDF5_SERIAL_1.8.7 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_ullong@HDF5_SERIAL_1.8.7 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_ullong@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_ulong@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_ldouble_ushort@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_double@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_float@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_int@HDF5_SERIAL_1.8.7 1.8.13 - (arch=!powerpc)H5T__conv_llong_ldouble@HDF5_SERIAL_1.8.7 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_llong_ldouble@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_long@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_schar@HDF5_SERIAL_1.8.7 1.8.13 H5T__conv_llong_short@HDF5_SERIAL_1.8.7 1.8.13 diff -Nurd hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-mpich-10.symbols hdf5-1.8.15-patch1+docs/debian/libhdf5-mpich-10.symbols --- hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-mpich-10.symbols 2015-08-15 06:33:48.0 +0900 +++ hdf5-1.8.15-patch1+docs/debian/libhdf5-mpich-10.symbols 2015-10-04 00:07:46.802443997 +0900 @@ -2117,19 +2117,19 @@ H5T__conv_ldouble_double@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_float@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_int@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_llong@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_llong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_long@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_schar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_short@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_uchar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_uint@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_ullong@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_ullong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_ulong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_ushort@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_double@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_float@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_int@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_llong_ldouble@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_llong_ldouble@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_long@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_schar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_short@HDF5_MPI_1.8.10 1.8.13 diff -Nurd hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-openmpi-10.symbols hdf5-1.8.15-patch1+docs/debian/libhdf5-openmpi-10.symbols --- hdf5-1.8.15-patch1+docs.orig/debian/libhdf5-openmpi-10.symbols 2015-08-15 06:33:48.0 +0900 +++ hdf5-1.8.15-patch1+docs/debian/libhdf5-openmpi-10.symbols 2015-10-04 00:04:26.221449370 +0900 @@ -2117,19 +2117,19 @@ H5T__conv_ldouble_double@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_float@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_int@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_llong@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_llong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_long@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_schar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_short@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_uchar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_uint@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_ldouble_ullong@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_ldouble_ullong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_ulong@HDF5_MPI_1.8.10 1.8.13 H5T__conv_ldouble_ushort@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_double@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_float@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_int@HDF5_MPI_1.8.10 1.8.13 - (arch=!powerpc)H5T__conv_llong_ldouble@HDF5_MPI_1.8.10 1.8.13 + (arch=!powerpc !ppc64)H5T__conv_llong_ldouble@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_long@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_schar@HDF5_MPI_1.8.10 1.8.13 H5T__conv_llong_short
Bug#791623: haskell-path-pieces FTBFS on debian-ports arches; missing build-depends.
Inspecting the ghc binary package it looks like alpha and hppa have /usr/bin/ghci but ppc64 does not. ppc64 also has /usr/bin/ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#787621: build/profiles/basic.make:92: recipe for target 'build/deps/basic-profile-check.exe' failed
Hi all, Sorry, I have only a build-node machine, so, my machine cannot be opened. I tried to build mono_4.0.1.44-0xamarin1 on schroot of sbuild, but building was failed. Its build-log is attached, in summary, building seems to failure by a same reason of 3.2.8+dfsg-10, as follows: cd /«PKGBUILDDIR»/mcs /usr/bin/make --no-print-directory -s NO_DIR_CHECK=1 PROFILES='binary_reference_assemblies net_4_5 xbuild_12 xbuild_14 ' CC='gcc' all-profiles mkdir -p -- build/deps build/profiles/basic.make:93: recipe for target 'build/deps/basic-profile-check.exe' failed make[7]: *** [build/deps/basic-profile-check.exe] Error 1 *** The compiler 'false' doesn't appear to be usable. *** Trying the 'monolite' directory. Stacktrace: Native stacktrace: /«PKGBUILDDIR»/mono/mini/mono() [0x100c3acc] /«PKGBUILDDIR»/mono/mini/mono() [0x101087a0] /«PKGBUILDDIR»/mono/mini/mono() [0x100334e4] linux-vdso64.so.1(__kernel_sigtramp_rt64+0) [0x3fff99c10478] [0x4e800020] [0x3fff97c98998] [0x3fff97c988e4] [0x3fff97c96bd0] [0x3fff97c966e4] [0x3fff97c95cd0] [0x3fff97c95bb0] [0x3fff97c9597c] [0x3fff97c8dbdc] [0x3fff97c8ccd4] [0x3fff97c8b774] [0x3fff97c8b198] [0x3fff97c23724] [0x3fff97bf3bc0] [0x3fff97bf4430] /«PKGBUILDDIR»/mono/mini/mono() [0x10036044] /«PKGBUILDDIR»/mono/mini/mono(mono_runtime_invoke-0x1b9f5c) [0x101e4864] /«PKGBUILDDIR»/mono/mini/mono(mono_runtime_exec_main-0x1b6de8) [0x101e7e10] /«PKGBUILDDIR»/mono/mini/mono(mono_jit_exec-0x2fd6d0) [0x1008e9d0] /«PKGBUILDDIR»/mono/mini/mono(mono_main-0x2fbef8) [0x100901d8] /«PKGBUILDDIR»/mono/mini/mono() [0x10026574] /lib/powerpc64-linux-gnu/libc.so.6(+0x47d6c) [0x3fff99927d6c] /lib/powerpc64-linux-gnu/libc.so.6(__libc_start_main-0x16d92c) [0x3fff99927f94] Debug info from gdb: = Got a SIGSEGV while executing native code. This usually indicates a fatal error in the mono runtime or one of the native libraries used by your application. = Aborted -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC Jo Shields wrote: Is there a big-endian ppc64 porterbox I can access yet? If not, give http://download.mono-project.com/repo/debian/pool/main/m/mono/mono_4.0.1.44-0xamarin1.dsc a shot Supposedly partch offers ppc64 build environments, but all the chroots in schroot on there are powerpc, not ppc64. On 03/06/15 13:09, Mathieu Malaterre wrote: Package: mono-devel Version: 3.2.8+dfsg-10 Severity: normal Usertags: ppc64 mono currently fails to build on ppc64: http://buildd.debian-ports.org/status/fetch.php?pkg=monoarch=ppc64ver=3.2.8%2Bdfsg-10stamp=1430613523 with the following error: cd /«BUILDDIR»/mono-3.2.8+dfsg/mcs /usr/bin/make --no-print-directory -s NO_DIR_CHECK=1 PROFILES='net_2_0 net_3_5 net_4_0 net_4_5 xbuild_12 ' CC='gcc' all-profiles mkdir -p -- build/deps make[7]: *** [build/deps/basic-profile-check.exe] Error 1 build/profiles/basic.make:92: recipe for target 'build/deps/basic-profile-check.exe' failed *** The compiler 'false' doesn't appear to be usable. *** Trying the 'monolite' directory. Stacktrace: Native stacktrace: /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono() [0x100c222c] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono() [0x1010505c] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono() [0x10029324] linux-vdso64.so.1(__kernel_sigtramp_rt64+0) [0x3fffaeeb0478] [0x4e800020] [0x3fffacf00154] [0x3fffacf06f4c] [0x3fffacef32b8] [0x3fffacef3c94] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono() [0x1002bb80] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono(mono_runtime_invoke-0x1d81d4) [0x101e59c4] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono(mono_runtime_exec_main-0x1d4e40) [0x101e9160] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono(mono_jit_exec-0x31df58) [0x1008dc10] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono(mono_main-0x31c794) [0x1008f404] /«BUILDDIR»/mono-3.2.8+dfsg/mono/mini/mono() [0x1001bd54] /lib/powerpc64-linux-gnu/libc.so.6(+0x47d6c) [0x3fffaebc7d6c] /lib/powerpc64-linux-gnu/libc.so.6(__libc_start_main-0x16d92c) [0x3fffaebc7f94] Debug info from gdb: mono_4.0.1.44-0xamarin1_ppc64-20150603-2147.build.gz Description: application/gzip signature.asc Description: OpenPGP digital signature
Bug#758843: haskell-platform: New upstream version
Source: haskell-platform Version: 2013.2.0.0.debian12 Severity: wishlist New upstream version 0.2.6 was released. http://www.haskell.org/platform/ http://www.haskell.org/platform/download/2014.2.0.0/haskell-platform-2014.2.0.0-srcdist.tar.gz Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#755157: gst-plugins-bad1.0: FTBFS: unsatisfiable build-dependency: libbluetooth-dev ( 5)
Source: gst-plugins-bad1.0 Version: 1.2.4-1 Severity: serious Justification: FTBFS libbluetooth-dev is provided as ver. 5.21-1 on sid, so unsatisfiable build-dependency libbluetooth-dev ( 5). Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#754516: libverto: New upstream version
Source: libverto Version: 0.2.4-1 Severity: wishlist New upstream version 0.2.6 was released. https://fedorahosted.org/libverto/ https://fedorahosted.org/releases/l/i/libverto/libverto-0.2.6.tar.gz Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#747151: linux-tools: FTBFS: __u32 and __u64 shoud be used instead of u32 and u64
Source: linux-tools Version: 3.14-1 Severity: important Tags: patch upstream Usertags: ppc64 alpha FTBFS on ppc64 and alpha of linux-tools is brought by using u32 and u64. http://buildd.debian-ports.org/status/package.php?p=linux-toolssuite=sid http://buildd.debian-ports.org/status/fetch.php?pkg=linux-toolsarch=ppc64ver=3.14-1stamp=1399098596 http://buildd.debian-ports.org/status/fetch.php?pkg=linux-toolsarch=alphaver=3.14-1stamp=1398794797 I think that __u32 and __u64 should be used in kernel headers instead of u32 and u64. Here is a patch and buildlog attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd linux-tools-3.14.orig/include/linux/types.h linux-tools-3.14/include/linux/types.h --- linux-tools-3.14.orig/include/linux/types.h 2014-03-31 12:40:15.0 +0900 +++ linux-tools-3.14/include/linux/types.h 2014-05-06 09:02:25.0 +0900 @@ -127,8 +127,8 @@ * blkcnt_t is the type of the inode's block count. */ #ifdef CONFIG_LBDAF -typedef u64 sector_t; -typedef u64 blkcnt_t; +typedef __u64 sector_t; +typedef __u64 blkcnt_t; #else typedef unsigned long sector_t; typedef unsigned long blkcnt_t; @@ -143,9 +143,9 @@ #endif #ifdef CONFIG_ARCH_DMA_ADDR_T_64BIT -typedef u64 dma_addr_t; +typedef __u64 dma_addr_t; #else -typedef u32 dma_addr_t; +typedef __u32 dma_addr_t; #endif /* dma_addr_t */ #ifdef __CHECKER__ @@ -159,9 +159,9 @@ typedef unsigned __bitwise__ oom_flags_t; #ifdef CONFIG_PHYS_ADDR_T_64BIT -typedef u64 phys_addr_t; +typedef __u64 phys_addr_t; #else -typedef u32 phys_addr_t; +typedef __u32 phys_addr_t; #endif typedef phys_addr_t resource_size_t; linux-tools_3.14-1_ppc64.build.xz Description: application/xz
Bug#747157: libunwind: FTBFS on ppc64: Please use /usr/lib instead of /usr/lib64
Source: libunwind
Version: 1.1-2.2
Severity: important
Tags: patch
Usertags: ppc64
libunwind fails to build on ppc64.
http://buildd.debian-ports.org/status/package.php?p=libunwindsuite=sid
http://buildd.debian-ports.org/status/fetch.php?pkg=libunwindarch=ppc64ver=1.1-2.2stamp=1394608509
Please use /usr/lib instead of /usr/lib64 on Debian.
Here is a patch and a buildlog attached.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd libunwind-1.1.orig/configure.ac libunwind-1.1/configure.ac
--- libunwind-1.1.orig/configure.ac 2014-05-06 11:25:17.0 +0900
+++ libunwind-1.1/configure.ac 2014-05-06 11:41:35.0 +0900
@@ -164,12 +164,6 @@
AM_CONDITIONAL(USE_DWARF, [test x$use_dwarf = xyes])
AC_MSG_RESULT([$use_dwarf])
-if test x$target_arch = xppc64; then
-libdir='${exec_prefix}/lib64'
-AC_MSG_NOTICE([PowerPC64 detected, lib will be installed ${libdir}]);
-AC_SUBST([libdir])
-fi
-
AC_MSG_CHECKING([whether to restrict build to remote support])
if test x$target_arch != x$host_arch; then
CPPFLAGS=${CPPFLAGS} -DUNW_REMOTE_ONLY
libunwind_1.1-2.2_ppc64.build.xz
Description: application/xz
Bug#743976: php5-json: Missing package dependencies prevent package removal
Control: reopen -1 I think this bug is not fixed, because php5-json real package is preferentially installed than virtual package provided by php5-common. I think that this bug is not solved until php5-json real package is removed form repository, or php5-common don't depend to php5-json. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743976: [Pkg-php-pecl] Bug#743976: php5-json: Missing package dependencies prevent package removal
Hmm, I may be misled by description of php5-json's packages.debian.org page. https://packages.debian.org/en/sid/php5-json Packages providing php5-json php5-common Common files for packages built from the php5 source It is right that php5-common doesn't provide php5-json according to apt-cache show php5-common. Ondřej Surý wrote: There's no virtual php5-json provided by php5-common, there's only the real one. O. On Sat, Apr 19, 2014, at 15:17, Hiroyuki Yamamoto wrote: Control: reopen -1 I think this bug is not fixed, because php5-json real package is preferentially installed than virtual package provided by php5-common. I think that this bug is not solved until php5-json real package is removed form repository, or php5-common don't depend to php5-json. -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#745241: liboil: FTBFS on ppc64: OIL: ERROR liboiltest.c 405: oil_test_check_impl(): function merge_linear_argb_powerpc in class merge_linear_argb failed check (3.64226e+10 0) || (outside=0)
Source: liboil
Version: 0.3.17-2
Severity: important
Tags: patch
Usertags: ppc64
FTBFS on ppc64, as follows:
http://buildd.debian-ports.org/status/package.php?p=liboilsuite=sid
http://buildd.debian-ports.org/status/fetch.php?pkg=liboilarch=ppc64ver=0.3.17-2stamp=1394609603
Here is a patch attached.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd liboil-0.3.17.orig/liboil/powerpc/copy.c liboil-0.3.17/liboil/powerpc/copy.c
--- liboil-0.3.17.orig/liboil/powerpc/copy.c 2007-11-16 11:53:47.0 +0900
+++ liboil-0.3.17/liboil/powerpc/copy.c 2014-04-20 01:01:53.0 +0900
@@ -61,7 +61,8 @@
add %1, %1, r11\n
addi %1, %1, -16\n
: +b (dest), +b (src)
-: r (n/16));
+: r (n/16)
+: r11, memory);
} else {
asm volatile (
mtctr %2\n
@@ -74,7 +75,8 @@
add %0, %0, r11\n
add %1, %1, r11\n
: +b (dest), +b (src)
-: r (n/16));
+: r (n/16)
+: r11, memory);
}
}
@@ -131,7 +133,8 @@
add %1, %1, r11\n
addi %1, %1, -16\n
: +b (dest), +b (src)
- : r (n/64));
+ : r (n/64)
+ : r11, memory);
}
n = 0x3f;
diff -Nurd liboil-0.3.17.orig/liboil/powerpc/resample.c liboil-0.3.17/liboil/powerpc/resample.c
--- liboil-0.3.17.orig/liboil/powerpc/resample.c 2007-11-16 11:53:47.0 +0900
+++ liboil-0.3.17/liboil/powerpc/resample.c 2014-04-20 01:01:53.0 +0900
@@ -86,7 +86,8 @@
vpkuhus v0, v0, v0\n
stvx v0, 0, %0\n
:
- : b (atmp));
+ : b (atmp)
+ : r11, memory);
dest[i] = atmp[0];
if (i+1n) dest[i+1] = atmp[1];
diff -Nurd liboil-0.3.17.orig/liboil/powerpc/splat.c liboil-0.3.17/liboil/powerpc/splat.c
--- liboil-0.3.17.orig/liboil/powerpc/splat.c 2007-11-16 11:53:47.0 +0900
+++ liboil-0.3.17/liboil/powerpc/splat.c 2014-04-20 01:01:53.0 +0900
@@ -57,7 +57,8 @@
bdnz+ 1b\n
add %0, %0, r11\n
: +b (dest), +b (src)
-: r (n/16));
+: r (n/16)
+: r11, memory);
}
n = 0xf;
@@ -96,7 +97,8 @@
bdnz+ 1b\n
add %0, %0, r11\n
: +b (dest), +b (src)
-: r (n/64));
+: r (n/64)
+: r11, memory);
}
n = 0x3f;
@@ -131,7 +133,8 @@
bdnz+ 1b\n
add %0, %0, r11\n
: +b (dest), +b (src)
-: r (n/4));
+: r (n/4)
+: r11, memory);
}
n = 0x3;
Bug#743775: ctpp2: FTBFS on ppc64: Update symbols to build on ppc64
Vasudev Kamath wrote: Control: tag -1 +pending Hiroyuki Yamamoto yama1...@gmail.com writes: Source: ctpp2 Version: 2.8.3-8 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: http://buildd.debian-ports.org/status/package.php?p=ctpp2suite=sid http://buildd.debian-ports.org/status/fetch.php?pkg=ctpp2arch=ppc64ver=2.8.3-8stamp=1390353104 Please update symbols of debian/libqt4pas5.symbols. Here is a patch attached. I hope you mean libctpp2-2.symbols file. I've already added this patch and will upload it soon. Oops! Sorry, I mistook fixing filename for ctpp2 from one for libqt4pas... Thanks for fixing and uploading. Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#743775: ctpp2: FTBFS on ppc64: Update symbols to build on ppc64
Source: ctpp2 Version: 2.8.3-8 Severity: important Tags: patch Usertags: ppc64 FTBFS on ppc64, as follows: http://buildd.debian-ports.org/status/package.php?p=ctpp2suite=sid http://buildd.debian-ports.org/status/fetch.php?pkg=ctpp2arch=ppc64ver=2.8.3-8stamp=1390353104 Please update symbols of debian/libqt4pas5.symbols. Here is a patch attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd ctpp2-2.8.3.orig/debian/libctpp2-2.symbols ctpp2-2.8.3/debian/libctpp2-2.symbols --- ctpp2-2.8.3.orig/debian/libctpp2-2.symbols 2014-01-21 02:21:50.0 +0900 +++ ctpp2-2.8.3/debian/libctpp2-2.symbols 2014-03-23 21:18:06.0 +0900 @@ -780,7 +780,7 @@ _ZN4CTPP6FnSizeD1Ev@Base 2.8.3 _ZN4CTPP6FnSizeD2Ev@Base 2.8.3 (arch=amd64 kfreebsd-amd64 powerpc powerpcspe s390 s390x)_ZN4CTPP6Logger10LogMessageEjPKcP13__va_list_tag@Base 2.8.3 - (arch=hurd-i386 i386 kfreebsd-i386)_ZN4CTPP6Logger10LogMessageEjPKcPc@Base 2.8.3 + (arch=hurd-i386 i386 kfreebsd-i386 ppc64)_ZN4CTPP6Logger10LogMessageEjPKcPc@Base 2.8.3 (arch=ia64 mips mipsel sparc mips64 mips64el)_ZN4CTPP6Logger10LogMessageEjPKcPv@Base 2.8.3 (arch=armel armhf)_ZN4CTPP6Logger10LogMessageEjPKcSt9__va_list@Base 2.8.3 _ZN4CTPP6Logger10LogMessageEjPKcz@Base 2.8.3 @@ -955,17 +955,17 @@ _ZN4CTPPmiERKdRKNS_3CDTE@Base 2.8.3 _ZN4CTPPmiERKiRKNS_3CDTE@Base 2.8.3 _ZN4CTPPmiERKjRKNS_3CDTE@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZN4CTPPmiERKlRKNS_3CDTE@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZN4CTPPmiERKmRKNS_3CDTE@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZN4CTPPmiERKxRKNS_3CDTE@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZN4CTPPmiERKyRKNS_3CDTE@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZN4CTPPmiERKlRKNS_3CDTE@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZN4CTPPmiERKmRKNS_3CDTE@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZN4CTPPmiERKxRKNS_3CDTE@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZN4CTPPmiERKyRKNS_3CDTE@Base 2.8.3 _ZN4CTPPmlERKdRKNS_3CDTE@Base 2.8.3 _ZN4CTPPmlERKiRKNS_3CDTE@Base 2.8.3 _ZN4CTPPmlERKjRKNS_3CDTE@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZN4CTPPmlERKlRKNS_3CDTE@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZN4CTPPmlERKmRKNS_3CDTE@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZN4CTPPmlERKxRKNS_3CDTE@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZN4CTPPmlERKyRKNS_3CDTE@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZN4CTPPmlERKlRKNS_3CDTE@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZN4CTPPmlERKmRKNS_3CDTE@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZN4CTPPmlERKxRKNS_3CDTE@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZN4CTPPmlERKyRKNS_3CDTE@Base 2.8.3 _ZN4CTPPplERKdRKNS_3CDTE@Base 2.8.3 _ZN4CTPPplERKiRKNS_3CDTE@Base 2.8.3 _ZN4CTPPplERKjRKNS_3CDTE@Base 2.8.3 @@ -1213,18 +1213,18 @@ _ZNK4CTPP3CDTmiEd@Base 2.8.3 _ZNK4CTPP3CDTmiEi@Base 2.8.3 _ZNK4CTPP3CDTmiEj@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZNK4CTPP3CDTmiEl@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZNK4CTPP3CDTmiEm@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmiEx@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmiEy@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZNK4CTPP3CDTmiEl@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZNK4CTPP3CDTmiEm@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmiEx@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmiEy@Base 2.8.3 _ZNK4CTPP3CDTmlERKS0_@Base 2.8.3 _ZNK4CTPP3CDTmlEd@Base 2.8.3 _ZNK4CTPP3CDTmlEi@Base 2.8.3 _ZNK4CTPP3CDTmlEj@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZNK4CTPP3CDTmlEl@Base 2.8.3 - (arch=amd64 ia64 kfreebsd-amd64 s390x mips64 mips64el)_ZNK4CTPP3CDTmlEm@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmlEx@Base 2.8.3 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmlEy@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZNK4CTPP3CDTmlEl@Base 2.8.3 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x mips64 mips64el)_ZNK4CTPP3CDTmlEm@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmlEx@Base 2.8.3 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x !mips64 !mips64el)_ZNK4CTPP3CDTmlEy@Base 2.8.3 _ZNK4CTPP3CDTneEPKc@Base 2.8.3 _ZNK4CTPP3CDTneERKS0_@Base 2.8.3
Bug#743761: libqt4pas: FTBFS on ppc64: Update symbols to build on ppc64
Source: libqt4pas
Version: 2.5-10
Severity: important
Tags: patch
Usertags: ppc64
FTBFS on ppc64, as follows:
http://buildd.debian-ports.org/status/package.php?p=libqt4passuite=sid
http://buildd.debian-ports.org/status/fetch.php?pkg=libqt4pasarch=ppc64ver=2.5-10stamp=1387329354
Please update symbols of debian/libqt4pas5.symbols.
Here is a patch attached.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd libqt4pas-2.5.orig/debian/libqt4pas5.symbols libqt4pas-2.5/debian/libqt4pas5.symbols
--- libqt4pas-2.5.orig/debian/libqt4pas5.symbols 2013-06-25 05:19:02.0 +0900
+++ libqt4pas-2.5/debian/libqt4pas5.symbols 2014-03-23 20:52:25.0 +0900
@@ -7733,23 +7733,24 @@
(optional=templinst)_Z30copyPtrIntArrayToQListTemplateIP7QActionEvPvR5QListIT_E@Base 2.4
(optional=templinst)_Z30copyPtrIntArrayToQListTemplateIiEvPvR5QListIT_E@Base 2.4
#MISSING: 2.5# (optional=templinst|subst|arch=!amd64)_Z30copyPtrIntArrayToQListTemplateI{qreal}EvPvR5QListIT_E@Base 2.4
+ (optional=templinst|subst|arch=ppc64)_Z30copyPtrIntArrayToQListTemplateI{qreal}EvPvR5QListIT_E@Base 2.4
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIN13QFontDatabase13WritingSystemEEvR5QListIT_EPv@Base 2.4
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIN8QPrinter8PageSizeEEvR5QListIT_EPv@Base 2.4
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP10QTextFrameEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP11QDockWidgetEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP10QTextFrameEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP11QDockWidgetEvR5QListIT_EPv@Base 2.5
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIP13QGraphicsItemEvR5QListIT_EPv@Base 2.4
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP13QGraphicsViewEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP13QMdiSubWindowEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP13QGraphicsViewEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP13QMdiSubWindowEvR5QListIT_EPv@Base 2.5
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIP13QStandardItemEvR5QListIT_EPv@Base 2.4
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP15QAbstractButtonEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP15QGraphicsWidgetEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP15QAbstractButtonEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP15QGraphicsWidgetEvR5QListIT_EPv@Base 2.5
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIP15QListWidgetItemEvR5QListIT_EPv@Base 2.4
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIP15QTreeWidgetItemEvR5QListIT_EPv@Base 2.4
(optional=templinst)_Z30copyQListTemplateToPtrIntArrayIP16QTableWidgetItemEvR5QListIT_EPv@Base 2.4
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP7QActionEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP7QObjectEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP7QWidgetEvR5QListIT_EPv@Base 2.5
- (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386)_Z30copyQListTemplateToPtrIntArrayIP9QWebFrameEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP7QActionEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP7QObjectEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP7QWidgetEvR5QListIT_EPv@Base 2.5
+ (arch=amd64 armel armhf hurd-i386 i386 kfreebsd-amd64 kfreebsd-i386 ppc64)_Z30copyQListTemplateToPtrIntArrayIP9QWebFrameEvR5QListIT_EPv@Base 2.5
(arch=!armel !armhf !ia64 !s390x)_Z30copyQListTemplateToPtrIntArrayIdEvR5QListIT_EPv@Base 2.5
(optional=templinst|arch=armel armhf)_Z30copyQListTemplateToPtrIntArrayIfEvR5QListIT_EPv@Base 2.5
(optional=templinst
Bug#736344: libffi: FTBFS on ppc64: symbols update needed
Control: reopen -1 Control: found -1 3.1~rc1+r3.0.13-12 Because debian/libffi6.symbols.ppc64 was reverted at changing from ver. 3.1~rc1-2 to ver. 3.1~rc1+r3.0.13-12, this bug recurs. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#724469: FTBFS on all big-endian architectures
Lennart Sorensen wrote: On Sat, Mar 22, 2014 at 11:53:23AM +0100, intrigeri wrote: intrigeri wrote (20 Jan 2014 17:58:03 GMT) : https://rt.cpan.org/Ticket/Display.html?id=89552 Sure. Debian porters, I'll let you subscribe to the RT ticket, and hopefully take care of this porting problem. I'd like to see this RC bug fixed eventually, and I still hope this can be done without dropping support for too many architectures in this package. AFAICT the latest patch proposed by upstream on February 9 [1] has been tested on mips only. My understanding is that upstream has been waiting for more test results since then. Can anyone please test this on other big-endian architectures? It would good if we could at least fix this for the 32-bit ones. [1] https://rt.cpan.org/Ticket/Attachment/1324475/702426/0001-Fix-return-value-handling-on-big-endian-architecture.patch Patch works for powerpc and someone else already reported it working for powerpcspe. As expected it does NOT work on ppc64. I am not currently awake enough to try and figure out why. Since mips was already tested with the patch originally, that probably just leaves sparc and s390 to test (I can't tell if s390 tested it or not, only that s390x does not work yet due to being 64bit). On ppc64, failing to build the source package patched was confirmed. -- make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_test -a make[1]: Entering directory `/«PKGBUILDDIR»' LD_LIBRARY_PATH=:build PERL_DL_NONLAZY=1 /usr/bin/perl -MExtUtils::Command::MM -e test_harness(0, 'blib/lib', 'blib/arch') t/*.t t/00-basic-types.t ok t/arg-checks.t ok # Failed test at t/arrays.t line 14. # got: '0' # expected: '6' t/arrays.t Failed 28/29 subtests t/boxed.t . ok t/cairo-integration.t . ok # Failed test at t/callbacks.t line 14. # got: '-40706304' # expected: '23' # Failed test at t/callbacks.t line 16. # got: '7395392' # expected: '23' # Failed test at t/callbacks.t line 17. # got: '7395392' # expected: '23' # Failed test at t/callbacks.t line 18. # got: '-33534596' # expected: '46' # Failed test at t/callbacks.t line 22. # got: '7171660' # expected: '23' # Failed test at t/callbacks.t line 26. # got: '-40706256' # expected: '23' # Looks like you failed 6 tests of 25. t/callbacks.t . Dubious, test returned 6 (wstat 1536, 0x600) Failed 6/25 subtests t/closures.t .. ok t/constants.t . ok t/enums.t . Failed 3/4 subtests t/hashes.t ok t/interface-implementation.t .. ok t/objects.t ... ok t/structs.t ... ok t/values.t ok t/vfunc-chaining.t ok t/vfunc-ref-counting.t ok Failed 3/16 test programs. 7/299 subtests failed. Test Summary Report --- t/arrays.t (Wstat: 9 Tests: 2 Failed: 1) Failed test: 2 Non-zero wait status: 9 Parse errors: Bad plan. You planned 29 tests but ran 2. t/callbacks.t (Wstat: 1536 Tests: 25 Failed: 6) Failed tests: 3, 6, 9, 14, 19, 25 Non-zero exit status: 6 t/enums.t (Wstat: 11 Tests: 1 Failed: 0) Non-zero wait status: 11 Parse errors: Bad plan. You planned 4 tests but ran 1. Files=16, Tests=299, 835 wallclock secs ( 0.25 usr 0.09 sys + 74.57 cusr 19.01 csys = 93.92 CPU) Result: FAIL make[1]: *** [test_dynamic] Error 255 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_test: make -j1 test returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Build finished at 20140323-1923 Finished -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#736344: libffi: FTBFS on ppc64: symbols update needed
Source: libffi Version: 3.0.13-12 Severity: important Tags: patch Usertags: ppc64 Please update symbols of debian/libffi6.symbols.ppc64. Here is a patch attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd libffi-3.0.13.orig/debian/libffi6.symbols.ppc64 libffi-3.0.13/debian/libffi6.symbols.ppc64 --- libffi-3.0.13.orig/debian/libffi6.symbols.ppc64 2013-11-29 00:43:02.0 +0900 +++ libffi-3.0.13/debian/libffi6.symbols.ppc64 2014-01-22 22:07:25.0 +0900 @@ -10,11 +10,11 @@ ffi_prep_cif_var@Base 3.0.10~rc8 ffi_prep_closure@Base 3.0.4 ffi_prep_closure_loc@Base 3.0.4 + ffi_prep_closure_loc_linux64@Base 3.0.13 ffi_prep_java_raw_closure@Base 3.0.4 ffi_prep_java_raw_closure_loc@Base 3.0.4 ffi_prep_raw_closure@Base 3.0.4 ffi_prep_raw_closure_loc@Base 3.0.4 - ffi_prep_raw_closure_loc_linux64@Base 3.0.13 ffi_ptrarray_to_raw@Base 3.0.4 ffi_raw_call@Base 3.0.4 ffi_raw_size@Base 3.0.4
Bug#733046: hdf5: libhdf5-mpi-dev depends libhdf5-mpich-dev, not libhdf5-mpich2-dev by replacing from mpich2 to mpich
Source: hdf5 Version: 1.8.11-5 Severity: important Control: found -1 1.8.12-2 Control: found -1 1.8.12-1 libhdf5-mpi-dev depends libhdf5-mpich-dev, not libhdf5-mpich2-dev by replacing from mpich2 to mpich on the ports which use mpich by mpi-default-dev_1.0.2. s390x: https://buildd.debian.org/status/fetch.php?pkg=hdf5arch=s390xver=1.8.12-2stamp=1387821930 https://buildd.debian.org/status/fetch.php?pkg=hdf5arch=s390xver=1.8.12-1stamp=1387545556 mips: https://buildd.debian.org/status/fetch.php?pkg=hdf5arch=mipsver=1.8.12-1stamp=1387557167 ppc64: http://buildd.debian-ports.org/status/fetch.php?pkg=hdf5arch=ppc64ver=1.8.12-2stamp=1387855461 http://buildd.debian-ports.org/status/fetch.php?pkg=hdf5arch=ppc64ver=1.8.12-1stamp=1387581642 http://buildd.debian-ports.org/status/fetch.php?pkg=hdf5arch=ppc64ver=1.8.11-5stamp=1387002060 This bug is brought about by substitution mistake that $(DEFAULT_MPI) becomes mpich, not mpich2 in debian/rules file. mpi-defaults_1.0.2 succeeded to be built on s390x, mips, mipsel, ppc64, m68k, hppa, which use mpich or mpich2, and on other ports (sh4, sparc64, x32), it cannot be built yet by unsatisfying build-dep of mpich, now. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731069: gcc-defaults: Please resume considering to change using unified version of gcc
Aurelien Jarno wrote: On Wed, Dec 04, 2013 at 01:52:22AM +0100, Matthias Klose wrote: Am 02.12.2013 23:20, schrieb Hiroyuki Yamamoto: Hi, I don't know whether it is appropriate that I remark, I have no objection to moving to gcc-4.8 on ppc64, too. this is not a question about any objections, but about a call to the ppc64 porters if they are able to maintain such a port in Debian. There is no response yet. Hiroyuki Yamamoto is the porter behind ppc64, so please consider that as an answer. Is Message #42 of Bug#731069 not enough? http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=731069#42 Best Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731252: Don't redeclare desc in mini_create_ftnptr on ppc64
Jo Shields wrote: On Wed, 2013-12-04 at 19:16 +0900, Hiroyuki Yamamoto wrote: Hiroyuki Yamamoto wrote: Jo Shields wrote: On Tue, 2013-12-03 at 17:34 +0100, Mathieu Malaterre wrote: Hiroyuki, On Tue, Dec 3, 2013 at 5:29 PM, Jo Shields direct...@apebox.org wrote: On Tue, 2013-12-03 at 17:08 +0100, Mathieu Malaterre wrote: Package: mono Tags: patch Please fix the ppc64 compilation error: http://buildd.debian-ports.org/status/fetch.php?pkg=monoarch=ppc64ver=3.0.6%2Bdfsg2-9stamp=1384751932 Is this sufficient to fix later issues with building on ppc64? As per http://buildd.debian-ports.org/status/fetch.php?pkg=monoarch=ppc64ver=3.2.3%2Bdfsg-3stamp=1385928050 I'm not too interested in making ports-only fixes to the package in sid, as my efforts are focused on the newer version in experimental right now - I'd only want to pull this fix in if it *really* fixes the build, not just makes it fail a little later. Could you please try the above patch and let us know if this is sufficient to build mono on ppc64 ? OK. I'll try it later. I tried to build patched mono_3.0.6+dfsg2-9 of sid and succeeded. (deleted 'gpointer *desc;' line) Here is a buildlog attached. About ver. 3.2 mono of experimental, mono_3.2.1+dfsg-1 was failed by same reason, but form mono_3.2.3+dfsg-1 it was solved and failed after it. OK, that's a fatal error in the runtime. I agree it. I'm not going to add ppc64 to the 3.0.6 package largely because I want to focus my efforts on 3.2 not 3.0 - and it's broken in 3.2, so it'd be a waste of time to have a single working 3.0.6 which then gets replaced in a month by a broken 3.2.6 OK. I understand. But I hope that it will be solved as soon as possible. I've CC'd in Alex Petersen of Xamarin - if you can coordinate access to PPC64 hardware in some capacity with him, he might be able to look into the build failures in 3.2 so we can fix it properly going forwards. I can cooperation building test sources. But my ppc64 machine is buildd-node, so it cannot be opened. I think that 'Alex Petersen of Xamarin' is the same person of a DD, 'Alex Rønne Petersen', maybe he have permission to use partch.d.o as a ppc/ppc64 porterbox. http://db.debian.org/machines.cgi?host=partch (Sorry, piston.d.o isn't left now.) Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731252: Don't redeclare desc in mini_create_ftnptr on ppc64
Hi, Jo Shields wrote: On Tue, 2013-12-03 at 17:34 +0100, Mathieu Malaterre wrote: Hiroyuki, On Tue, Dec 3, 2013 at 5:29 PM, Jo Shields direct...@apebox.org wrote: On Tue, 2013-12-03 at 17:08 +0100, Mathieu Malaterre wrote: Package: mono Tags: patch Please fix the ppc64 compilation error: http://buildd.debian-ports.org/status/fetch.php?pkg=monoarch=ppc64ver=3.0.6%2Bdfsg2-9stamp=1384751932 Is this sufficient to fix later issues with building on ppc64? As per http://buildd.debian-ports.org/status/fetch.php?pkg=monoarch=ppc64ver=3.2.3%2Bdfsg-3stamp=1385928050 I'm not too interested in making ports-only fixes to the package in sid, as my efforts are focused on the newer version in experimental right now - I'd only want to pull this fix in if it *really* fixes the build, not just makes it fail a little later. Could you please try the above patch and let us know if this is sufficient to build mono on ppc64 ? OK. I'll try it later. If a PPC64 porterbox were available (or a ppc64 chroot on partch, given it's already got a 64-bit kernel), then it would be much easier to test and fix issues in Mono and similar porting-required packages, as it would remove the upload-wait-buildlog-upload-wait-buildlog cycle from testing. This is my general objection to adding new debian-ports architectures to the Mono packages - I want to be able to test things and I can't. I made a ppc64 environment on /srv/chroot/sid of 'piston' in May 2012, but 'piston' is restricted machine and I have no permission now, so, I don't know that it is still left as it was, now. Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731069: gcc-defaults: Please resume considering to change using unified version of gcc
Hi, (2013/12/04 9:52), Matthias Klose wrote: Am 02.12.2013 23:20, schrieb Hiroyuki Yamamoto: Hi, I don't know whether it is appropriate that I remark, I have no objection to moving to gcc-4.8 on ppc64, too. this is not a question about any objections, but about a call to the ppc64 porters if they are able to maintain such a port in Debian. There is no response yet. Because I don't have enough skill for maintaining powerpc64-unknown-linux-gnu-gcc as no trouble now, I don't know whether I may remark or not. But I will make effort to find occurring troubles and to maintain it as no trouble within my possible skill. I did check http://gcc.gnu.org/gcc-4.9/criteria.html and apparently ppc64 is a primary release architecture, so I did make it the default for sid (and will make 4.9 the default for jessie once uploaded to unstable). I also think it reasonable at this moment. Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731069: gcc-defaults: Please resume considering to change using unified version of gcc
Hi, I don't know whether it is appropriate that I remark, I have no objection to moving to gcc-4.8 on ppc64, too. Matthias Klose wrote: Control: tags -1 + moreinfo Afaics, the situation didn't change. There is nobody committing to work on the toolchain for these architectures. At least for release architectures the alternative is to drop the port unless somebody wants to maintain the toolchain for this port. This is the current status, please correct me if I'm wrong. - alpha, no feedback, CCing Michael Cree. - hppa, no feedback, CCing John David Anglin - ia64, no feedback, likely to be removed. - powerpc, found some feedback from the porters, but unrelated to toolchain issues, see https://lists.debian.org/debian-powerpc/2013/11/msg00050.html - powerpcspe, no feedback, CCing Roland Stigge. - ppc64, no feedback - s390x, pending upload - sparc, no feedback - sh4, no feedback, doesn't build, CCing Nobuhiro Iwamatsu Am 01.12.2013 16:45, schrieb Hiroyuki Yamamoto: Source: gcc-defaults Version: 1.123 Severity: wishlist Tags: patch Please resume considering to change using unified version of gcc, because FTBFS of many packages occur by e.g. c++11 on ports which stayed using gcc-4.6 and g++-4.6, ia64, powerpc, s390x, sparc, alpha, powerpcspe, ppc64, sh4. And using unified version of gcc must bring happiness to many package maintainers. On the other hand, I understand that this changing depends on the correspondence status of gcc porting, so I leave decision to you. This is a decision for the porters. If there are no active porters, there shouldn't be a port. Unfortunately, building gcc-4.8 source package on sh4 has not succeeded yet, so here is a patch which changes gcc-4.8 using on ports except sh4. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731031: tcpdump: FTBFS on Big-Endian ports: 'nflog-e' test failed
Source: tcpdump Version: 4.5.1-1 Severity: serious Justification: FTBFS on Big-Endian ports 'nflog-e' test of tcpdump_4.5.1-1 failed on Big-Endian ports, mips, powerpc, s390x, sparc, powerpcspe, ppc64, and maybe same on m68k, sparc64. https://buildd.debian.org/status/package.php?p=tcpdumpsuite=sid http://buildd.debian-ports.org/status/package.php?p=tcpdumpsuite=sid Failed test: nflog-e 1,4c1,4 version 0, resource ID 20, family IPv4 (2), length 180: version 0, resource ID 20, family IPv4 (2), length 192: version 0, resource ID 20, family IPv4 (2), length 184: version 0, resource ID 20, family IPv4 (2), length 196: --- version 0, resource ID 20, family IPv4 (2), length 180: 74.82.42.42.53 10.0.0.20.42585: 17265 1/0/0 A 93.184.216.119 (45) version 0, resource ID 20, family IPv4 (2), length 192: 74.82.42.42.53 10.0.0.20.45190: 52954 1/0/0 2606:2800:220:6d:26bf:1447:1097:aa7 (57) version 0, resource ID 20, family IPv4 (2), length 184: 74.82.42.42.53 10.0.0.20.44031: 8279 1/0/0 A 93.184.216.119 (49) version 0, resource ID 20, family IPv4 (2), length 196: 74.82.42.42.53 10.0.0.20.48736: 2122 1/0/0 2606:2800:220:6d:26bf:1447:1097:aa7 (61) make[1]: *** [check] Error 1 make[1]: Leaving directory `/«PKGBUILDDIR»' dh_auto_test: make -j6 check returned exit code 2 make: *** [build-arch] Error 2 dpkg-buildpackage: error: debian/rules build-arch gave error exit status 2 Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#731060: gcc-defaults: Please move symlink of /usr/include/asm from 'gcc-multilib' to 'gcc' package
Source: gcc-defaults Version: 1.123 Severity: important Please move symlink of /usr/include/asm from 'gcc-multilib' to 'gcc' package, because 1. failing to be found of /usr/include/asm causes failing to build many sources. 2. 'build-essential' package depends on 'gcc' package, but 'gcc-multilib' not. 3. /usr/include/$(DEB_HOST_MULTIARCH)/asm is provided by linux-libc-dev package of all linux architectures now. Here is a patch for moving asm symlink. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd gcc-defaults-1.123.orig/debian/rules gcc-defaults-1.123/debian/rules --- gcc-defaults-1.123.orig/debian/rules 2013-07-10 01:24:13.0 +0900 +++ gcc-defaults-1.123/debian/rules 2013-12-01 23:20:16.0 +0900 @@ -494,15 +494,9 @@ /usr/share/info/libgomp-$(PV_GCC).info.gz /usr/share/info/libgomp.info.gz endif -ifeq ($(with_multiarch_lib),yes) - ifeq ($(with_multilib),yes) - : # gcc-multilib - # multilib needs to provide a compat symlink pointing to the asm - # header directory of the primary architecture, since we may not - # have separate asm headers installed for our non-default targets. - dh_link -pgcc-multilib \ +ifeq ($(OS_NAME),Linux) + dh_link -pgcc \ /usr/include/$(DEB_HOST_MULTIARCH)/asm /usr/include/asm - endif endif ifneq (,$(filter gdc, $(packages)))
Bug#731069: gcc-defaults: Please resume considering to change using unified version of gcc
Source: gcc-defaults Version: 1.123 Severity: wishlist Tags: patch Please resume considering to change using unified version of gcc, because FTBFS of many packages occur by e.g. c++11 on ports which stayed using gcc-4.6 and g++-4.6, ia64, powerpc, s390x, sparc, alpha, powerpcspe, ppc64, sh4. And using unified version of gcc must bring happiness to many package maintainers. On the other hand, I understand that this changing depends on the correspondence status of gcc porting, so I leave decision to you. Unfortunately, building gcc-4.8 source package on sh4 has not succeeded yet, so here is a patch which changes gcc-4.8 using on ports except sh4. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd gcc-defaults-1.123.orig/debian/rules gcc-defaults-1.123/debian/rules --- gcc-defaults-1.123.orig/debian/rules 2013-07-10 01:24:13.0 +0900 +++ gcc-defaults-1.123/debian/rules 2013-12-02 00:25:31.0 +0900 @@ -160,7 +160,7 @@ DEB_HOST_MULTIARCH := $(shell dpkg-architecture -qDEB_HOST_MULTIARCH) #gcc48_archs = alpha amd64 armel armhf hppa i386 ia64 m68k mips mipsel powerpc powerpcspe ppc64 s390 s390x sh4 sparc sparc64 kfreebsd-amd64 kfreebsd-i386 hurd-i386 -gcc48_archs = amd64 armel armhf arm64 i386 m68k mips mipsel x32 kfreebsd-amd64 kfreebsd-i386 hurd-i386 sparc64 +gcc48_archs = alpha amd64 armel armhf arm64 i386 ia64 m68k mips mipsel powerpc powerpcspe ppc64 s390x sparc sparc64 x32 kfreebsd-amd64 kfreebsd-i386 hurd-i386 gcj48_archs = alpha amd64 armel armhf arm64 hppa i386 ia64 m68k mips mipsel powerpc powerpcspe ppc64 s390 s390x sh4 sparc sparc64 x32 kfreebsd-amd64 kfreebsd-i386 hurd-i386 # CV_XXX is the complete version number, including the release, without epoch
Bug#729876: aghermann: FTBFS on ia64, powerpc, s390x, sparc, ppc64, sh4: configure: error: g++ = 4.7 is required
Hi, Thanks for a patch , Andrei. However, with considering of happiness for all package maintainers, maybe it is good that gcc-defaults shifts using unified version of gcc on all architectures, e.g. dealing with c++11. Matthias Klose posted a plan of updating default gcc, but since applied only some architectures, there is no change recently. http://lists.debian.org/debian-devel-announce/2013/05/msg5.html http://lists.debian.org/debian-devel/2013/05/msg00259.html Unfortunately, on sh4, gcc-4.8 has not succeeded to build yet, but the other architectures have ever succeeded. http://buildd.debian-ports.org/status/logs.php?pkg=gcc-defaultsarch=sh4 Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC andrei zavada wrote: Hi, I added to debian/rules a small amount of bash code which selects the best available g++ (trying first g++-4.8 then 4.7, both of which are known to work) and assigns it to CXX. After that, ./configure will use $CXX (not whatever g++ happens to be), and therein lieth the fix. This is the relevant part: %: for v in 4.8 4.7; do \ g=`which g++-$$v`; \ if test -n $$g; then \ $$g /dev/null 21; \ if [ $$? != 127 ]; then export CXX=`which g++-$$v`; break; fi \ fi \ done; \ dh $@ --with autoreconf The check for exit code 127 is required to detect the case of /usr/bin/g++-4.x existing (as a symlink) without g++-4.x actually installed. This is actually the case with g++-4.9: $ g++-4.9 /usr/bin/g++-4.9: not found (maybe g++-4.9 is not installed?) $ echo $? 127 Unless anyone suggests a better solution, I would ask my trusty sponsor Yaroslav to proceed with upload from http://johnhommer.com/academic/code/aghermann/source/deb/aghermann_1.0-2.dsc. Thanks Andrei On Mon, 18 Nov 2013 23:34:17 +0900 Hiroyuki Yamamoto yama1...@gmail.com wrote: Source: aghermann Version: 1.0-1 Severity: serious Justification: FTBFS by unsatisfiable build-dependency aghermann cannot be built on ia64, powerpc, s390x, sparc, ppc64, sh4, which use gcc-4.6 designated by gcc-defaults_1.123, so, maybe on alpha, too. https://buildd.debian.org/status/package.php?p=aghermannsuite=sid http://buildd.debian-ports.org/status/package.php?p=aghermannsuite=sid configure: error: g++ = 4.7 is required to build aghermann as we must use -std=c++11 features your compiler doesn't seem to support checking whether g++ has all required c++11 features... no On powerpcspe, its sbuild may not be maintained as clean-build environment, and all of g++-4.6, g++-4.7, g++-4.8 are installed, so building succeeded. Regards, -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#729876: aghermann: FTBFS on ia64, powerpc, s390x, sparc, ppc64, sh4: configure: error: g++ = 4.7 is required
Source: aghermann Version: 1.0-1 Severity: serious Justification: FTBFS by unsatisfiable build-dependency aghermann cannot be built on ia64, powerpc, s390x, sparc, ppc64, sh4, which use gcc-4.6 designated by gcc-defaults_1.123, so, maybe on alpha, too. https://buildd.debian.org/status/package.php?p=aghermannsuite=sid http://buildd.debian-ports.org/status/package.php?p=aghermannsuite=sid configure: error: g++ = 4.7 is required to build aghermann as we must use -std=c++11 features your compiler doesn't seem to support checking whether g++ has all required c++11 features... no On powerpcspe, its sbuild may not be maintained as clean-build environment, and all of g++-4.6, g++-4.7, g++-4.8 are installed, so building succeeded. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#710890: libfftw3-3 transitional package also has to depend on libfftw3-long3
Control: reopen -1
Hi,
libfftw3-long3 of fftw3 (3.3.3-6) can be built only on
amd64 hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc
powerpcspe s390 s390x sparc.
So, libfftw3-3 cannot be installed on armel, armhf, mips, mipsel, alpha,
arm64, hppa, m68k, ppc64, sh4, sparc64, x32.
Please change debian/control at Architecture: of libfftw3-long3
to any, or Depends: of libfftw3-3 to libfftw3-long3 (=${binary:Version})
[amd64 hurd-i386 i386 ia64 kfreebsd-amd64 kfreebsd-i386 powerpc powerpcspe s390
s390x sparc].
Best regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#677243: libverto: FTBFS on ppc64
Hi, If you read this URL[1], you can be certain that function descriptors on powerpc64-linux appear in the data section. [1] http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#726186: zvbi: FTBFS: test-packet-830 failed on ia64, s390x, alpha, and ppc64
Control: retitle -1 zvbi: FTBFS: test-packet-830 failed on ia64, s390x, alpha, and ppc64 Control: severity -1 serious Hi, This bug is also found on ia64, s390x, alpha, and ppc64. https://buildd.debian.org/status/fetch.php?pkg=zvbiarch=ia64ver=0.2.35-1stamp=1380836524 https://buildd.debian.org/status/fetch.php?pkg=zvbiarch=s390xver=0.2.35-1stamp=1380836564 http://buildd.debian-ports.org/status/fetch.php?pkg=zvbiarch=alphaver=0.2.35-1stamp=1380861750 http://buildd.debian-ports.org/status/fetch.php?pkg=zvbiarch=ppc64ver=0.2.35-1stamp=1380891222 However, it isn't found on amd64 and sparc64 which are also 64-bit architectures. Although I'm not sure, by some chance, it may have relation that zvbi_0.2.35-1 was built by gcc-4.6 on ia64, s390x, alpha, and ppc64, and that zvbi_0.2.35-1 was built by gcc-4.8 on amd64 and sparc64. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716813: fpc: FTBFS on ppc64: install/man/man1/ppcppc64.1 has vanished
Hi, Here is a patch attached. Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd fpc-2.6.2.orig/debian/patches/series fpc-2.6.2/debian/patches/series --- fpc-2.6.2.orig/debian/patches/series 2013-07-24 09:38:15.0 +0900 +++ fpc-2.6.2/debian/patches/series 2013-10-06 20:25:33.0 +0900 @@ -10,3 +10,4 @@ armhf-build-with-2.6.0.diff add-a-new-directive-CFGDIR-to-configuration-file.patch use-bfd-explicitly.diff +add-ppc64-support.diff
Bug#613820: Please support ppc64
Control: reopen -1 Control: found -1 libx11/2:1.6.1-1 Control: severity -1 important The change at ver. 2:1.6.1-1 is not to add supporting ppc64 port which was remarked dead and buried by Julien Cristau, but to add supporting powerpc64 port which is a new port and not listed to Debian's ports in dpkg now. So, this bug is not fixed and this closing is mistake certainly. http://buildd.debian-ports.org/status/package.php?p=libx11suite=sid Because there is ability that Julien plans to begin another porting powerpc64, I post a new patch added furthermore ppc64 port. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd libx11-1.6.1.orig/debian/libx11-6.symbols libx11-1.6.1/debian/libx11-6.symbols --- libx11-1.6.1.orig/debian/libx11-6.symbols 2013-08-13 21:23:09.0 +0900 +++ libx11-1.6.1/debian/libx11-6.symbols 2013-08-13 21:26:40.0 +0900 @@ -791,7 +791,7 @@ _XCopyEventCookie@Base 2:1.2.99.901 (optional)_XCopyToArg@Base 0 1 _XCreateMutex_fn@Base 0 - (arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 s390x sparc64)_XData32@Base 0 + (arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 ppc64 s390x sparc64)_XData32@Base 0 _XDefaultError@Base 0 _XDefaultIOError@Base 0 (optional)_XDefaultOpenIM@Base 0 1 @@ -854,7 +854,7 @@ _XProcessInternalConnection@Base 0 _XProcessWindowAttributes@Base 0 _XPutBackEvent@Base 0 - (arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 s390x sparc64)_XRead32@Base 0 + (arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 ppc64 s390x sparc64)_XRead32@Base 0 _XRead@Base 0 _XReadEvents@Base 0 _XReadPad@Base 0 @@ -1102,9 +1102,9 @@ (optional)_XkbInternAtomFunc@Base 0 1 (optional)_XkbNoteCoreMapChanges@Base 0 1 (optional)_XkbPeekAtReadBuffer@Base 0 1 - (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 s390x sparc64)_XkbReadBufferCopy32@Base 0 1 + (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 ppc64 s390x sparc64)_XkbReadBufferCopy32@Base 0 1 (optional)_XkbReadBufferCopyKeySyms@Base 0 1 - (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 s390x sparc64)_XkbReadCopyData32@Base 0 1 + (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 ppc64 s390x sparc64)_XkbReadCopyData32@Base 0 1 (optional)_XkbReadCopyKeySyms@Base 0 1 (optional)_XkbReadGetCompatMapReply@Base 0 1 (optional)_XkbReadGetGeometryReply@Base 0 1 @@ -1113,7 +1113,7 @@ (optional)_XkbReadGetNamesReply@Base 0 1 (optional)_XkbReloadDpy@Base 0 1 (optional)_XkbSkipReadBufferData@Base 0 1 - (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 s390x sparc64)_XkbWriteCopyData32@Base 0 1 + (optional|arch=arm64 alpha amd64 kfreebsd-amd64 ia64 powerpc64 ppc64 s390x sparc64)_XkbWriteCopyData32@Base 0 1 (optional)_XkbWriteCopyKeySyms@Base 0 1 (optional)_XkeyTable@Base 0 1 (optional)_XlcAddCT@Base 0 1
Bug#613820: Please support ppc64
Hi, Julien. Julien Cristau wrote: On Tue, Aug 13, 2013 at 23:02:32 +0900, Hiroyuki Yamamoto wrote: Control: reopen -1 Control: found -1 libx11/2:1.6.1-1 Control: severity -1 important The change at ver. 2:1.6.1-1 is not to add supporting ppc64 port which was remarked dead and buried by Julien Cristau, but to add supporting powerpc64 port which is a new port and not listed to Debian's ports in dpkg now. So, this bug is not fixed and this closing is mistake certainly. http://buildd.debian-ports.org/status/package.php?p=libx11suite=sid Because there is ability that Julien plans to begin another porting powerpc64, I post a new patch added furthermore ppc64 port. Oh ffs. Apparently consistency is too much to ask for... ffs? Although there is no way, if you intended to change official source package and be enbuged ONLY for provoking me, I must doubt that you are an appropriate DD. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#613820: Please support ppc64
Julien Cristau wrote: Oh ffs. Apparently consistency is too much to ask for... ffs? Although there is no way, if you intended to change official source package and be enbuged ONLY for provoking me, I must doubt that you are an appropriate DD. No, I'm just annoyed at myself for the mistake, and at whoever picked the ppc64 arch name because it doesn't seem to make sense to use that when our ppc port is called powerpc. OK, sorry, it seems that I misunderstood you a little. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716813: fpc: FTBFS on ppc64: install/man/man1/ppcppc64.1 has vanished
Control: reopen -1 Control: found -1 fpc/2.6.2-5 Because add-ppc64-support.diff is not described in debian/patches/series, the source is not patched by the same reason as Bug#692893. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716813: fpc: FTBFS on ppc64: install/man/man1/ppcppc64.1 has vanished
Source: fpc Version: 2.6.2-2 Severity: important Tags: patch upstream install/man/man1/ppcppc64.1 which was included by closing Bug#692893 has vanished with changing from ver. 2.6.0-12 to ver. 2.6.2-1. So, FTBFS on ppc64 revives. I guess that it occurs by debian/patches/add-ppc64-support.diff file erased before install/man/man1/ppcppc64.1 file adopted into upstream's code. Please report to upstream. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#716813: fpc: FTBFS on ppc64: install/man/man1/ppcppc64.1 has vanished
Sorry, I forgot to attach a patch. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd fpc-2.6.2.orig/install/man/man1/ppcppc64.1 fpc-2.6.2/install/man/man1/ppcppc64.1 --- fpc-2.6.2.orig/install/man/man1/ppcppc64.1 1970-01-01 09:00:00.0 +0900 +++ fpc-2.6.2/install/man/man1/ppcppc64.1 2013-07-12 21:57:01.0 +0900 @@ -0,0 +1,33 @@ +.TH ppcppc64 1 30 may 1999 Free Pascal Free Pascal Compiler +.SH NAME +ppcppc64 \- Free Pascal Compiler (FPC) binary, name derived +from Portable Pascal Compiler + +.SH SYNOPSIS + +.B ppcppc64 [options] [sourcefile] +.BR + +.SH DESCRIPTION +This binary is the back-end binary of the +.I Free Pascal Compiler (FPC) +which is a +.I Turbo Pascal +and +.I Delphi (7.0) +compatible standalone (non GCC frontend) multitarget Pascal compiler. + +This binary should not be called directly, instead the +.B fpc +program should be used instead. +It will choose the right back-end for compiling units for the requested platforms. + +.SH OPTIONS + +For a complete list of all supported command-line options, see the +.BR fpc (1) +manual page. + +.SH SEE ALSO +.BR fpc (1) +
Bug#701561: Please test ioquake3 on PowerPC, particularly without Altivec
Hi, I'm a porter of ppc64 port. Unluckyly, ppc64 buildd nodes and my machines are shifting of place, and they are offline now. (If no trouble, plobably they will revive to online on 2013-06-16.) So, this build test cannot be done now, but on ppc64 port, the packages have been tested to be built packages with Altivec option as default, unless package maintainers specify build options. If buildlogs till now are helpful, please refer to them. http://buildd.debian-ports.org/status/logs.php?pkg=ioquake3arch=ppc64 Regards, -- Hiroyuki Yamamoto (2013/06/04 23:37), thinkbr...@gmail.com wrote: On Tue, Jun 4, 2013 at 9:58 AM, Simon McVittie s...@debian.org wrote: On 04/06/13 13:58, thinkbr...@gmail.com wrote: One thing I'd suggest is that altivec is enabled based on the CPU itself, and not just PPC vs PPC64. Sorry, I'm not going to do significant development on this myself, but if you or another powerpc porter want to put a patchset together, upstream would probably take it. There seems to be some support for runtime detection already, but AIUI, compiling the whole thing with -maltivec means that's useless, because gcc is within its rights to emit Altivec instructions anyway? Another possibility would be to have a separate lowest common denominator Q3 binary for PowerPC-without-Altivec, and have it transparently exec the Altivec binary (with the same command line) if it determines that we do actually have Altivec. It would probably need to behave like its own mini-architecture within the Quake 3 engine, with a separate suffix or directory for loadable modules (perhaps *ppc.so for Altivec and *oldppc.so for non-Altivec?) What I'm more concerned about is whether the PowerPC JIT for the Quake 3 bytecode language (code/qcommon/vm_powerpc*) emits Altivec opcodes - I have no idea how I'd determine that. That's why I'm specifically asking for testing with the bytecode game logic. I did some tinkering with runtime detection when I was working on getting PPC64 support under Quake II, so I'll see if I can make something work. Maybe *ppcaltivec.so, *ppc.so, and *ppc64.so Is Rage128 still a supported 3D accelerator? I know it'll be slow as heck, but it's the only card I have for my PowerMac G3s. Your guess is as good as mine :-) If all G3s are likely to be this low-spec, perhaps ioquake3/powerpc should just continue to require Altivec, and put a note in xmessage(1) on older machines... Yeah, for the most part, non-altivec PPC/PPCSPE machines are probably going to be incapable of running Quake III at a reasonable speed. AFAIK, the highest end PCI card that there's a Macintosh ROM for is the Radeon 7000. I'll see if I can get a build machine up later today, since actually compiling on a G3 would be exceptionally slow. Logan -- Hiroyuki Yamamoto -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#708641: python2.7: wrong sequence of __powerpc__ and __powerpc64__ in debian/multiarch.h.in
Source: python2.7 Version: 2.7.5-2 Severity: important Tags: patch GCC of Linux/PowerPC64 defines not only __powerpc64__ but also __powerpc__, so if there is a decision of __powerpc__ before __powerpc64__, the decision of __powerpc__ becomes TRUE. e.g..: http://buildd.debian-ports.org/status/fetch.php?pkg=python-qt4arch=ppc64ver=4.10.1-1stamp=1368762729 Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd python2.7-2.7.5.orig/debian/multiarch.h.in python2.7-2.7.5/debian/multiarch.h.in --- python2.7-2.7.5.orig/debian/multiarch.h.in 2013-05-17 21:39:15.0 +0900 +++ python2.7-2.7.5/debian/multiarch.h.in 2013-05-17 21:53:13.0 +0900 @@ -41,10 +41,10 @@ # endif # elif defined(__powerpc__) defined(__SPE__) # include powerpc-linux-gnuspe/@subdir@/@header@ -# elif defined(__powerpc__) -# include powerpc-linux-gnu/@subdir@/@header@ # elif defined(__powerpc64__) # include powerpc64-linux-gnu/@subdir@/@header@ +# elif defined(__powerpc__) +# include powerpc-linux-gnu/@subdir@/@header@ # elif defined(__s390x__) # include s390x-linux-gnu/@subdir@/@header@ # elif defined(__s390__)
Bug#708646: python3.3: wrong sequence of __powerpc__ and __powerpc64__ in debian/multiarch.h.in
Source: python3.3 Version: 3.3.2-1 Severity: important Tags: patch GCC of Linux/PowerPC64 defines not only __powerpc64__ but also __powerpc__, so if there is a decision of __powerpc__ before __powerpc64__, the decision of __powerpc__ becomes TRUE. Bug#708641 was posted to python2.7 for same cause. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd python3.3-3.3.2.orig/debian/multiarch.h.in python3.3-3.3.2/debian/multiarch.h.in --- python3.3-3.3.2.orig/debian/multiarch.h.in 2013-05-17 22:34:12.0 +0900 +++ python3.3-3.3.2/debian/multiarch.h.in 2013-05-17 22:35:38.0 +0900 @@ -41,10 +41,10 @@ # endif # elif defined(__powerpc__) defined(__SPE__) # include powerpc-linux-gnuspe/@subdir@/@header@ -# elif defined(__powerpc__) -# include powerpc-linux-gnu/@subdir@/@header@ # elif defined(__powerpc64__) # include powerpc64-linux-gnu/@subdir@/@header@ +# elif defined(__powerpc__) +# include powerpc-linux-gnu/@subdir@/@header@ # elif defined(__s390x__) # include s390x-linux-gnu/@subdir@/@header@ # elif defined(__s390__)
Bug#692893: fpc: FTBFS on ppc64: Please support ppc64
Hi, fpc 2.6.0-10 still has FTBFS. http://buildd.debian-ports.org/status/fetch.php?pkg=fpcarch=ppc64ver=2.6.0-10stamp=1367296476 Causes is as follows: 1: Because PPSUF isn't set as ppc64 in debian/rules, PPNEW is maintained as ppc, so it cannot found fpc-2.6.0/fpcsrc/compiler/ppcppc64 at build RTL using new compiler. 2: Because add-ppc64-support.diff is not described in debian/patches/series, quilt doesn't patch for preparing install/man/man1/ppcppc64.1. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701504: hdf5: FTBFS on powerpc, powerpcspe, and ppc64 due to symbols files
Control: retitle -1 hdf5: FTBFS on powerpc, powerpcspe, and ppc64 due to symbols files Here are patches including ppc64 port. -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd hdf5-1.8.10-patch1.orig/debian/libhdf5-7.symbols hdf5-1.8.10-patch1/debian/libhdf5-7.symbols --- hdf5-1.8.10-patch1.orig/debian/libhdf5-7.symbols 2013-01-27 19:22:09.0 +0900 +++ hdf5-1.8.10-patch1/debian/libhdf5-7.symbols 2013-04-05 23:32:33.0 +0900 @@ -2020,7 +2020,7 @@ H5T__conv_ldouble_double@Base 1.8.7 H5T__conv_ldouble_float@Base 1.8.7 H5T__conv_ldouble_int@Base 1.8.7 - H5T__conv_ldouble_llong@Base 1.8.7 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_ldouble_llong@Base 1.8.7 H5T__conv_ldouble_long@Base 1.8.7 H5T__conv_ldouble_schar@Base 1.8.7 H5T__conv_ldouble_short@Base 1.8.7 @@ -2032,7 +2032,7 @@ H5T__conv_llong_double@Base 1.8.7 H5T__conv_llong_float@Base 1.8.7 H5T__conv_llong_int@Base 1.8.7 - H5T__conv_llong_ldouble@Base 1.8.7 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_llong_ldouble@Base 1.8.7 H5T__conv_llong_long@Base 1.8.7 H5T__conv_llong_schar@Base 1.8.7 H5T__conv_llong_short@Base 1.8.7 diff -Nurd hdf5-1.8.10-patch1.orig/debian/libhdf5-mpich2-7.symbols hdf5-1.8.10-patch1/debian/libhdf5-mpich2-7.symbols --- hdf5-1.8.10-patch1.orig/debian/libhdf5-mpich2-7.symbols 2013-01-27 19:22:09.0 +0900 +++ hdf5-1.8.10-patch1/debian/libhdf5-mpich2-7.symbols 2013-04-05 23:30:00.0 +0900 @@ -2138,7 +2138,7 @@ H5T__conv_ldouble_double@Base 1.8.10 H5T__conv_ldouble_float@Base 1.8.10 H5T__conv_ldouble_int@Base 1.8.10 - H5T__conv_ldouble_llong@Base 1.8.10 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_ldouble_llong@Base 1.8.10 H5T__conv_ldouble_long@Base 1.8.10 H5T__conv_ldouble_schar@Base 1.8.10 H5T__conv_ldouble_short@Base 1.8.10 @@ -2150,7 +2150,7 @@ H5T__conv_llong_double@Base 1.8.10 H5T__conv_llong_float@Base 1.8.10 H5T__conv_llong_int@Base 1.8.10 - H5T__conv_llong_ldouble@Base 1.8.10 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_llong_ldouble@Base 1.8.10 H5T__conv_llong_long@Base 1.8.10 H5T__conv_llong_schar@Base 1.8.10 H5T__conv_llong_short@Base 1.8.10 diff -Nurd hdf5-1.8.10-patch1.orig/debian/libhdf5-openmpi-7.symbols hdf5-1.8.10-patch1/debian/libhdf5-openmpi-7.symbols --- hdf5-1.8.10-patch1.orig/debian/libhdf5-openmpi-7.symbols 2013-01-27 19:22:09.0 +0900 +++ hdf5-1.8.10-patch1/debian/libhdf5-openmpi-7.symbols 2013-04-05 23:31:12.0 +0900 @@ -2138,7 +2138,7 @@ H5T__conv_ldouble_double@Base 1.8.10 H5T__conv_ldouble_float@Base 1.8.10 H5T__conv_ldouble_int@Base 1.8.10 - H5T__conv_ldouble_llong@Base 1.8.10 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_ldouble_llong@Base 1.8.10 H5T__conv_ldouble_long@Base 1.8.10 H5T__conv_ldouble_schar@Base 1.8.10 H5T__conv_ldouble_short@Base 1.8.10 @@ -2150,7 +2150,7 @@ H5T__conv_llong_double@Base 1.8.10 H5T__conv_llong_float@Base 1.8.10 H5T__conv_llong_int@Base 1.8.10 - H5T__conv_llong_ldouble@Base 1.8.10 + (arch=!powerpc !powerpcspe !ppc64)H5T__conv_llong_ldouble@Base 1.8.10 H5T__conv_llong_long@Base 1.8.10 H5T__conv_llong_schar@Base 1.8.10 H5T__conv_llong_short@Base 1.8.10 diff -Nurd hdf5-1.8.8.orig/debian/libhdf5-7.symbols hdf5-1.8.8/debian/libhdf5-7.symbols --- hdf5-1.8.8.orig/debian/libhdf5-7.symbols 2012-02-24 19:15:58.0 +0900 +++ hdf5-1.8.8/debian/libhdf5-7.symbols 2013-04-08 07:34:41.0 +0900 @@ -2015,7 +2015,7 @@ H5T_conv_ldouble_double@Base 1.8.7 H5T_conv_ldouble_float@Base 1.8.7 H5T_conv_ldouble_int@Base 1.8.7 - (arch=!powerpc !sh4)H5T_conv_ldouble_llong@Base 1.8.7 + (arch=!powerpc !powerpcspe !ppc64 !sh4)H5T_conv_ldouble_llong@Base 1.8.7 H5T_conv_ldouble_long@Base 1.8.7 H5T_conv_ldouble_schar@Base 1.8.7 H5T_conv_ldouble_short@Base 1.8.7 @@ -2027,7 +2027,7 @@ H5T_conv_llong_double@Base 1.8.7 H5T_conv_llong_float@Base 1.8.7 H5T_conv_llong_int@Base 1.8.7 - (arch=!powerpc !sh4)H5T_conv_llong_ldouble@Base 1.8.7 + (arch=!powerpc !powerpcspe !ppc64 !sh4)H5T_conv_llong_ldouble@Base 1.8.7 H5T_conv_llong_long@Base 1.8.7 H5T_conv_llong_schar@Base 1.8.7 H5T_conv_llong_short@Base 1.8.7 @@ -2107,7 +2107,7 @@ H5T_conv_ullong_float@Base 1.8.7 H5T_conv_ullong_int@Base 1.8.7 H5T_conv_ullong_ldouble@Base 1.8.7 - (arch=!armel !armhf !alpha !sparc !mipsel !powerpc !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 + (arch=!armel !armhf !alpha !sparc !mipsel !powerpc !powerpcspe !ppc64 !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 H5T_conv_ullong_llong@Base 1.8.7 H5T_conv_ullong_long@Base 1.8.7 H5T_conv_ullong_schar@Base 1.8.7 diff -Nurd hdf5-1.8.8.orig/debian/libhdf5-mpich2-7.symbols hdf5-1.8.8/debian/libhdf5-mpich2-7.symbols --- hdf5-1.8.8.orig/debian/libhdf5-mpich2-7.symbols 2012-01-31 23:02:05.0 +0900 +++ hdf5-1.8.8/debian/libhdf5-mpich2-7.symbols 2013-04-08 07:33:32.0 +0900 @@ -2056,7 +2056,7 @@ H5T_conv_ldouble_double@Base 1.8.7 H5T_conv_ldouble_float@Base 1.8.7 H5T_conv_ldouble_int@Base 1.8.7
Bug#704936: [Pkg-openmpi-maintainers] Bug#704936: openmpi1.6: FTBFS: inconsistency in debian/libopenmpi1.6.install
Hi, Sylvestre Ledru wrote: Hi, On 08/04/2013 01:10, Hiroyuki Yamamoto wrote: Source: openmpi1.6 Version: 1.6.4-1 Severity: serious Tags: patch sid Justification: FTBFS There is inconsistency in debian/libopenmpi1.6.install. Could you detail what you mean by inconsistency here ? debian/libopenmpi1.6.install of 1.6.4-1 includes dynamic link libraries which are not build without libcr-dev and supporting BLCR checkpointing, so, FTBFS occurs except for amd64, armel, armhf, i386, and powerpc. (On armel port, another FTBFS occurs.) https://buildd.debian.org/status/package.php?p=openmpi1.6suite=sid http://buildd.debian-ports.org/status/package.php?p=openmpi1.6suite=sid Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704936: openmpi1.6: FTBFS: inconsistency in debian/libopenmpi1.6.install
Source: openmpi1.6 Version: 1.6.4-1 Severity: serious Tags: patch sid Justification: FTBFS There is inconsistency in debian/libopenmpi1.6.install. Patch is attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd openmpi1.6-1.6.4.orig/debian/libopenmpi1.6.install openmpi1.6-1.6.4/debian/libopenmpi1.6.install --- openmpi1.6-1.6.4.orig/debian/libopenmpi1.6.install 2013-02-22 18:35:48.0 +0900 +++ openmpi1.6-1.6.4/debian/libopenmpi1.6.install 2013-04-07 22:04:22.0 +0900 @@ -8,93 +8,6 @@ usr/lib/openmpi/lib/libopen-pal.so.4.0.4 usr/lib/openmpi/lib/libopen-rte.so.4.0.3 ## Plugins -usr/lib/openmpi/lib/openmpi/libompi_dbg_msgq.so -usr/lib/openmpi/lib/openmpi/mca_allocator_basic.so -usr/lib/openmpi/lib/openmpi/mca_allocator_bucket.so -usr/lib/openmpi/lib/openmpi/mca_bml_r2.so -usr/lib/openmpi/lib/openmpi/mca_btl_ofud.so -usr/lib/openmpi/lib/openmpi/mca_btl_openib.so -usr/lib/openmpi/lib/openmpi/mca_btl_self.so -usr/lib/openmpi/lib/openmpi/mca_btl_sm.so -usr/lib/openmpi/lib/openmpi/mca_btl_tcp.so -usr/lib/openmpi/lib/openmpi/mca_carto_auto_detect.so -usr/lib/openmpi/lib/openmpi/mca_carto_file.so -usr/lib/openmpi/lib/openmpi/mca_coll_basic.so -usr/lib/openmpi/lib/openmpi/mca_coll_hierarch.so -usr/lib/openmpi/lib/openmpi/mca_coll_inter.so -usr/lib/openmpi/lib/openmpi/mca_coll_self.so -usr/lib/openmpi/lib/openmpi/mca_coll_sm.so -usr/lib/openmpi/lib/openmpi/mca_coll_sync.so -usr/lib/openmpi/lib/openmpi/mca_coll_tuned.so -usr/lib/openmpi/lib/openmpi/mca_crcp_bkmrk.so -usr/lib/openmpi/lib/openmpi/mca_crs_blcr.so -usr/lib/openmpi/lib/openmpi/mca_crs_none.so -usr/lib/openmpi/lib/openmpi/mca_crs_self.so -usr/lib/openmpi/lib/openmpi/mca_dpm_orte.so -usr/lib/openmpi/lib/openmpi/mca_errmgr_default.so -usr/lib/openmpi/lib/openmpi/mca_ess_env.so -usr/lib/openmpi/lib/openmpi/mca_ess_hnp.so -usr/lib/openmpi/lib/openmpi/mca_ess_singleton.so -usr/lib/openmpi/lib/openmpi/mca_ess_slave.so -usr/lib/openmpi/lib/openmpi/mca_ess_slurmd.so -usr/lib/openmpi/lib/openmpi/mca_ess_slurm.so -usr/lib/openmpi/lib/openmpi/mca_ess_tm.so -usr/lib/openmpi/lib/openmpi/mca_ess_tool.so -usr/lib/openmpi/lib/openmpi/mca_filem_rsh.so -usr/lib/openmpi/lib/openmpi/mca_grpcomm_bad.so -usr/lib/openmpi/lib/openmpi/mca_grpcomm_basic.so -usr/lib/openmpi/lib/openmpi/mca_iof_hnp.so -usr/lib/openmpi/lib/openmpi/mca_iof_orted.so -usr/lib/openmpi/lib/openmpi/mca_iof_tool.so -usr/lib/openmpi/lib/openmpi/mca_maffinity_first_use.so -usr/lib/openmpi/lib/openmpi/mca_maffinity_hwloc.so -usr/lib/openmpi/lib/openmpi/mca_mpool_fake.so -usr/lib/openmpi/lib/openmpi/mca_mpool_rdma.so -usr/lib/openmpi/lib/openmpi/mca_mpool_sm.so -usr/lib/openmpi/lib/openmpi/mca_notifier_command.so -usr/lib/openmpi/lib/openmpi/mca_notifier_syslog.so -usr/lib/openmpi/lib/openmpi/mca_odls_default.so -usr/lib/openmpi/lib/openmpi/mca_oob_tcp.so -usr/lib/openmpi/lib/openmpi/mca_osc_pt2pt.so -usr/lib/openmpi/lib/openmpi/mca_osc_rdma.so -usr/lib/openmpi/lib/openmpi/mca_paffinity_hwloc.so -usr/lib/openmpi/lib/openmpi/mca_plm_rsh.so -usr/lib/openmpi/lib/openmpi/mca_plm_slurm.so -usr/lib/openmpi/lib/openmpi/mca_plm_tm.so -usr/lib/openmpi/lib/openmpi/mca_pml_bfo.so -usr/lib/openmpi/lib/openmpi/mca_pml_cm.so -usr/lib/openmpi/lib/openmpi/mca_pml_crcpw.so -usr/lib/openmpi/lib/openmpi/mca_pml_csum.so -usr/lib/openmpi/lib/openmpi/mca_pml_ob1.so -usr/lib/openmpi/lib/openmpi/mca_pml_v.so -usr/lib/openmpi/lib/openmpi/mca_pstat_linux.so -usr/lib/openmpi/lib/openmpi/mca_pubsub_orte.so -usr/lib/openmpi/lib/openmpi/mca_ras_cm.so -usr/lib/openmpi/lib/openmpi/mca_ras_gridengine.so -usr/lib/openmpi/lib/openmpi/mca_ras_loadleveler.so -usr/lib/openmpi/lib/openmpi/mca_ras_slurm.so -usr/lib/openmpi/lib/openmpi/mca_ras_tm.so -usr/lib/openmpi/lib/openmpi/mca_rcache_vma.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_load_balance.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_rank_file.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_resilient.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_round_robin.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_seq.so -usr/lib/openmpi/lib/openmpi/mca_rmaps_topo.so -usr/lib/openmpi/lib/openmpi/mca_rml_ftrm.so -usr/lib/openmpi/lib/openmpi/mca_rml_oob.so -usr/lib/openmpi/lib/openmpi/mca_routed_binomial.so -usr/lib/openmpi/lib/openmpi/mca_routed_cm.so -usr/lib/openmpi/lib/openmpi/mca_routed_direct.so -usr/lib/openmpi/lib/openmpi/mca_routed_linear.so -usr/lib/openmpi/lib/openmpi/mca_routed_radix.so -usr/lib/openmpi/lib/openmpi/mca_routed_slave.so -usr/lib/openmpi/lib/openmpi/mca_shmem_mmap.so -usr/lib/openmpi/lib/openmpi/mca_shmem_posix.so -usr/lib/openmpi/lib/openmpi/mca_shmem_sysv.so -usr/lib/openmpi/lib/openmpi/mca_snapc_full.so -usr/lib/openmpi/lib/openmpi/mca_sysinfo_linux.so -usr/lib/openmpi/lib/openmpi/mca_topo_unity.so -usr/lib/openmpi/lib/openmpi/mca_vprotocol_pessimist.so +usr/lib/openmpi/lib/openmpi/*.so ## Other files usr/lib/openmpi/lib/mpi.mod diff -Nurd openmpi1.6-1.6.4.orig/debian/libopenmpi1.6.install.armel openmpi1.6-1.6.4/debian
Bug#704937: openmpi1.6: Please support BLCR checkpointing on ppc64 port
Source: openmpi1.6 Version: 1.6.4-1 Severity: wishlist Tags: patch Please support BLCR checkpointing on ppc64 port. Patch is attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd openmpi1.6-1.6.4.orig/debian/control openmpi1.6-1.6.4/debian/control --- openmpi1.6-1.6.4.orig/debian/control 2013-02-22 18:35:48.0 +0900 +++ openmpi1.6-1.6.4/debian/control 2013-04-06 00:14:37.0 +0900 @@ -4,7 +4,7 @@ Homepage: http://www.open-mpi.org/ Maintainer: Debian Open MPI Maintainers pkg-openmpi-maintain...@lists.alioth.debian.org Uploaders: Manuel Prinz man...@debian.org, Sylvestre Ledru sylves...@debian.org -Build-Depends: dpkg-dev (= 1.16.1~), debhelper (= 8.0.0~), libibverbs-dev (= 1.1.1), gfortran, gcc (= 4:4.1.2), chrpath, quilt, libcr-dev [amd64 armel armhf i386 powerpc], libnuma-dev [amd64 i386 ia64 mips mipsel powerpc], autoconf (= 2.59), automake, libtool, libltdl-dev, libhwloc-dev, libtorque2-dev +Build-Depends: dpkg-dev (= 1.16.1~), debhelper (= 8.0.0~), libibverbs-dev (= 1.1.1), gfortran, gcc (= 4:4.1.2), chrpath, quilt, libcr-dev [amd64 armel armhf i386 powerpc ppc64], libnuma-dev [amd64 i386 ia64 mips mipsel powerpc], autoconf (= 2.59), automake, libtool, libltdl-dev, libhwloc-dev, libtorque2-dev Standards-Version: 3.9.3 Vcs-Svn: svn://svn.debian.org/svn/pkg-openmpi/openmpi/trunk/ Vcs-Browser: http://svn.debian.org/wsvn/pkg-openmpi/openmpi/trunk/ diff -Nurd openmpi1.6-1.6.4.orig/debian/rules openmpi1.6-1.6.4/debian/rules --- openmpi1.6-1.6.4.orig/debian/rules 2013-02-22 18:38:34.0 +0900 +++ openmpi1.6-1.6.4/debian/rules 2013-04-07 21:36:06.0 +0900 @@ -10,7 +10,7 @@ endif # BLCR checkpointing support -BLCR_ARCH := amd64 armel armhf i386 powerpc +BLCR_ARCH := amd64 armel armhf i386 powerpc ppc64 ifneq (,$(findstring $(DEB_HOST_ARCH),$(BLCR_ARCH))) CHKPT = --enable-ft-thread --with-ft=cr --with-blcr=/usr --with-blcr-libdir=/usr/lib endif
Bug#704736: gtkpod: FTBFS on ppc64: Please modify libatomicparsley0.symbols
Source: gtkpod Version: 2.1.3-2 Severity: important Tags: patch FTBFS on ppc64 port occurs from ver. 2.1.2~beta2-3, because of ppc64 not listed in debian/libatomicparsley0.symbols. build logs http://buildd.debian-ports.org/status/package.php?p=gtkpodsuite=experimental http://buildd.debian-ports.org/status/package.php?p=gtkpodsuite=sid Here is a patch attached which was build-checked. Incidentally, this error also occurs on alpha which is 64-bit port, too, so, I think that it can correct by similar modification. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd gtkpod-2.1.3.orig/debian/libatomicparsley0.symbols gtkpod-2.1.3/debian/libatomicparsley0.symbols --- gtkpod-2.1.3.orig/debian/libatomicparsley0.symbols 2012-06-12 23:38:09.0 +0900 +++ gtkpod-2.1.3/debian/libatomicparsley0.symbols 2013-04-05 14:56:48.0 +0900 @@ -33,8 +33,8 @@ _Z13UTF8ToUTF16LEPhiPKhi@Base 0.0.1 _Z13UTF8Toisolat1PhiPKhi@Base 0.0.1 _Z13char4TOuint32jPc@Base 0.0.1 - (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z13char8TOuint64mPc@Base 0.0.1 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z13char8TOuint64yPc@Base 0.0.1 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x)_Z13char8TOuint64mPc@Base 0.0.1 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z13char8TOuint64yPc@Base 0.0.1 _Z13isolat1ToUTF8PhiPKhi@Base 0.0.1 _Z13sha1_init_ctxP8sha1_ctx@Base 0.0.1 _Z13sha1_read_ctxPK8sha1_ctxPv@Base 0.0.1 @@ -82,8 +82,8 @@ _Z19UInt16FromBigEndianPKc@Base 0.0.1 _Z19UInt32FromBigEndianPKc@Base 0.0.1 _Z19UInt64FromBigEndianPKc@Base 0.0.1 - (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1 - (arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1 + (arch=amd64 ia64 kfreebsd-amd64 ppc64 s390x)_Z20APar_AtomizeFileInfojjmPchhhjtP11uuid_vitals@Base 0.0.1 + (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z20APar_AtomizeFileInfojjyPchhhjtP11uuid_vitals@Base 0.0.1 _Z20APar_ExtractDataAtomi@Base 0.0.1 _Z20APar_ExtractPicPrefsPc@Base 0.0.1 _Z20APar_FindValueInAtomPcP8_IO_FILEsjj@Base 0.0.1
Bug#704742: shishi: FTBFS on s390x and ppc64: quilt is not working because of debian/patches/series missing
Source: shishi Version: 1.0.2-1 Severity: serious Tags: patch experimental Justification: FTBFS on s390x and ppc64 (64-bit big endian ports) Because of debian/patches/series missing, although 3.0 (quilt) is designated in debian/source/format, quilt is not working normally. So, as a result, bug#670316 is reverted and FTBFS on s390x and ppc64 occurs. (Maybe on sparc64, too, but it cannot be sure because of no buildd machine of sparc64's experimental repository now) build logs https://buildd.debian.org/status/package.php?p=shishisuite=experimental http://buildd.debian-ports.org/status/package.php?p=shishisuite=experimental Here is a patch attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd shishi-1.0.2.orig/debian/patches/series shishi-1.0.2/debian/patches/series --- shishi-1.0.2.orig/debian/patches/series 1970-01-01 09:00:00.0 +0900 +++ shishi-1.0.2/debian/patches/series 2013-04-05 18:58:53.0 +0900 @@ -0,0 +1 @@ +64bigendian-ftbfs.diff
Bug#704665: harfbuzz: FTBFS on ppc64: symbols marked with 'D' on powerpc64 instead
Source: harfbuzz
Version: 0.9.14-1
Severity: important
Tags: patch upstream
Hi,
In output of nm utility, symbols are marked with 'D' on powerpc64-linux instead
of 'T',
because powerpc64-linux uses 64-bit PowerPC ELF ABI,
in which function descriptors are found in data section.
http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html
Here is a patch attached.
Buildlogs:
http://buildd.debian-ports.org/status/package.php?p=harfbuzzsuite=experimental
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd harfbuzz-0.9.14.orig/src/check-symbols.sh harfbuzz-0.9.14/src/check-symbols.sh
--- harfbuzz-0.9.14.orig/src/check-symbols.sh 2013-03-19 18:47:13.0 +0900
+++ harfbuzz-0.9.14/src/check-symbols.sh 2013-04-04 16:20:58.0 +0900
@@ -21,7 +21,7 @@
lib=`echo $def | sed 's/[.]def$//;s@.*/@@'`
so=.libs/lib${lib}.so
- EXPORTED_SYMBOLS=`nm $so | grep ' [BCDGINRSTVW] ' | grep -v ' T _fini\\| T _init\\| _fdata\\| _ftext\\| __bss_start\\| __bss_start__\\| __bss_end__\\| _edata\\| _end\\| _bss_end__\\| __end__\' | cut -d' ' -f3`
+ EXPORTED_SYMBOLS=`nm $so | grep ' [BCDGINRSTVW] ' | grep -v ' T\|D _fini\\| T\|D _init\\| _fdata\\| _ftext\\| __bss_start\\| __bss_start__\\| __bss_end__\\| _edata\\| _end\\| _bss_end__\\| __end__\' | cut -d' ' -f3`
if test -f $so; then
Bug#704673: libccid: typo of Product ID for SCR3310-NTTCom USB SmartCard Reader in 92_pcscd_ccid.rules
Package: libccid
Version: 1.4.9-1
Severity: important
Tags: patch upstream sid
SCR3310-NTTCom USB SmartCard Reader was revert to be supported from 1.4.8-1,
but in src/92_pcscd_ccid.rules, SCR3310-NTTCom USB SmartCard Reader and
SCR331-DI USB Smart Card Reader are confused at Product ID.
cf. readers/supported_readers.txt
Line 290: 0x04E6:0x511A:NTT Communications Corp. SCR3310-NTTCom USB SmartCard
Reader
Line 339: 0x04E6:0x5120:SCM Microsystems Inc. SCR331-DI USB Smart Card Reader
So, SCR3310-NTTCom USB SmartCard Reader cannot be used now.
Here is a patch attached.
Regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
--- ccid-1.4.9.orig/src/92_pcscd_ccid.rules 2012-06-08 23:17:11.0 +0900
+++ ccid-1.4.9/src/92_pcscd_ccid.rules 2013-04-04 20:49:02.0 +0900
@@ -29,7 +29,9 @@
ATTRS{idVendor}==413c, ATTRS{idProduct}==2100, GROUP=pcscd
# MySmartPad.txt
ATTRS{idVendor}==09be, ATTRS{idProduct}==0002, GROUP=pcscd
-# SCR331-DI-NTTCom.txt
+# SCR3310-NTTCom USB SmartCard Reader
+ATTRS{idVendor}==04e6, ATTRS{idProduct}==511a, GROUP=pcscd
+# SCR331-DI USB Smart Card Reader
ATTRS{idVendor}==04e6, ATTRS{idProduct}==5120, GROUP=pcscd
# SCR331-DI.txt
ATTRS{idVendor}==04e6, ATTRS{idProduct}==5111, GROUP=pcscd
Bug#701059: [Pkg-haskell-maintainers] Bug#701059: haskell-conduit: FTBFS: test failure form doctest adopted
Joachim Breitner wrote: Am Donnerstag, den 21.02.2013, 13:10 +0900 schrieb Debian ppc64 build daemon: Build test of haskell-conduit fails form ver. 0.5.5 which adopted doctest. http://buildd.debian-ports.org/status/logs.php?pkg=haskell-conduitarch=ppc64 Unfortunately, because transitions of ghc is not applied to experimental repository, this error is not checked at present except on ppc64 port. https://buildd.debian.org/status/package.php?p=haskell-conduitsuite=experimental http://buildd.debian-ports.org/status/package.php?p=haskell-conduitsuite=experimental So, since it may be a bug peculiar to doctest on ppc64 port, this is reported by Severity: important. doctest requires GHCi, which is not supported on all architectures. The cleanest fix would be if doctest would detect this situation and fail gracefully: https://github.com/sol/doctest-haskell/issues/46 OK. This bug is under jurisdiction of haskell-doctest. Although it can be understood that this bug should be solved at haskell-doctest, if it is taken into consideration that GHCi is supporting architectures only amd64, i386, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc, sparc, powerpcspe, and not supporting official armel, armhd, ia64, mips, mipsel, s390, s390x, and unofficial alpha, hppa, m68k, ppc64, sh4, sparc64, x32, it may be worthy of considering avoiding the test by doctest. Since libghc-conduit-dev is build-depended from many other haskell packages, it blocks building many packages now. http://buildd.debian-ports.org/status/architecture.php?a=ppc64suite=experimental If another wishlist BTS to haskell-conduit about this is needed, shall I post it? Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#701059: [Pkg-haskell-maintainers] Bug#701059: Bug#701059: haskell-conduit: FTBFS: test failure form doctest adopted
Joachim Breitner wrote: Am Freitag, den 22.02.2013, 21:09 +0900 schrieb Hiroyuki Yamamoto: Joachim Breitner wrote: Am Donnerstag, den 21.02.2013, 13:10 +0900 schrieb Debian ppc64 build daemon: Build test of haskell-conduit fails form ver. 0.5.5 which adopted doctest. http://buildd.debian-ports.org/status/logs.php?pkg=haskell-conduitarch=ppc64 Unfortunately, because transitions of ghc is not applied to experimental repository, this error is not checked at present except on ppc64 port. https://buildd.debian.org/status/package.php?p=haskell-conduitsuite=experimental http://buildd.debian-ports.org/status/package.php?p=haskell-conduitsuite=experimental So, since it may be a bug peculiar to doctest on ppc64 port, this is reported by Severity: important. doctest requires GHCi, which is not supported on all architectures. The cleanest fix would be if doctest would detect this situation and fail gracefully: https://github.com/sol/doctest-haskell/issues/46 OK. This bug is under jurisdiction of haskell-doctest. Although it can be understood that this bug should be solved at haskell-doctest, if it is taken into consideration that GHCi is supporting architectures only amd64, i386, hurd-i386, kfreebsd-amd64, kfreebsd-i386, powerpc, sparc, powerpcspe, and not supporting official armel, armhd, ia64, mips, mipsel, s390, s390x, and unofficial alpha, hppa, m68k, ppc64, sh4, sparc64, x32, it may be worthy of considering avoiding the test by doctest. Yes, but it should be avoided centrally, i.e. in doctest itself. No need to encode the information “doctest needs GHCi” in every packages that uses doctest. Since libghc-conduit-dev is build-depended from many other haskell packages, it blocks building many packages now. http://buildd.debian-ports.org/status/architecture.php?a=ppc64suite=experimental If another wishlist BTS to haskell-conduit about this is needed, shall I post it? no need, as there is no change to conduit required. I’ll just upload the new doctest as soon as it is released. OK. I'll give-back to build haskell-conduit on ppc64 as soon as new haskell-doctest built. But it is surely a problem that GHCi's supporting architectures are very few, only Intel architectures, 32-bit PowerPC, and 32-bit SPARC. These days, there is a tendency that haskell packages depending on ghc-ghci increase, it has been really troubled a little. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694933: [Pkg-haskell-maintainers] Bug#694933: haskell-warp: FTBFS: unsatisfiable build-dependency: libghc-blaze-builder-conduit-dev ( 0.5)
Hi, (2012/12/13 17:34), Joachim Breitner wrote: Am Donnerstag, den 13.12.2012, 09:15 +0100 schrieb Ralf Treinen: libghc-blaze-builder-conduit-dev package is ver. 0.5.0.1.is.really.0.4.0.2-1 on sid now. As far as I (and dose-builddebcheck) can see, the build-dependency is satisfiable in testing alone. An installation set found by dose-builddebcheck is attached to this mail. Hence, this bug should be tagged as sid. Do you agree? yes, this is a but that exists only in unstable; the Haskell packages in testing should be in good shape. OK, I agree, too. I tried to attach the tag of wheezy-ignore at first, but since this tag should not be used except a release manager, it was not be attached. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695487: haskell-vector: FTBFS: unsatisfiable build-dependency on experimental: libghc-primitive-dev ( 0.5) haskell-devscripts (= 0.8.13)
Source: haskell-vector Version: 0.9.1-3 Severity: serious Justification: FTBFS by unsatisfiable build-dependency libghc-primitive-dev ( 0.5) is unsatisfiable now. libghc-primitive-dev package is ver. 0.5.0.1-1 on on experimental (haskell-devscripts (= 0.8.13)) after 2012-12-02. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695067: mesa: FTBFS on ppc64: symbols marked with 'D' on powerpc64 instead of 'T'
(2012-12-07 20:38 +0100), Julien Cristau wrote: Hi, Hi, In output of nm utility, symbols are marked with 'D' on powerpc64-linux instead of 'T'. Here is a patch and a buildlog attached. http://buildd.debian-ports.org/status/package.php?p=mesasuite=sid Sending a 3M attachment means your mail never makes it anywhere, this is less than helpful. Oh, sorry, I only wanted to show that it can build satisfactorily. Also, please: - explain why nm is being different on ppc64 than everywhere else 32-bit PowerPC Linux (powerpc port) uses SVR4 ABI, but 64-bit PowerPC Linux (ppc64 port) uses 64-bit PowerPC ELF ABI. http://refspecs.linuxfoundation.org/ELF/ppc64/PPC-elf64abi.html In 64-bit PowerPC ELF ABI, function descriptors are found in data section. - explain why we should be building the vmware driver on ppc64 Do you ask me for the justification for existence of libxatracker1 package in mesa source? - if you think it still makes sense, send the patch upstream to mesa-...@lists.freedesktop.org Hmmm, In order to get maintainers' refereeing and judgment that this patch should be sent to upstream, I contributed to BTS. Do you say that it shoudn't be sent to upstream? Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#695067: mesa: FTBFS on ppc64: symbols marked with 'D' on powerpc64 instead of 'T'
(2012-12-08 00:20 +0100), Julien Cristau wrote: - explain why we should be building the vmware driver on ppc64 Do you ask me for the justification for existence of libxatracker1 package in mesa source? I guess it doesn't make much sense on non-x86, indeed. I think so, too, but FTBFS on ppc64 is no good. So, I don't care that maintainers decide whether this patch should be forwarded to upstream or not. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694933: haskell-warp: FTBFS: unsatisfiable build-dependency: libghc-blaze-builder-conduit-dev ( 0.5)
Source: haskell-warp Version: 1.2.1.1-1 Severity: serious Justification: FTBFS by unsatisfiable build-dependency libghc-blaze-builder-conduit-dev package is ver. 0.5.0.1.is.really.0.4.0.2-1 on sid now. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#694030: skytools3: FTBFS: unsatisfiable build-dependency: postgresql-server-dev-8.4
Source: skytools3 Version: 3.0~rc1-2 Severity: serious Justification: FTBFS postgresql-server-dev-8.4 is not provided from postgresql-8.4 8.4.12-2. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#423934: systemtap: please support other architectures
Hi,
(2012-11-21 22:56 +0200), Timo Juhani Lindfors wrote:
Hiroyuki Yamamoto yama1...@gmail.com writes:
added ppc64 to debian/control) can build on ppc64.
Here is a buildlog attached.
Build log alone does not unfortunately tell that much about whether the
package actually works. We don't run testsuite during build since it
loads kernel modules and buildds don't like that.
You can run the testsuite if you install systemtap package and then
apt-get source systemtap
cd systemtap-*
touch -d @0 stap
./configure --prefix=/usr
make installcheck
The results should be in the file testsuite/systemtap.sum.
I run it in test chroot directory, but it made no testsuite/systemtap.sum file.
--
/systemtap/systemtap-1.7# make installcheck
if test \! -e /usr/bin/stap; then \
echo /usr/bin/stap doesn\'t exist, run make install; \
exit -1; \
fi; \
if test ./stap -nt /usr/bin/stap; then \
echo /usr/bin/stap is not recent, run make install; \
exit -1; \
fi;
make -C testsuite installcheck RUNTESTFLAGS=
make[1]: Entering directory `/systemtap/systemtap-1.7/testsuite'
Making a new site.exp file...
rmmod uprobes 2/dev/null
make[1]: [installcheck] Error 1 (ignored)
make check-DEJAGNU RUNTESTFLAGS= --tool_opts \'install \'
make[2]: Entering directory `/systemtap/systemtap-1.7/testsuite'
srcdir=`CDPATH=${ZSH_VERSION+.}: cd . pwd`; export srcdir; \
EXPECT=expect; export EXPECT; \
runtest=env LANG=C SYSTEMTAP_TESTREMOTES= SYSTEMTAP_TESTAPPS=
SYSTEMTAP_RUNTIME=/usr/share/systemtap/runtime
SYSTEMTAP_TAPSET=/usr/share/systemtap/tapset LD_LIBRARY_PATH=/usr/lib/systemtap
CRASH_LIBDIR=/usr/lib/systemtap PATH=/usr/bin:$PATH SYSTEMTAP_PATH=/usr/bin
SYSTEMTAP_INCLUDES=/usr/include PKGLIBDIR=/usr/libexec/systemtap ./execrc
runtest; \
if /bin/bash -c $runtest --version /dev/null 21; then \
exit_status=0; l='systemtap'; for tool in $l; do \
if $runtest --tool $tool --tool_opts \'\' --srcdir $srcdir
--tool_opts \'install \'; \
then :; else exit_status=1; fi; \
done; \
else echo WARNING: could not find \`runtest' 12; :;\
fi; \
exit $exit_status
kernel location: /boot/vmlinux-3.2.0-4-powerpc64
kernel version: 3.2.0-4-powerpc64
systemtap location: /usr/bin/stap
systemtap version: version 1.7/0.153 Debian version 1.7-1
gcc location: /usr/bin/gcc
gcc version: gcc (Debian 4.6.3-12) 4.6.3
failed systemtap kernel-debuginfo smoke test:
semantic error: no match while resolving probe point syscall.open
Pass 2: analysis failed. Try again with another '--vp 01' option.
aborting testing.
make[2]: Leaving directory `/systemtap/systemtap-1.7/testsuite'
if test -n ; then mail systemtap.sum; fi
make[1]: Leaving directory `/systemtap/systemtap-1.7/testsuite'
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#423934: systemtap: please support other architectures
(2012-11-22 00:27 +0200), Timo Juhani Lindfors wrote: Hi, Hiroyuki Yamamoto yama1...@gmail.com writes: semantic error: no match while resolving probe point syscall.open Pass 2: analysis failed. Try again with another '--vp 01' option. Does running http://lindi.iki.fi/lindi/systemtap/diagnose-error-cases.bash give any insight on this one? I cannot understand what you want, but dbg package of linux-image is provided only on amd64, i386, s390, and s390x ports. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#693590: rtaudio: FTBFS on ppc64: Please add powerpc64 support to config/config.sub
Source: rtaudio Version: 4.0.10~ds0-2 Severity: normal Tags: patch upstream Justification: FTBFS on ppc64 Hi, Please add powerpc64 support to config/config.sub. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=rtaudiosuite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd rtaudio-4.0.10~ds0.orig/config/config.sub rtaudio-4.0.10~ds0/config/config.sub --- rtaudio-4.0.10~ds0.orig/config/config.sub 2008-11-22 12:32:52.0 +0900 +++ rtaudio-4.0.10~ds0/config/config.sub 2012-11-18 18:15:33.0 +0900 @@ -225,7 +225,7 @@ | alpha | alphaev[4-8] | alphaev56 | alphapca5[67] \ | alphaev6[78] \ | we32k | ns16k | clipper | i370 | sh | sh[34] \ - | powerpc | powerpcle \ + | powerpc | powerpc64 | powerpcle \ | 1750a | dsp16xx | pdp10 | pdp11 \ | mips16 | mips64 | mipsel | mips64el \ | mips64orion | mips64orionel | mipstx39 | mipstx39el \ @@ -271,7 +271,7 @@ | alphaev6[78]-* \ | we32k-* | cydra-* | ns16k-* | pn-* | np1-* | xps100-* \ | clipper-* | orion-* \ - | sparclite-* | pdp10-* | pdp11-* | sh-* | powerpc-* | powerpcle-* \ + | sparclite-* | pdp10-* | pdp11-* | sh-* | powerpc-* | powerpc64-* | powerpcle-* \ | sparc64-* | sparcv9-* | sparcv9b-* | sparc86x-* \ | mips16-* | mips64-* | mipsel-* \ | mips64el-* | mips64orion-* | mips64orionel-* \ @@ -721,6 +721,10 @@ ;; ppc-*) basic_machine=powerpc-`echo $basic_machine | sed 's/^[^-]*-//'` ;; + ppc64) basic_machine=powerpc64-unknown + ;; + ppc64-*) basic_machine=powerpc64-`echo $basic_machine | sed 's/^[^-]*-//'` + ;; ppcle | powerpclittle | ppc-le | powerpc-little) basic_machine=powerpcle-unknown ;;
Bug#693592: rtmidi: FTBFS on ppc64: Please add powerpc64 support to config/config.sub
Source: rtmidi Version: 1.0.15~ds0-2 Severity: normal Tags: patch upstream Justification: FTBFS on ppc64 Hi, Please add powerpc64 support to config/config.sub. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=rtmidisuite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd rtmidi-1.0.15~ds0.orig/config/config.sub rtmidi-1.0.15~ds0/config/config.sub --- rtmidi-1.0.15~ds0.orig/config/config.sub 2012-11-18 19:13:19.0 +0900 +++ rtmidi-1.0.15~ds0/config/config.sub 2012-11-18 19:15:11.0 +0900 @@ -225,7 +225,7 @@ | alpha | alphaev[4-8] | alphaev56 | alphapca5[67] \ | alphaev6[78] \ | we32k | ns16k | clipper | i370 | sh | sh[34] \ - | powerpc | powerpcle \ + | powerpc | powerpc64 | powerpcle \ | 1750a | dsp16xx | pdp10 | pdp11 \ | mips16 | mips64 | mipsel | mips64el \ | mips64orion | mips64orionel | mipstx39 | mipstx39el \ @@ -271,7 +271,7 @@ | alphaev6[78]-* \ | we32k-* | cydra-* | ns16k-* | pn-* | np1-* | xps100-* \ | clipper-* | orion-* \ - | sparclite-* | pdp10-* | pdp11-* | sh-* | powerpc-* | powerpcle-* \ + | sparclite-* | pdp10-* | pdp11-* | sh-* | powerpc-* | powerpc64-* | powerpcle-* \ | sparc64-* | sparcv9-* | sparcv9b-* | sparc86x-* \ | mips16-* | mips64-* | mipsel-* \ | mips64el-* | mips64orion-* | mips64orionel-* \ @@ -721,6 +721,10 @@ ;; ppc-*) basic_machine=powerpc-`echo $basic_machine | sed 's/^[^-]*-//'` ;; + ppc64) basic_machine=powerpc64-unknown + ;; + ppc64-*) basic_machine=powerpc64-`echo $basic_machine | sed 's/^[^-]*-//'` + ;; ppcle | powerpclittle | ppc-le | powerpc-little) basic_machine=powerpcle-unknown ;;
Bug#693590: FTBFS on ppc64: Please add powerpc64 support to config/config.sub
Hi, (2012-11-18 19:56 +), Alessio Treglia wrote: Hello, thanks so much for your great work! Have you already forwarded the patches to upstream? No, because it's better to be forwarded the patches to upstream by maintainers after refereeing. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#423934: systemtap: please support other architectures
Hi, I think that systemtap (ver. 1.7) supports s390x and ppc64, too. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#692893: fpc: FTBFS on ppc64: Please support ppc64
Source: fpc
Version: 2.6.0-6
Severity: normal
Tags: patch upstream
Justification: FTBFS on ppc64
Hi,
Please support ppc64.
Here is a patch attached.
http://buildd.debian-ports.org/status/package.php?p=fpcsuite=sid
About install/man/man1/ppcppc64.1, it is better to contact the upstream,
since a manual is considered to be an inclusion failure.
Best regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd fpc-2.6.0.orig/debian/control.in fpc-2.6.0/debian/control.in
--- fpc-2.6.0.orig/debian/control.in 2012-11-09 21:09:39.0 +0900
+++ fpc-2.6.0/debian/control.in 2012-11-10 00:27:00.0 +0900
@@ -53,7 +53,7 @@
the Lazarus IDE.
Package: fp-compiler${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), binutils
Recommends: fp-utils${PACKAGESUFFIX} (= ${binary:Version})
Suggests: fp-docs${PACKAGESUFFIX} (= ${source:Upstream-Version})
@@ -76,7 +76,7 @@
This package contains the command line compiler.
Package: fp-ide${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), ${shlibs:Depends}
Recommends: fp-utils${PACKAGESUFFIX} (= ${binary:Version})
Suggests: fp-docs${PACKAGESUFFIX} (= ${source:Upstream-Version})
@@ -99,7 +99,7 @@
has an internal compiler.
Package: fp-utils${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}
Recommends: fp-compiler${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-utils
@@ -144,7 +144,7 @@
format.
Package: fp-units-rtl${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}
Recommends: fp-compiler${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-rtl, fpc-abi-${source:Upstream-Version}
@@ -161,7 +161,7 @@
This package contains the Runtime Libraries for the Free Pascal Compiler.
Package: fp-units-base${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-base
Breaks: fp-units-base (= 2.4.0-3)
@@ -181,7 +181,7 @@
- ZLib
Package: fp-units-fcl${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), fp-units-base${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-fcl
Breaks: fp-units-fcl (= 2.4.0-3)
@@ -197,7 +197,7 @@
This package contains the Free Component Library for the Free Pascal Compiler.
Package: fp-units-fv${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-fv
Breaks: fp-units-fv (= 2.4.0-3)
@@ -213,7 +213,7 @@
This package contains the Free Vision units for the Free Pascal Compiler.
Package: fp-units-gtk${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), fp-units-fcl${PACKAGESUFFIX} (= ${binary:Version}), libgtk2.0-dev
Provides: fp-units-gtk
Breaks: fp-units-gtk (= 2.4.0-3)
@@ -230,7 +230,7 @@
programs with GTK+ 1.2.
Package: fp-units-gtk2${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), fp-units-fcl${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-gtk2
Breaks: fp-units-gtk2 (= 2.4.0-3)
@@ -247,7 +247,7 @@
programs with GTK+ 2.x.
Package: fp-units-gnome1${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version}), fp-units-gtk${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-gnome1
Breaks: fp-units-gnome1 (= 2.4.0-3)
@@ -264,7 +264,7 @@
programs for GNOME 1.
Package: fp-units-db${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf ppc64
Depends: ${misc:Depends}, fp-units-rtl${PACKAGESUFFIX} (= ${binary:Version})
Provides: fp-units-db
Breaks: fp-units-db (= 2.4.0-3)
@@ -287,7 +287,7 @@
- SQLite
Package: fp-units-gfx${PACKAGESUFFIX}
-Architecture: i386 powerpc sparc amd64 armel armhf
+Architecture: i386 powerpc sparc amd64 armel armhf
Bug#685060: corosync: fails to install and remove: corosync-notifyd cannot start and stop
reopen 685060 found 685060 1.4.4-2 retitle 685060 corosync: fails to install and remove: corosync-notifyd cannot start and stop severity 685060 grave Changing default to defaults in /var/lib/dpkg/info/corosync.postinst is completed, but solving the problem at corosync-notifyd which was reported by Rain Maker is not completed. Because corosync-notifyd cannot start and stop, installing of corosync does not complete, and corosync becomes uninstalable. The package can remove only by adding exit 0 to the 2nd line of /var/lib/dpkg/info/corosync.prerm being different from 1.4.4-1. -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682521: haskell-data-accessor-template: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-data-accessor-template Version: 0.2.1.9-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682522: haskell-path-pieces: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-path-pieces Version: 0.1.0-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682523: haskell-haxr: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-haxr Version: 3000.8.5-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682525: haskell-shakespeare: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-shakespeare Version: 1.0.0.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682524: haskell-shakespeare-text: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-shakespeare-text Version: 1.0.0.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682526: haskell-shakespeare-i18n: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-shakespeare-i18n Version: 1.0.0.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682528: haskell-persistent-template: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-persistent-template Version: 0.9.0.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682527: haskell-yesod-routes: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-yesod-routes Version: 1.0.1.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682531: haskell-hamlet: FTBFS:
Source: haskell-hamlet Version: 1.0.1.3-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682533: haskell-happstack-server: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-happstack-server Version: 7.0.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682534: haskell-yesod-auth: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-yesod-auth Version: 1.0.2.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682535: haskell-clientsession: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-clientsession Version: 0.7.5-3 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682536: haskell-yesod-static: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-yesod-static Version: 1.0.0.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682537: haskell-fclabels: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-fclabels Version: 1.1.3-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682539: haskell-cabal-file-th: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-cabal-file-th Version: 0.2.2-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682542: haskell-file-embed: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-file-embed Version: 0.0.4.4-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682541: haskell-test-framework-th-prime: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-test-framework-th-prime Version: 0.0.5-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682545: haskell-options: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-options Version: 0.1.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682544: haskell-test-framework-th: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-test-framework-th Version: 0.2.2-5 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682546: haskell-boomerang: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-boomerang Version: 1.3.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682547: haskell-chell: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-chell Version: 0.3-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682548: haskell-postgresql-simple: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-postgresql-simple Version: 0.1.4.3-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682549: haskell-hledger: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-hledger Version: 0.18.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682550: haskell-hledger-web: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
Source: haskell-hledger-web Version: 0.18.1-1 Severity: serious Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#682527: haskell-yesod-routes: FTBFS: Don't use ghc-ghci virtual-package-name on Build-Depends
(2012-07-24 02:30 +), Clint Adams wrote: On Tue, Jul 24, 2012 at 12:05:28AM +0900, Hiroyuki Yamamoto wrote: Don't use ghc-ghci virtual-package-name on Build-Depends, because it has not been allowed yet by Debian-Policy to use the virtual-package-name of ghc-ghci. How is this a FTBFS? Of course, this bug must be FTBFS because the package which cannot exist according to the architecture is specified. In Debian, it is usual to not any but listed the architecture to build. But in order to detain the architecture which is not supporting ghci to the status of BD-Uninstallable, I was explained when it had become intentionally so by Haskell Policy. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#670250: geotranz: FTBFS on ppc64: Please support ppc64
Source: geotranz Version: 3.1-2.1 Severity: wishlist Tags: patch Please support ppc64. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=geotranzsuite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd geotranz-3.1.orig/debian/libgeotranz3.1.symbols geotranz-3.1/debian/libgeotranz3.1.symbols --- geotranz-3.1.orig/debian/libgeotranz3.1.symbols 2011-03-12 13:25:23.0 +0900 +++ geotranz-3.1/debian/libgeotranz3.1.symbols 2012-04-24 21:03:55.0 +0900 @@ -14,6 +14,10 @@ WGS72_Ellipsoid_Code@Base 3.1 WGS84_Datum_Code@Base 3.1 WGS84_Ellipsoid_Code@Base 3.1 + (arch=ppc64)_Z10readBinaryPvmmP8_IO_FILE@Base 3.1 + (arch=ppc64)_Z9swapBytesPvmm@Base 3.1 + (arch=ppc64)_ZNSt6vectorIPN3MSP3CCS5DatumESaIS3_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS3_S5_EEmRKS3_@Base 3.1 + (arch=ppc64)_ZNSt6vectorIPN3MSP3CCS9EllipsoidESaIS3_EE14_M_fill_insertEN9__gnu_cxx17__normal_iteratorIPS3_S5_EEmRKS3_@Base 3.1 datumLibraryImplementationCleanerInstance@Base 3.1 ellipsoidLibraryImplementationCleanerInstance@Base 3.1 geoidLibraryCleanerInstance@Base 3.1 @@ -248,7 +252,7 @@ (c++)MSP::CCS::Datum::name() const@Base 3.1 (c++)MSP::CCS::Datum::northLatitude() const@Base 3.1 (c++)MSP::CCS::Datum::southLatitude() const@Base 3.1 - (c++|optional)MSP::CCS::Datum** std::__copy_move_afalse, MSP::CCS::Datum**, MSP::CCS::Datum**(MSP::CCS::Datum**, MSP::CCS::Datum**, MSP::CCS::Datum**)@Base 3.1 + (c++|optional|arch=!ppc64)MSP::CCS::Datum** std::__copy_move_afalse, MSP::CCS::Datum**, MSP::CCS::Datum**(MSP::CCS::Datum**, MSP::CCS::Datum**, MSP::CCS::Datum**)@Base 3.1 (c++)MSP::CCS::Datum::userDefined() const@Base 3.1 (c++)MSP::CCS::Datum::westLongitude() const@Base 3.1 (c++)MSP::CCS::Eckert4::convertFromGeodetic(MSP::CCS::GeodeticCoordinates*)@Base 3.1 @@ -318,7 +322,7 @@ (c++)MSP::CCS::EllipsoidParameters::setSemiMajorAxis(double)@Base 3.1 (c++)MSP::CCS::Ellipsoid::semiMajorAxis() const@Base 3.1 (c++)MSP::CCS::Ellipsoid::semiMinorAxis() const@Base 3.1 - (c++|optional)MSP::CCS::Ellipsoid** std::__copy_move_afalse, MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**(MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**)@Base 3.1 + (c++|optional|arch=!ppc64)MSP::CCS::Ellipsoid** std::__copy_move_afalse, MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**(MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**, MSP::CCS::Ellipsoid**)@Base 3.1 (c++)MSP::CCS::Ellipsoid::userDefined() const@Base 3.1 (c++)MSP::CCS::EquidistantCylindrical::convertFromGeodetic(MSP::CCS::GeodeticCoordinates*)@Base 3.1 (c++)MSP::CCS::EquidistantCylindrical::convertToGeodetic(MSP::CCS::MapProjectionCoordinates*)@Base 3.1 @@ -944,7 +948,7 @@ (c++)multiply(Complex, Complex)@Base 3.1 (c++)oneMinusSqr(double)@Base 3.1 (c++)polyCoeffTimesSine(double, double, double)@Base 3.1 - (c++|arch=!s390 !alpha !amd64 !kfreebsd-amd64 !ia64)readBinary(void*, unsigned int, unsigned int, _IO_FILE*)@Base 3.1 + (c++|arch=!s390 !alpha !amd64 !kfreebsd-amd64 !ia64 !ppc64)readBinary(void*, unsigned int, unsigned int, _IO_FILE*)@Base 3.1 (c++|arch=s390 alpha amd64 kfreebsd-amd64 ia64)readBinary(void*, unsigned long, unsigned long, _IO_FILE*)@Base 3.1 (c++)roundBNG(double)@Base 3.1 (c++)roundGEOREF(double)@Base 3.1 @@ -965,13 +969,13 @@ (c++)std::_Rb_treeint, std::pairint const, MSP::CCS::TransverseMercator*, std::_Select1ststd::pairint const, MSP::CCS::TransverseMercator* , std::lessint, std::allocatorstd::pairint const, MSP::CCS::TransverseMercator* ::_M_insert_unique_(std::_Rb_tree_const_iteratorstd::pairint const, MSP::CCS::TransverseMercator* , std::pairint const, MSP::CCS::TransverseMercator* const)@Base 3.1 (c++)std::vectorMSP::CCS::Accuracy*, std::allocatorMSP::CCS::Accuracy* ::_M_insert_aux(__gnu_cxx::__normal_iteratorMSP::CCS::Accuracy**, std::vectorMSP::CCS::Accuracy*, std::allocatorMSP::CCS::Accuracy* , MSP::CCS::Accuracy* const)@Base 3.1 (c++)std::vectorMSP::CCS::CoordinateTuple*, std::allocatorMSP::CCS::CoordinateTuple* ::_M_insert_aux(__gnu_cxx::__normal_iteratorMSP::CCS::CoordinateTuple**, std::vectorMSP::CCS::CoordinateTuple*, std::allocatorMSP::CCS::CoordinateTuple* , MSP::CCS::CoordinateTuple* const)@Base 3.1 - (c++|arch=!s390 !alpha !amd64 !kfreebsd-amd64 !ia64)std::vectorMSP::CCS::Datum*, std::allocatorMSP::CCS::Datum* ::_M_fill_insert(__gnu_cxx::__normal_iteratorMSP::CCS::Datum**, std::vectorMSP::CCS::Datum*, std::allocatorMSP::CCS::Datum* , unsigned int, MSP::CCS::Datum* const)@Base 3.1 + (c++|arch=!s390 !alpha !amd64 !kfreebsd-amd64 !ia64 !ppc64)std::vectorMSP::CCS::Datum*, std::allocatorMSP::CCS::Datum* ::_M_fill_insert(__gnu_cxx::__normal_iteratorMSP::CCS::Datum**, std::vectorMSP::CCS::Datum*, std::allocatorMSP::CCS::Datum* , unsigned int, MSP::CCS::Datum* const)@Base 3.1 (c++|arch=s390 alpha amd64 kfreebsd-amd64 ia64)std::vectorMSP::CCS::Datum*, std::allocatorMSP::CCS::Datum* ::_M_fill_insert(__gnu_cxx::__normal_iteratorMSP::CCS
Bug#670251: arpack: FTBFS on ppc64: Please support ppc64
Source: arpack Version: 3.1.0-2 Severity: wishlist Tags: patch Please support ppc64. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=arpacksuite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd arpack-3.1.0.orig/debian/libparpack2.symbols arpack-3.1.0/debian/libparpack2.symbols --- arpack-3.1.0.orig/debian/libparpack2.symbols 2012-03-28 22:42:33.0 +0900 +++ arpack-3.1.0/debian/libparpack2.symbols 2012-04-24 21:19:55.0 +0900 @@ -44,21 +44,21 @@ iset_@Base 2.1 iswap_@Base 2.1 ivout_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_argv_null_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_argvs_null_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_bottom_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_errcodes_ignore_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_in_place_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_status_ignore_@Base 2.1 - (arch=!mips !mipsel !s390 !s390x !sh4 !sparc64)mpi_fortran_statuses_ignore_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb1_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb2_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb3_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb4_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb5_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb6_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb7_@Base 2.1 - (arch=mips mipsel s390 s390x sh4 sparc64)mpifcmb8_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_argv_null_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_argvs_null_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_bottom_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_errcodes_ignore_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_in_place_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_status_ignore_@Base 2.1 + (arch=!mips !mipsel !ppc64 !s390 !s390x !sh4 !sparc64)mpi_fortran_statuses_ignore_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb1_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb2_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb3_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb4_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb5_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb6_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb7_@Base 2.1 + (arch=mips mipsel ppc64 s390 s390x sh4 sparc64)mpifcmb8_@Base 2.1 pcgetv0_@Base 2.1 pclarnv_@Base 2.1 pcmout_@Base 2.1
Bug#670266: hdf5: FTBFS on ppc64: Please support ppc64
Source: hdf5 Version: 1.8.8-9 Severity: wishlist Tags: patch Please support ppc64. Here is a patch attached. http://buildd.debian-ports.org/status/package.php?p=hdf5suite=sid Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd hdf5-1.8.8.orig/debian/libhdf5-7.symbols hdf5-1.8.8/debian/libhdf5-7.symbols --- hdf5-1.8.8.orig/debian/libhdf5-7.symbols 2012-02-24 19:15:58.0 +0900 +++ hdf5-1.8.8/debian/libhdf5-7.symbols 2012-04-24 22:59:03.0 +0900 @@ -2015,7 +2015,7 @@ H5T_conv_ldouble_double@Base 1.8.7 H5T_conv_ldouble_float@Base 1.8.7 H5T_conv_ldouble_int@Base 1.8.7 - (arch=!powerpc !sh4)H5T_conv_ldouble_llong@Base 1.8.7 + (arch=!powerpc !ppc64 !sh4)H5T_conv_ldouble_llong@Base 1.8.7 H5T_conv_ldouble_long@Base 1.8.7 H5T_conv_ldouble_schar@Base 1.8.7 H5T_conv_ldouble_short@Base 1.8.7 @@ -2027,7 +2027,7 @@ H5T_conv_llong_double@Base 1.8.7 H5T_conv_llong_float@Base 1.8.7 H5T_conv_llong_int@Base 1.8.7 - (arch=!powerpc !sh4)H5T_conv_llong_ldouble@Base 1.8.7 + (arch=!powerpc !ppc64 !sh4)H5T_conv_llong_ldouble@Base 1.8.7 H5T_conv_llong_long@Base 1.8.7 H5T_conv_llong_schar@Base 1.8.7 H5T_conv_llong_short@Base 1.8.7 @@ -2107,7 +2107,7 @@ H5T_conv_ullong_float@Base 1.8.7 H5T_conv_ullong_int@Base 1.8.7 H5T_conv_ullong_ldouble@Base 1.8.7 - (arch=!armel !armhf !alpha !sparc !mipsel !powerpc !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 + (arch=!armel !armhf !alpha !sparc !mipsel !powerpc !ppc64 !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 H5T_conv_ullong_llong@Base 1.8.7 H5T_conv_ullong_long@Base 1.8.7 H5T_conv_ullong_schar@Base 1.8.7 diff -Nurd hdf5-1.8.8.orig/debian/libhdf5-mpich2-7.symbols hdf5-1.8.8/debian/libhdf5-mpich2-7.symbols --- hdf5-1.8.8.orig/debian/libhdf5-mpich2-7.symbols 2012-01-31 23:02:05.0 +0900 +++ hdf5-1.8.8/debian/libhdf5-mpich2-7.symbols 2012-04-24 22:16:10.0 +0900 @@ -2056,7 +2056,7 @@ H5T_conv_ldouble_double@Base 1.8.7 H5T_conv_ldouble_float@Base 1.8.7 H5T_conv_ldouble_int@Base 1.8.7 - (arch=!powerpc)H5T_conv_ldouble_llong@Base 1.8.7 + (arch=!powerpc !ppc64)H5T_conv_ldouble_llong@Base 1.8.7 H5T_conv_ldouble_long@Base 1.8.7 H5T_conv_ldouble_schar@Base 1.8.7 H5T_conv_ldouble_short@Base 1.8.7 @@ -2068,7 +2068,7 @@ H5T_conv_llong_double@Base 1.8.7 H5T_conv_llong_float@Base 1.8.7 H5T_conv_llong_int@Base 1.8.7 - (arch=!powerpc)H5T_conv_llong_ldouble@Base 1.8.7 + (arch=!powerpc !ppc64)H5T_conv_llong_ldouble@Base 1.8.7 H5T_conv_llong_long@Base 1.8.7 H5T_conv_llong_schar@Base 1.8.7 H5T_conv_llong_short@Base 1.8.7 @@ -2147,7 +2147,7 @@ H5T_conv_ullong_double@Base 1.8.7 H5T_conv_ullong_float@Base 1.8.7 H5T_conv_ullong_int@Base 1.8.7 - (arch=!mipsel !armel !armhf !alpha !powerpc !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 + (arch=!mipsel !armel !armhf !alpha !powerpc !ppc64 !sh4)H5T_conv_ullong_ldouble@Base 1.8.7 H5T_conv_ullong_llong@Base 1.8.7 H5T_conv_ullong_long@Base 1.8.7 H5T_conv_ullong_schar@Base 1.8.7 diff -Nurd hdf5-1.8.8.orig/debian/libhdf5-openmpi-7.symbols hdf5-1.8.8/debian/libhdf5-openmpi-7.symbols --- hdf5-1.8.8.orig/debian/libhdf5-openmpi-7.symbols 2012-01-18 23:10:07.0 +0900 +++ hdf5-1.8.8/debian/libhdf5-openmpi-7.symbols 2012-04-24 19:52:46.0 +0900 @@ -2055,7 +2055,7 @@ H5T_conv_ldouble_double@Base 1.8.7 H5T_conv_ldouble_float@Base 1.8.7 H5T_conv_ldouble_int@Base 1.8.7 - (arch=!powerpc)H5T_conv_ldouble_llong@Base 1.8.7 + (arch=!powerpc !ppc64)H5T_conv_ldouble_llong@Base 1.8.7 H5T_conv_ldouble_long@Base 1.8.7 H5T_conv_ldouble_schar@Base 1.8.7 H5T_conv_ldouble_short@Base 1.8.7 @@ -2067,7 +2067,7 @@ H5T_conv_llong_double@Base 1.8.7 H5T_conv_llong_float@Base 1.8.7 H5T_conv_llong_int@Base 1.8.7 - (arch=!powerpc)H5T_conv_llong_ldouble@Base 1.8.7 + (arch=!powerpc !ppc64)H5T_conv_llong_ldouble@Base 1.8.7 H5T_conv_llong_long@Base 1.8.7 H5T_conv_llong_schar@Base 1.8.7 H5T_conv_llong_short@Base 1.8.7 @@ -2146,7 +2146,7 @@ H5T_conv_ullong_double@Base 1.8.7 H5T_conv_ullong_float@Base 1.8.7 H5T_conv_ullong_int@Base 1.8.7 - (arch=!powerpc !armel !armhf !alpha)H5T_conv_ullong_ldouble@Base 1.8.7 + (arch=!powerpc !armel !armhf !alpha !ppc64)H5T_conv_ullong_ldouble@Base 1.8.7 H5T_conv_ullong_llong@Base 1.8.7 H5T_conv_ullong_long@Base 1.8.7 H5T_conv_ullong_schar@Base 1.8.7
Bug#670251: arpack: FTBFS on ppc64: Please support ppc64
(2012-04-25 02:41 +0200), Sylvestre Ledru wrote: Le 24/04/2012 14:34, Hiroyuki Yamamoto a écrit : Sorry but you patch breaks the current build under amd64 : It's very strange. In my pbuilder environment, it can be building satisfactorily on amd64, too. dpkg-gensymbols: warning: debian/libparpack2/DEBIAN/symbols doesn't match completely debian/libparpack2.symbols --- debian/libparpack2.symbols (libparpack2_3.1.0-3_amd64) +++ dpkg-gensymbols5cM9XL 2012-04-24 14:57:50.318578745 + (snip) + mpipriv_@Base 3.1.0-3 If it was true, you could not build original ver. 3.1.0-2 source itself, too. Regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#669940: cityhash: FTBFS on ppc64: Please support ppc64
Source: cityhash Version: 1.0.3-1 Severity: wishlist Tags: patch Please support ppc64. Here is a patch attached. Best regards, -- Hiroyuki Yamamoto A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC diff -Nurd cityhash-1.0.3.orig/debian/libcityhash0.symbols cityhash-1.0.3/debian/libcityhash0.symbols --- cityhash-1.0.3.orig/debian/libcityhash0.symbols 2011-10-09 23:53:15.0 +0900 +++ cityhash-1.0.3/debian/libcityhash0.symbols 2012-04-22 15:30:29.0 +0900 @@ -1,5 +1,5 @@ libcityhash.so.0 libcityhash0 #MINVER# # 64bit architectures symbols -(arch=alpha amd64 kfreebsd-amd64 ia64 s390x)#include libcityhash0.symbols.64bit +(arch=alpha amd64 kfreebsd-amd64 ia64 ppc64 s390x)#include libcityhash0.symbols.64bit # 32bit architectures symbols -(arch=!alpha !amd64 !kfreebsd-amd64 !ia64 !s390x)#include libcityhash0.symbols.32bit +(arch=!alpha !amd64 !kfreebsd-amd64 !ia64 !ppc64 !s390x)#include libcityhash0.symbols.32bit
Bug#669944: mozjs: FTBFS on ppc64: Please support ppc64
Source: mozjs
Version: 1.8.5-1.0.0+dfsg-3
Severity: wishlist
Tags: patch
Please support ppc64.
Here is a patch attached.
http://buildd.debian-ports.org/status/package.php?p=mozjssuite=sid
Best regards,
--
Hiroyuki Yamamoto
A75D B285 7050 4BF9 AEDA 91AC 3A10 59C6 5203 04DC
diff -Nurd mozjs-1.8.5-1.0.0+dfsg.orig/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.orig/debian/libmozjs185-1.0.symbols 2012-01-25 08:11:56.0 +0900
+++ mozjs-1.8.5-1.0.0+dfsg/debian/libmozjs185-1.0.symbols 2012-04-22 17:01:42.0 +0900
@@ -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 !ia64 !kfreebsd-amd64 !s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPl@Base 1.8.5-1.0.0+dfsg
+ (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z12js_EnumerateP9JSContextP8JSObject11JSIterateOpPN2js5ValueEPi@Base 1.8.5-1.0.0+dfsg
+ (arch=amd64 ia64 kfreebsd-amd64 ppc64 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 !ia64 !kfreebsd-amd64 !s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z15js_FindPropertyP9JSContextlPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z15js_FindPropertyP9JSContextiPP8JSObjectS3_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=amd64 ia64 kfreebsd-amd64 ppc64 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,10 +546,11 @@
_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 !ia64 !kfreebsd-amd64 !s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
- (arch=amd64 ia64 kfreebsd-amd64 s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectlPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z17js_LookupPropertyP9JSContextP8JSObjectiPS2_PP10JSProperty@Base 1.8.5-1.0.0+dfsg
+ (arch=amd64 ia64 kfreebsd-amd64 ppc64 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
+ (subst|arch=!ppc64)_Z18JS_StructuredCloneP9JSContext{uint64_t}P{uint64_t}PFP8JSObjectS0_P23JSStructuredCloneReaderjjPvEPK26JSStructuredCloneCallbacksS6_@Base 1.8.5-1.0.0+dfsg
+ (arch=ppc64)_Z18JS_StructuredCloneP9JSContextmPmPFP8JSObjectS0_P23JSStructuredCloneReaderjjPvEPK26JSStructuredCloneCallbacksS6_@Base 1.8.5-1.0.0+dfsg
_Z18js_ConsumeJSONTextP9JSContextP10JSONParserPKtj12DecodingMode@Base 1.8.5-1.0.0+dfsg
_Z18js_GCThingIsMarkedPvj@Base 1.8.5-1.0.0+dfsg
_Z18js_GetErrorMessagePvPKcj@Base 1.8.5-1.0.0+dfsg
@@ -571,11 +572,12 @@
_Z24js_DateGetMsecSinceEpochP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
(arch=!s390 !s390x)_Z24js_InitTypedArrayClassesP9JSContextP8JSObject@Base 1.8.5-1.0.0+dfsg
_Z24js_IsDensePrimitiveArrayP8JSObject@Base 1.8.5-1.0.0+dfsg
- (subst|arch=!amd64 !ia64 !kfreebsd-amd64 !s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectiiP{uint64_t}@Base 1.8.5-1.0.0+dfsg
+ (subst|arch=!amd64 !ia64 !kfreebsd-amd64 !ppc64 !s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectiiP{uint64_t}@Base 1.8.5-1.0.0+dfsg
(subst|arch=amd64 ia64 kfreebsd-amd64 s390x)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectliP{uint64_t}@Base 1.8.5-1.0.0+dfsg
+ (arch=ppc64)_Z25js_GetterOnlyPropertyStubP9JSContextP8JSObjectliPm@Base 1.8.5-1.0.0+dfsg
_Z27js_CloneDensePrimitiveArrayP9JSContextP8JSObjectPS2_@Base 1.8.5-1.0.0+dfsg
_Z27js_ReportAllocationOverflowP9JSContext@Base 1.8.5-1.0.0+dfsg
- (arch=!ia64 !mips !mipsel !powerpc !s390 !s390x)_Z27js_SetTraceableNativeFailedP9JSContext@Base 1.8.5-1.0.0+dfsg
+ (arch=!ia64 !mips !mipsel !powerpc !ppc64 !s390 !s390x)_Z27js_SetTraceableNativeFailedP9JSContext@Base 1.8.5-1.0.0+dfsg
