Launchpad itself

32bit build running on a 64bit builder

Asked by Vadim Peretokin

My 32bit build running on a 64bit builder, how can I fix this?

See https://launchpadlibrarian.net/310948791/buildlog_ubuntu-trusty-i386.mudlet_1%3A3.0.0-1~ppa3-0ubuntu1_BUILDING.txt.gz - i386 in the url yet kernel version reports x86_64. The qmake package that gets installed is 32bit (Setting up qt5-qmake:i386) yet when qmake is called, it tries to call the 64bit version (usr/lib/x86_64-linux-gnu/qt5/bin/qmake: Command not found).

Question information

Language:
English Edit question
Status:
Solved
For:
Launchpad itself Edit question
Assignee:
No assignee Edit question
Solved by:
Vadim Peretokin
Solved:
Last query:
Last reply:
Revision history for this message
Colin Watson (cjwatson) said : 		#1

All our i386 builds run on 64-bit kernels. This won't change. However, i386 builds run inside "linux32", so "uname -m" reports i686 rather than x86_64.

But anyway, the kernel flavour isn't actually your problem at all. You can see your problem if you unpack your source package in a clean directory and grep it for x86_64; it contains things like this:

./src/Makefile:19:QMAKE = /usr/lib/x86_64-linux-gnu/qt5/bin/qmake

So it looks like you somehow managed to upload a source package without cleaning it properly, even though the dh_auto_clean override in your debian/rules file looks reasonable at first glance. You'll need to investigate this on your side.

Revision history for this message
Vadim Peretokin (vperetokin) said : 		#2

Makes sense - my 64bit also failed because it was looking for some paths that are specific to my computer, even though I did think I cleaned it. I'll see about getting rid of ./src/Makefile - that's supposed to be autogenerated by qmake.