On Monday 14 April 2008, Jan Niehusmann wrote: > I just reproduced this problem. First, I got the following problem: > > Checking Qt version...no! > ERROR: incorrect Qt version found: **Unknown** > > The "**Unknown**" strings comes from a call to qmake -query QT_VERSION. > This seems to be a problem of qt3: > > [EMAIL PROTECTED]:/tmp/qbrew-0.4.0$ qmake-qt4 -query QT_VERSION > 4.4.0-rc1 > [EMAIL PROTECTED]:/tmp/qbrew-0.4.0$ qmake-qt3 -query QT_VERSION > **Unknown** > > Therefore, there are two possibilites to fix this: Either a > Build-Conflicts against qt3-dev-tools, or an explicit call to qmake-qt4 > instead of just calling qmake. > > However, as buildds probably don't have qt3-dev-tools installed, this > probably is not the cause of the FTBFS bug. So I tried again in a clean > changeroot. Here, I got the following error: > > /usr/bin/ld: cannot find -lfontconfig > > This can be fixed by adding CONFIG -= link_prl to the .pro files > (qbrew.pro as well as the ones dynamically generated by configure.) > > With the following patch, qbrew builds again inside a clean chroot:
We are working for some other solution as well - there will hopefully within this week arrive a qt4 -4 to the archive. /Sune -- I'm not able to receive the mousepad, how does it work? You either should doubleclick a virus, or can never insert a secret password of the provider to send to the BIOS.
signature.asc
Description: This is a digitally signed message part.
