Summary: | kdebase-3.2.0 fails to during configure saying kdelibs need to be installed first | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Robert Kroes <robert> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED INVALID | ||
Severity: | major | CC: | hhuettler, paul |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Robert Kroes
2004-02-19 23:17:41 UTC
I have just tried to (unsuccessfully) rebuild kdelibs. I already have it installed (emerged successfully on Feb 11). Please see http://bugs.gentoo.org/show_bug.cgi?id=42223. Although the two appear to be related, I didnt' want to list #42223 as a dependency (I'll leave that to the true bug munchers :-). I can think of no reason why my ebuilds are suddenly in so much trouble. The machine is running perfectly smoothly, there are no hard disk errors, and aside from these persistent KDE build failures you'd never know anything was wrong. There also haven't been any power failures or system crashes. I am running a journaling filesystem (reiserfs). I am at a loss... Help? :-) your kdebase is due to the upgrade of Qt - you have to reinstall kdelibs after upgrading to qt 3.3 (as is noted in the ebuild) your kdelibs problem is most likely a cflags issue. can you post the exact error? I don't know how you spotted it, but you're dead right about the Qt 3.3 thing. Below is my "genlop -l" output. As you can see kdelibs-3.2.0 emerged a day before qt-3.3.0. ... Wed Feb 11 06:30:27 2004 arts-1.2.0 has been merged. Wed Feb 11 09:45:36 2004 kdelibs-3.2.0 has been merged. Thu Feb 12 21:49:28 2004 libungif-4.1.0.1b has been merged. Thu Feb 12 23:46:37 2004 qt-3.3.0 has been merged. ... You mentioned that it's noted in the ebuild that kdelibs-3.2.0 needs to be rebuilt after qt-3.3.0. Since "emerge -u world" can take hours and hours (especially when there's a new KDE release) I generally just set it going and check back much later to see if it's finished. I never saw the notice you speak of. What should I do in future to make sure I don't miss critical bits of information like this? As for the exact error of the kdelibs build crash, I'd love to give that to you, but could you tell me which log file contains the information you're after? I listed the emerge output in bug report #42223 but I expect you're after more than that :-) Thanks heaps for your help - I owe you guys some brewskys! Unfortunately if you do it doing an emerge world it will just scroll by. There's an open bug report about a request to log this information so that you can view it after an emerge world is done (I don't have the number off hand, though). Perhaps in future I should run "emerge -u world" under "screen" with logging turned on (Ctrl-a, H)... Just a thought... |