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.
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 20100413142401.1269.67424.reportbug@eefk2m5.upc.ed u">http://lists.debian.org/20100413142401.1269.67424.reportbug@eefk2m5.upc.ed u
When building cross compilers (only seen on biarch architectures):
Hector, it's known to be broken. Are you working on a patch/fix?
Matthias
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4BC48B33.6070404@debian.org">http://lists.debian.org/4BC48B33.6070404@debian.org
Hello Matthias,
> Hector, it's known to be broken. Are you working on a patch/fix?
I am not sure what you are trying to accomplish by those changes, so I
wanted to know that first.
If none is working on a fix I would not mind to work on it, but I am
short on time these days, so do not expect something soon.
I'll work on it if you do not state the contrary. :-)
Kind regards,
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: r2ydd0a3d701004130839ob49d4820q88c2c10f31da3071@ma il.gmail.com">http://lists.debian.org/r2ydd0a3d701004130839ob49d4820q88c2c10f31da3071@ma il.gmail.com
Hector, it's known to be broken. Are you working on a patch/fix?
I am not sure what you are trying to accomplish by those changes, so I
wanted to know that first.
building libgomp.
If none is working on a fix I would not mind to work on it, but I am
short on time these days, so do not expect something soon.
I'll work on it if you do not state the contrary. :-)
the right fix would be to merge the .cross.mk files into the native ones, but
not using one big ifdef, starting with one file
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4BC49272.5090800@debian.org">http://lists.debian.org/4BC49272.5090800@debian.org
2010/4/13 Matthias Klose <doko@debian.org>:
> the right fix would be to merge the .cross.mk files into the native ones,
> but not using one big ifdef, starting with one file
OK, I'll start with libgcc
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: t2sdd0a3d701004130852me2744c21j2729d7767f02d5fd@ma il.gmail.com">http://lists.debian.org/t2sdd0a3d701004130852me2744c21j2729d7767f02d5fd@ma il.gmail.com
I have started to do some work in this way, it is still WIP, but I
would like you to check if this way is OK with you then prepare
something more mergeable
debian/dh_doclink -p$(p_cxx) $(p_base)
+# For cross targets we do not need it
+ifneq($(DEB_CROSS),yes)
cp -p debian/README.C++ $(d_cxx)/$(docdir)/$(p_base)/C++/
cp -p $(srcdir)/gcc/cp/ChangeLog
$(d_cxx)/$(docdir)/$(p_base)/C++/changelog
+endif
debian/dh_rmemptydirs -p$(p_cxx)
-
+# For cross targets we do not need it
+ifneq($(DEB_CROSS),yes)
mkdir -p $(d_cxx)/$(docdir)/$(p_base)/test-summaries
echo "TEST COMPARE BEGIN"
ifeq ($(with_check),yes)
@@ -79,6 +108,7 @@ else
echo "Nothing to compare (testsuite not run)"
endif
echo "TEST COMPARE END"
+endif # end DEB_CROSS
# ----------------------------------------------------------------------
+# XXX HO: Only for native builds, do we want to implement cross targets here?
$(binary_stamp)-cxx-multi: $(install_stamp)
dh_testdir
dh_testroot
--
1.7.0
OK to proceed with the rest?
Kind regards,
--
Héctor Orón
"Our Sun unleashes tremendous flares expelling hot gas into the Solar
System, which one day will disconnect us."
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: h2jdd0a3d701004210927hff764d40nfa62b98300812579@ma il.gmail.com">http://lists.debian.org/h2jdd0a3d701004210927hff764d40nfa62b98300812579@ma il.gmail.com
I have started to do some work in this way, it is still WIP, but I
would like you to check if this way is OK with you then prepare
something more mergeable
There are two merge patches below:
From 024f597bbe0aa95fe967cc60abb0edec6f2694b3 Mon Sep 17 00:00:00 2001
that should be a macro, which expands to nothing for the native build, and to
the mangling for the cross build, called with no ifdef.
$(call cross_mangle_scripts, $(p_gcc))
The macro should find out itself which scripts should be mangled.
I would place these macros in rules.defs for now.
The more interesting case is the merging of the library packaging. I would
recommend starting with some lib which is not libgcc or libstdc++ for the easy
cases.
Matthias
--
To UNSUBSCRIBE, email to debian-gcc-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: 4BD31252.3060004@debian.org">http://lists.debian.org/4BD31252.3060004@debian.org