Summary: | Qt is a required dep for licq | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Seemant Kulleen (RETIRED) <seemant> |
Component: | New packages | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | normal | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Seemant Kulleen (RETIRED)
![]() checking for QT libraries... yes, lib: -lqt-mt in /usr/qt/3/lib checking for QT includes... /usr/qt/3/include checking for QT >= 2.1... no configure: error: Sorry, but you need QT version 2.1 or higher to compile the Qt gui plugin. !!! ERROR: net-im/licq-1.2.0a-r1 failed. !!! Function src_compile, Line 57, Exitcode 1 !!! (no error message) I get that error message whether or not I enable the qt USE flag though. nebuchadnezzar licq # qpkg -I -v -nc qt x11-libs/qt-2.3.2-r1 x11-libs/qt-3.0.5-r2 dev-util/qtunit-0.9.7 licq has interface plugins. This means that if you build it with USE=-qt -kde, you have _no_ interface and can't run it. That's useful for installing the console, gtk etc. interface plugins whose sources are packaged/developed separately and so have separate ebuilds. With USE=-kde -qt, it shouldn't even attempt to build the qt/kde stuff (I've checked it here and it works). Maybe you had -qt but +kde in USE? The qt/kde plugin supports either qt or qt+kde, but obviously not kde without qt. It lives in a separate subdir plugins/qt-gui-1.2.0 so it should be easy to check why the ebuild runs or does not run its configure script. worked fine in 1.2.3 |