forcemerge 712264 756302
thanks
On Monday 28 July 2014 16:56:23 Carlo Wood wrote:
[snip]
> Dear Maintainer,
>
> since I installed qtchooser, *every* project that uses qt has been
> broken. The reason for that is that they run 'qmake' in order to
> find out if it exists (and/or for an other query), but the 'qmake'
> that is found (in the PATH) is (obviously) /usr/bin/qmake, which
> is a symlink to qtchooser, which exits with an error (error code 1):
>
> $ qmake
> qmake: could not exec '/usr/lib/i386-linux-gnu/qt4/bin/qmake': No such file
> or directory $ echo $?
> 1
>
> which then results in the configure script of that project to abort.
>
> It doesn't seem an option to install whatever provides
> /usr/lib/i386-linux-gnu/qt4/bin/qmake because that wants to delete half
> of my (64bit) OS.
Hi Carlo! We have multiple issues here.
For a part of it, the real bug, is what #712264 "Does not depends on the
binaries it masks" is about. I'm so merging this bug with the aforementioned
one. Sadly this is wontfix.
Now let's take a look at the other part of your report.
If qtchooser is looking for /usr/lib/i386-linux-gnu/qt4/bin/qmake is because
you might have qt4:i386 stuff installed. Run qtchooser -l to see which
configurations you have at hand.
If you want to build qt4 stuff on amd64 you need libqt4-dev:amd64 installed.
This part is definitely not a bug but part of what qtchooser does. Feel free
to ask in debian-kde@lists.debian.org or in #debian-kde if in doubt.
Kinds regards, Lisandro.
--
14: Para acceder y navegar en internet
* Debe tener conexion a Internet
Damian Nadales
http://mx.grulic.org.ar/lurker/message/20080307.141449.a70fb2fc.es.html
Lisandro Damián Nicanor Pérez Meyer
http://perezmeyer.com.ar/
http://perezmeyer.blogspot.com/
Attachment:
signature.asc
Description: This is a digitally signed message part.