[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#884050: marked as done (qtconnectivity-opensource-src FTCBFS: does not pass cross flags to qmake)

Your message dated Fri, 9 Mar 2018 11:01:05 -0300
with message-id <CA+QPbz3POpR4kq+N_pxDqng8OjGmXQcVW9EuX=Y9nnnrAqZfXA@mail.gmail.com>
and subject line Done
has caused the Debian Bug report #884050,
regarding qtconnectivity-opensource-src FTCBFS: does not pass cross flags to qmake
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
884050: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=884050
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: qtconnectivity-opensource-src
Version: 5.9.2-2
Severity: minor
Tags: patch
User: helmutg@debian.org
Usertags: rebootstrap

qtconnectivity-opensource-src fails to cross build from source, because
it does not pass cross flags to qmake. This is best done by deferring to
dh_auto_configure these days. After doing so, it still fails to cross
build, because it fails finding libbluetooth. I don't have a solution
here, but let me try to describe the problem.

In src/bluetooth/configure.json it describes how to check for BlueZ with
pkg-config. It seems that qmake implements this by running another qmake
on a small test project to determine success or failure. Unfortunately,
this sub-qmake lacks cross flags again, so it uses the build
architecture pkg-config and g++ thus failing to find the bluetooth
library.

Potential options for fixing this:
 * Maybe we need to set PKG_CONFIG_EXECUTABLE?
 * Maybe we need to set a suitable QMAKE_QMAKE?

In any case, please close this bug when switching to dh_auto_configure
and making the BlueZ finding issue visible.

Helmut

diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/changelog qtconnectivity-opensource-src-5.9.2/debian/changelog
--- qtconnectivity-opensource-src-5.9.2/debian/changelog	2017-10-27 10:33:07.000000000 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/changelog	2017-12-10 13:32:07.000000000 +0100
@@ -1,3 +1,10 @@
+qtconnectivity-opensource-src (5.9.2-2.1) UNRELEASED; urgency=medium
+
+  * Non-maintainer upload.
+  * Address FTCBFS: Let dh_auto_configure pass cross flags to qmake.
+
+ -- Helmut Grohne <helmut@subdivi.de>  Sun, 10 Dec 2017 13:32:07 +0100
+
 qtconnectivity-opensource-src (5.9.2-2) unstable; urgency=medium
 
   * Upload to unstable.
diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/control qtconnectivity-opensource-src-5.9.2/debian/control
--- qtconnectivity-opensource-src-5.9.2/debian/control	2017-10-27 10:33:07.000000000 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/control	2017-12-10 13:32:02.000000000 +0100
@@ -8,7 +8,7 @@
            Felix Geyer <fgeyer@debian.org>,
            Timo Jyrinki <timo@debian.org>,
            Dmitry Shachnev <mitya57@debian.org>
-Build-Depends: debhelper (>= 10),
+Build-Depends: debhelper (>= 10.9.2~),
                libbluetooth-dev [linux-any],
                pkg-config,
                pkg-kde-tools,
diff --minimal -Nru qtconnectivity-opensource-src-5.9.2/debian/rules qtconnectivity-opensource-src-5.9.2/debian/rules
--- qtconnectivity-opensource-src-5.9.2/debian/rules	2017-10-27 10:33:07.000000000 +0200
+++ qtconnectivity-opensource-src-5.9.2/debian/rules	2017-12-10 13:31:11.000000000 +0100
@@ -15,7 +15,7 @@
 	# Be sure to regenerate the DBus cpp files
 	cd src/bluetooth/bluez/ ; ./generate
 	# Now call qmake
-	qmake
+	dh_auto_configure
 
 override_dh_auto_build-indep:
 	dh_auto_build -Smakefile -- docs

--- End Message ---
--- Begin Message --- 
Version: 5.10.1-1

-- 
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/

--- End Message ---
Reply to: