id	summary	reporter	owner	description	type	status	priority	milestone	component	version	severity	resolution	keywords	cc	mlocked
12661	mythtv fails to build against anything that's not x86/amd64/armhf	superm1@…		"configure has a hard time finding qt5.  Ubuntu guys had dug into what was going on in configure.  Snippet of conversation:

{{{
12:36:46 <xnox> cjwatson, superm1 - ok found it. Mythtv plugins are funky and did tricks behind our back with iterating:
12:36:47 <xnox> if [ x""$qmake"" = ""xqmake"" ]; then
12:36:47 <xnox>     CHECK_QMAKE=""qmake-qt5 /usr/lib64/qt5/bin/qmake /usr/lib/x86_64-linux-gnu/qt5/bin/qmake /usr/lib/i386-linux-gnu/qt5/bin/qmake /usr/lib/arm-linux-gnueabihf/qt5/bin/qmake /usr/local/lib/qt5/bin/qmake $\
12:36:47 <xnox> qmake qmake-qt4""
12:36:54 <xnox> in case of ""qmake"" default qmake specified.
12:37:10 <xnox> and thus it ""worked"" on x86_64, i386, armhf only =)
12:37:21 <xnox> exporting QT_SELECT=5 would have been a better trick.
12:37:34 <xnox> or like querying the triplet from gcc.
12:38:02 <xnox> Mirv, our qt is fine, it's mythtv which is funny.
}}}

So the ask would be to explicitly export:
{{{
QT_SELECT=5
}}}
when running the build for configure to properly find qt5 without looking around all the various paths for every architecture known to man.

We can of course override this at packaging level too, but this should really work properly in the configure script.
"	Bug Report - General	closed	minor	29.2	MythTV - General	Master Head	medium	Trac EOL			0