Source: xinv3d
Version: 1.3.6-6
Tags: patch
User: [email protected]
Usertags: rebootstrap

xinv3d fails to cross build from source, because it does not pass any
cross tools to make. Using dh_auto_build mostly fixes that except for
the final install invocation. It carries -s and therefore strips with
the wrong strip. Doing so not only breaks cross compilation, but also
generation of a -dbgsym package. It is best to defer stripping to
dh_strip. Thus the attached patch makes xinv3d cross build a -dbgsym
package successfully. Please consider applying it.

Helmut
diff -u xinv3d-1.3.6/debian/control xinv3d-1.3.6/debian/control
--- xinv3d-1.3.6/debian/control
+++ xinv3d-1.3.6/debian/control
@@ -3,7 +3,7 @@
 Priority: optional
 Maintainer: Chris Butler <[email protected]>
 Standards-Version: 3.8.0
-Build-Depends: libx11-dev, x11proto-core-dev, debhelper (>> 4.0.0)
+Build-Depends: libx11-dev, x11proto-core-dev, debhelper (>> 7)
 
 Package: xinv3d
 Architecture: any
diff -u xinv3d-1.3.6/debian/changelog xinv3d-1.3.6/debian/changelog
--- xinv3d-1.3.6/debian/changelog
+++ xinv3d-1.3.6/debian/changelog
@@ -1,3 +1,12 @@
+xinv3d (1.3.6-6.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Fix FTCBFS: (Closes: #-1)
+    + Let dh_auto_build pass cross tools to make.
+    + Defer stripping to dh_strip.
+
+ -- Helmut Grohne <[email protected]>  Tue, 27 Nov 2018 19:34:01 +0100
+
 xinv3d (1.3.6-6) unstable; urgency=low
 
   * Updatd build dependency on x-dev to x11proto-core-dev (closes:
diff -u xinv3d-1.3.6/debian/rules xinv3d-1.3.6/debian/rules
--- xinv3d-1.3.6/debian/rules
+++ xinv3d-1.3.6/debian/rules
@@ -7,9 +7,6 @@
 CFLAGS = -g -Wall -ansi
 INSTALL = install
 
-ifeq (,$(findstring nostrip,$(DEB_BUILD_OPTIONS)))
-       INSTALL += -s
-endif
 ifneq (,$(findstring noopt,$(DEB_BUILD_OPTIONS)))
        CFLAGS += -O0
 else
@@ -29,7 +26,7 @@
        dh_testdir
 
        # Add here commands to compile the package.
-       $(MAKE) "CFLAGS=$(CFLAGS)"
+       dh_auto_build -- "CFLAGS=$(CFLAGS)"
 
        touch build-stamp
 

Reply via email to