qmake built in paths are incorrect

Bug #727150 reported by Francis Hart
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
qt4-x11 (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

Binary package hint: qt4-dev-tools

The qmake tool has built in paths that it uses to determine the location of other qt tools, libs, spec files etc.
These paths are set at compile time when building qmake from the QT SDK.

The version of qmake provided for 64bit ubuntu 10.04, the qt4-qmake package (or qt4-dev-tools) is unusable, as these built in paths are incorrect.

For example, when dumping the built in paths with 'qmake -query', it reports:
QT_INSTALL_BINS:/usr/bin
QT_INSTALL_PREFIX:/usr/bin
QT_INSTALL_DATA:/usr/bin
QT_INSTALL_DOCS:/usr/bin/doc
QT_INSTALL_HEADERS:/usr/bin/include
QT_INSTALL_LIBS:/usr/bin/lib
QT_INSTALL_BINS:/usr/bin/bin
QT_INSTALL_PLUGINS:/usr/bin/../lib/p4v/qt4/plugins
QT_INSTALL_TRANSLATIONS:/usr/bin/../lib/p4v/P4VResources/translations
QT_INSTALL_CONFIGURATION:/usr/bin
QT_INSTALL_EXAMPLES:/usr/bin
QT_INSTALL_DEMOS:/usr/bin
QMAKE_MKSPECS:/usr/bin/mkspecs
QMAKE_VERSION:2.01a
QT_VERSION:4.6.2

One obviously issue is the bin path pointing to /usr/bin/bin, and the mkspecs path pointing to /usr/bin/mkspecs.

I think that when the QT SDK was built, the '-prefix' directory specified in the configure script is incorrect, and does not match when the uduntu package actually places the files.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: qt4-dev-tools 4:4.6.2-0ubuntu5.1
ProcVersionSignature: Ubuntu 2.6.32-28.55-generic 2.6.32.27+drm33.12
Uname: Linux 2.6.32-28-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Tue Mar 1 14:55:13 2011
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.utf8
 SHELL=/bin/bash
SourcePackage: qt4-x11

Revision history for this message
Francis Hart (francis-hart) wrote :
Revision history for this message
Felix Geyer (debfx) wrote :

Are you sure that you aren't using a custom build of qmake?

Changed in qt4-x11 (Ubuntu):
status: New → Incomplete
Revision history for this message
Francis Hart (francis-hart) wrote :

Yes I'm pretty sure its the qmake from the qt4-qmake package.

I'll recheck again tomorrow when I back at work and can access the machine.

I do have a custom QT build on the machine, but it is build from 4.7.1 sources, and was actually only done as a solution to encountering this problem first!

Revision history for this message
Terence Simpson (tsimpson) wrote :

These two lines look rather suspicious:
QT_INSTALL_PLUGINS:/usr/bin/../lib/p4v/qt4/plugins
QT_INSTALL_TRANSLATIONS:/usr/bin/../lib/p4v/P4VResources/translations
Do you have something installed like "p4v"?

I can't confirm this on my 64bit 10.04.1:
$ qmake -query
QT_INSTALL_PREFIX:/usr
QT_INSTALL_DATA:/usr/share/qt4
QT_INSTALL_DOCS:/usr/share/qt4/doc
QT_INSTALL_HEADERS:/usr/include/qt4
QT_INSTALL_LIBS:/usr/lib
QT_INSTALL_BINS:/usr/bin
QT_INSTALL_PLUGINS:/usr/lib/qt4/plugins
QT_INSTALL_TRANSLATIONS:/usr/share/qt4/translations
QT_INSTALL_CONFIGURATION:/etc/xdg
QT_INSTALL_EXAMPLES:/usr/lib/qt4/examples
QT_INSTALL_DEMOS:/usr/lib/qt4/demos
QMAKE_MKSPECS:/usr/share/qt4/mkspecs
QMAKE_VERSION:2.01a
QT_VERSION:4.6.2

$ apt-cache policy qt4-dev-tools
qt4-dev-tools:
  Installed: 4:4.6.2-0ubuntu5.1
  Candidate: 4:4.6.2-0ubuntu5.1
  Version table:
 *** 4:4.6.2-0ubuntu5.1 0
        500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages
        100 /var/lib/dpkg/status
     4:4.6.2-0ubuntu5 0
        500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages

Revision history for this message
Francis Hart (francis-hart) wrote :

Hi Terence,

Yes, many thanks, that has solved the problem.

p4v was installed on the system, done by copying the contents of the p4v.tgz bin directory to /usr/bin.
This included a 'qt.conf' file, which I guess was interfering with qmake.

Is there an official p4 and p4v package for ubuntu?

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for qt4-x11 (Ubuntu) because there has been no activity for 60 days.]

Changed in qt4-x11 (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.