Package: gcc-4.4
Version: 4.4.3-7
Severity: wishlist
Hello,
When building cross compilers (only seen on biarch architectures):
Builds are done with:
GCC_TARGET=powerpc DEB_CROSS=yes fakeroot debian/rules control
DEB_CROSS_NO_BIARCH=yes DH_VERBOSE=1 GCC_TARGET=powerpc DEB_CROSS=yes
dpkg-buildpackage -us -uc -rfakeroot
dh_makeshlibs -plib64gomp1-powerpc-cross
rm -f debian/lib64gomp1-powerpc-cross/DEBIAN/shlibs
sed s/-powerpc-cross//g < debian/lib64gomp1-powerpc-cross/DEBIAN/shlibs >
debian/lib64gomp1-powerpc-cross/DEBIAN/shlibs.fixed
/bin/bash: debian/lib64gomp1-powerpc-cross/DEBIAN/shlibs: No such file or
directory
make[1]: *** [stamps/08-binary-stamp-lib64gomp] Error 1
make[1]: Leaving directory `/home/zumbi/buildcross/trunk/test/gcc-4.4-4.4.3'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
There are no files under debian/lib64gomp1-powerpc-cross/usr/lib64/, so
shlibs file is not created and should not be built on a DEB_NO_BIARCH=yes build.
If you workarround this issue, another issues follow:
* Also tries to build lib64fortran3
* Tries to create an existing file and fails:
mkdir: cannot create directory `debian/libstdc++6-powerpc-cross-deps': File
exists
* Tries to write on a directory owned by root (making fakeroot unusable)
ln: creating symbolic link `debian/libstdc++6-powerpc-cross-deps/lib/lib':
Permission denied
* And I also believe (not sure) it tries to run the testsuite on cross
builds, which should be avoided or done remotely.
Feel free to split this bug if you find this issues should be worked out as
separated bugs.
Kind regards,
Hector Oron
==> powerlog-fortran.txt <== find debian/lib64gfortran3-powerpc-cross
-perm -5 -type f \( -name '*.cmxs' \) -print0 2>/dev/null | xargs -0r chmod 644
find debian/lib64gfortran3-powerpc-cross/usr/lib/perl5
debian/lib64gfortran3-powerpc-cross/usr/share/perl5 -type f -perm -5 -name
'*.pm' -print0 2>/dev/null | xargs -0r chmod a-Xdh_makeshlibs
-plib64gfortran3-powerpc-cross
rm -f debian/lib64gfortran3-powerpc-cross/DEBIAN/shlibssed -i
s/-powerpc-cross//g debian/lib64gfortran3-powerpc-cross/DEBIAN/shlibs
sed: can't read debian/lib64gfortran3-powerpc-cross/DEBIAN/shlibs: No such file
or directory
make[1]: *** [stamps/08-binary-stamp-lib64fortran] Error 2
make[1]: Leaving directory `/home/zumbi/buildcross/trunk/powerpc/gcc-4.4-4.4.3'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
==> powerlog-libstdc++.txt <==
chmod 644 debian/libstdc\+\+6-powerpc-cross/DEBIAN/shlibs
chown 0:0 debian/libstdc\+\+6-powerpc-cross/DEBIAN/shlibs
sed s/-powerpc-cross//g < debian/libstdc++6-powerpc-cross/DEBIAN/shlibs >
debian/libstdc++6-powerpc-cross/DEBIAN/shlibs.fixed
mv debian/libstdc++6-powerpc-cross/DEBIAN/shlibs.fixed
debian/libstdc++6-powerpc-cross/DEBIAN/shlibs
mkdir debian/libstdc++6-powerpc-cross-deps
mkdir: cannot create directory `debian/libstdc++6-powerpc-cross-deps': File
exists
make[1]: *** [stamps/08-binary-stamp-libstdcxx] Error 1
make[1]: Leaving directory `/home/zumbi/buildcross/trunk/powerpc/gcc-4.4-4.4.3'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
==> powerlog-libstdc++-2.txt <==
chown 0:0 debian/libstdc\+\+6-powerpc-cross/DEBIAN/shlibs
sed s/-powerpc-cross//g < debian/libstdc++6-powerpc-cross/DEBIAN/shlibs >
debian/libstdc++6-powerpc-cross/DEBIAN/shlibs.fixed
mv debian/libstdc++6-powerpc-cross/DEBIAN/shlibs.fixed
debian/libstdc++6-powerpc-cross/DEBIAN/shlibs
test -d debian/libstdc++6-powerpc-cross-deps || mkdir
debian/libstdc++6-powerpc-cross-deps
ln -s "`readlink -e /usr/powerpc-linux-gnu/lib`"
debian/libstdc++6-powerpc-cross-deps/lib
ln: creating symbolic link `debian/libstdc++6-powerpc-cross-deps/lib/lib':
Permission denied
make[1]: *** [stamps/08-binary-stamp-libstdcxx] Error 1
make[1]: Leaving directory `/home/zumbi/buildcross/trunk/powerpc/gcc-4.4-4.4.3'
make: *** [binary] Error 2
dpkg-buildpackage: error: fakeroot debian/rules binary gave error exit status 2
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
