kdewin32 emerge problem (with qmake path?)

Bernhard Reiter bernhard at intevation.de
Wed Oct 15 16:44:58 CEST 2008


On Mittwoch, 15. Oktober 2008, Pau Garcia i Quiles wrote:
> Quoting Bernhard Reiter <bernhard at intevation.de>:
>
> Confirmed. Are you by any chance using CMake 2.6.2?

Yes, this came with the new emerge 
when I did the emerge dbus-src before the emerge kdewin32 support.


> > emerge kdewin32 currently fails for me.
> >
> > qmake -v  also gives a strange value:
> > QMake version 2.01a
> > Using Qt version 4.4.3 in
> > c:/XYZ/kderoot-4/tmp/qt-4.4.2.20080924/image-mingw//lib
> >
> > In a different directory a "qmake -v"
> > leads to not having the "tmp/" in the path.
> > This observation might help to frame the infection.
> >
> > Here is the emerge output that fails:



-- 
Managing Director - Owner: www.intevation.net      (Free Software Company)
Germany Coordinator: fsfeurope.org. Coordinator: www.Kolab-Konsortium.com.
Intevation GmbH, Osnabrück, DE; Amtsgericht Osnabrück, HRB 18998
Geschäftsführer Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://mail.kde.org/pipermail/kde-windows/attachments/20081015/0d1b3424/attachment.sig 


More information about the Kde-windows mailing list