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

Bug#931019: marked as done (padthv1 FTCBFS: uses the build architecture qmake)

Your message dated Sat, 11 Jan 2020 21:45:58 +0100
with message-id <d46e73fc-c933-e4f9-9185-95de25d90249@kabelmail.de>
and subject line Re: padthv1 FTCBFS: uses the build architecture qmake
has caused the Debian Bug report #931019,
regarding padthv1 FTCBFS: uses the build architecture 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.)


-- 
931019: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=931019
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Source: padthv1
Version: 0.8.6-1
Tags: patch upstream
User: debian-cross@lists.debian.org
Usertags: ftcbfs

padthv1 fails to cross build from source, because configure.ac fails to
consider $ac_tool_prefix when checking for qmake. The attached patch
fixes that and makes padthv1 cross buildable. Please consider applying
it.

Helmut

--- padthv1-0.8.6.orig/configure.ac
+++ padthv1-0.8.6/configure.ac
@@ -266,12 +266,12 @@
 ac_errmsg="not found in current PATH. Maybe QT development environment isn't available."
 
 if test "x$ac_qt4" = "xyes"; then
-   AC_PATH_PROG(ac_qmake, qmake-qt4, [no], $ac_path)
+   AC_PATH_TOOL(ac_qmake, qmake-qt4, [no], $ac_path)
 else
-   AC_PATH_PROG(ac_qmake, qmake-qt5, [no], $ac_path)
+   AC_PATH_TOOL(ac_qmake, qmake-qt5, [no], $ac_path)
 fi
 if test "x$ac_qmake" = "xno"; then
-   AC_PATH_PROG(ac_cv_qmake, qmake, [no], $ac_path)
+   AC_PATH_TOOL(ac_cv_qmake, qmake, [no], $ac_path)
    ac_qmake=$ac_cv_qmake
 fi
 if test "x$ac_qmake" = "xno"; then

--- End Message ---
--- Begin Message --- 
Hello Helmut,

this seems to be fixed now by upstream, with the 0.9.12 release in
unstable. :-)

Best regards,
Dennis

--- End Message ---
Reply to: