Bug#472917: gcc-4.3: FTBFS (ppc64): Please add lib32gfortran3.symbols.ppc64, remove "msoft-float"/"nof" in gcc-multilib64dir and disable ppc64-biarch patch
Andreas Jochens writes:
> Package: gcc-4.3
> Version: 4.3.0-2
> Severity: wishlist
> Tags: patch
>
> Hello,
>
> the current version of gcc-4.3 FTBFS on ppc64. Some small changes are
> necessary to build the gcc-4.3 package on ppc64 (see patch below):
>
> * debian/lib32gfortan3.symbols.ppc64:
> new file with ppc64 specific symbols
>
> * debian/patches/gcc-multilib64dir.dpatch:
> remove "msoft-float" and "nof" from MULTILIB variables
>
> * debian/rules.defs:
> do not apply ppc64-biarch anymore
done in r2965.
> When these three things are fixed, there is still another issue
> with the lib32gomp1 symbols which leads to the following build error:
>
> dh_makeshlibs -plib32gomp1 -V 'lib32gomp1 (>= 4.3)'
> dpkg-gensymbols: warning: some new symbols appeared in the symbols file.
> dpkg-gensymbols: warning: some symbols disappeared in the symbols file.
> dpkg-gensymbols: warning: debian/lib32gomp1/DEBIAN/symbols doesn't match comple$
>
> --- dpkg-gensymbolstynYFy 2008-03-26 15:31:34.000000000 +0000
> +++ dpkg-gensymbolsRJxhFu 2008-03-26 15:31:34.000000000 +0000
> @@ -1,92 +1,180 @@
> libgomp.so.1 lib32gomp1 #MINVER#
> - GOMP_1.0@GOMP_1.0 4.2.1-4
> - GOMP_atomic_end@GOMP_1.0 4.2.1-4
> - GOMP_atomic_start@GOMP_1.0 4.2.1-4
> [...]
> + omp_unset_nest_lock@Base 4.3.0-2
> +#MISSING: 4.3.0-2# omp_unset_nest_lock@OMP_1.0 4.2.1-4
> + omp_unset_nest_lock_@Base 4.3.0-2
> +#MISSING: 4.3.0-2# omp_unset_nest_lock_@OMP_1.0 4.2.1-4
> dh_makeshlibs: command returned error code 256
> make[1]: *** [stamps/08-binary-stamp-lib32gomp] Error 1
> make[1]: Leaving directory `/srv/dbuild/tmp/gcc-4.3-4.3.0'
> make: *** [binary] Error 2
> dpkg-buildpackage: failure: debian/rules binary gave error exit status 2
>
> I do not know how to fix this correctly.
Updated the libgomp symbol files (r2964). Just wondering why the
32bit powerpc build has different symbols, or maybe this is a
configuration error? The universioned omp_unset_nest_lock symbols look
suspicious.
Matthias
Reply to: