> checking for Qt... configure: error: Qt (>= Qt 3.3) (library qt-mt) not > found. Please check your installation! > For more details about this problem, look at the end of config.log. > Make sure that you have compiled Qt with thread support! > > !!! ERROR: kde-base/arts-1.3.2-r1 failed. > !!! Function kde_src_compile, Line 154, Exitcode 1 > !!! died running ./configure, kde_src_compile:configure > !!! If you need support, post the topmost build error, NOT this status > message. > > but qt-3.3.4-r2 is installed. > > I have 2 questions. > > 1. what can I do to resolve this ? (except masking arts)
I had this same issue with the kde 3.4 release; re-emerging qt resolved it. The true source of the problem is that at the same time 3.4 came out a new update to glibc came out; in rebuilding glibc, a new pthread library (ala nptl) was built that had an API change that libqt-mt is no longer compatible with. Re-emerging qt resolves the linking failures in qt/kde builds. > 2. What is arts good for ? Shouldn't I avoid it altogether with a -arts > USE flag ? Arts is the kde sound daemon. Based on your output of "emerge -pvtuD world", something (the ebuild) is overriding your "-arts" flag. It's probably being overridden by the libao ebuild, but why it thinks arts is a dependency I can't answer. -- [email protected] mailing list
