View previous topic :: View next topic |
Author |
Message |
Zarhan l33t
Joined: 27 Feb 2004 Posts: 994
|
Posted: Sat Mar 19, 2005 8:39 am Post subject: Why didn't revdep-rebuild rebuild Qt? |
|
|
I've been upgrading to KDE 3.4. Now, before starting the KDE upgrade, I ran "emerge world", and the result was that a new version of glibc was pulled in. This broke Qt in some way, for now emerging KDE packages gives
Code: |
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! |
Re-emerging Qt fixed the problem.
However, the question is: I ran revdep-rebuild after emerging world. Why did the revdep-rebuild not detect that Qt was broken and re-emerge it automatically? I thought revdep-rebuild was specifically the tool that allows Gentoo to avoid broken library problems! Now I more or less did the re-emerging of Qt out on whim because I did not really know if anything was wrong with that (I mean, I still could start KDE 3.3 just fine!). |
|
Back to top |
|
|
KsE Apprentice
Joined: 18 Mar 2003 Posts: 269 Location: St. Cloud, MN
|
Posted: Sat Mar 19, 2005 2:22 pm Post subject: |
|
|
It probably wasn't "broken". The libs were probably still linked ok.
Another good tool for fixing thing is "emerge -pvuD --newuse world". This fixes a lot of problems too.
revdep-rebuild is a great tool. If this is a bug of some sort, I'd really like to know also. |
|
Back to top |
|
|
thechris Veteran
Joined: 12 Oct 2003 Posts: 1203
|
Posted: Mon Mar 21, 2005 7:45 am Post subject: |
|
|
emerge -pvuD world does not fix this bug. i got this bug when using said command. I guess now i just have to re-emerge qt. _________________ HW problems. It's a VIA thing. |
|
Back to top |
|
|
KsE Apprentice
Joined: 18 Mar 2003 Posts: 269 Location: St. Cloud, MN
|
Posted: Mon Mar 21, 2005 1:54 pm Post subject: |
|
|
Well, keep in mind the "--newuse" arg in there. That will rebuild all packages where use flags have changed. This will usually fix a lot of problems. You could also try "revdep-rebuild -pv". |
|
Back to top |
|
|
Zarhan l33t
Joined: 27 Feb 2004 Posts: 994
|
Posted: Mon Mar 21, 2005 10:01 pm Post subject: |
|
|
KsE, you should know that my standard upgrade procedure is
Code: |
emerge sync
emerge -uvDa --newuse world
emerge depclean
revdep-rebuild
|
And Qt did not get rebuilt after glibc upgrade, but KDE 3.4 complains about it nevertheless. All I'm looking for is an answer why revdep-rebuild does not detect the problem. |
|
Back to top |
|
|
KsE Apprentice
Joined: 18 Mar 2003 Posts: 269 Location: St. Cloud, MN
|
Posted: Tue Mar 22, 2005 3:07 am Post subject: |
|
|
That's how everyone should do it |
|
Back to top |
|
|
cylgalad Veteran
Joined: 18 Apr 2003 Posts: 1327 Location: France
|
Posted: Tue Mar 22, 2005 11:37 am Post subject: |
|
|
It's a configure/compilation time problem, I got the same sort of error with the updates of baghira & amarok here's the error in the config.log for baghira-0.6e :
Code: | configure:29500: checking for Qt
configure: 29568: /usr/qt/3/include/qstyle.h
taking that
configure:29683: rm -rf SunWS_cache; i686-pc-linux-gnu-g++ -o conftest -Wnon-vir
tual-dtor -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-
align -Wconversion -Wchar-subscripts -Wall -W -Wpointer-arith -Wwrite-strings -D
NDEBUG -DNO_DEBUG -O2 -march=athlon-xp -mcpu=athlon-xp -mmmx -m3dnow -msse -mfpm
ath=sse -fforce-addr -fomit-frame-pointer -O3 -pipe -Wformat-security -Wmissing-
format-attribute -fno-exceptions -fno-check-new -fno-common -I/usr/qt/3/include
-I. -DQT_THREAD_SUPPORT -D_REENTRANT -L/usr/qt/3/lib -L/usr/lib conftest.
cc -lqt-mt -lpng -lz -lm -ljpeg -ldl -lXext -lX11 -lSM -lICE -lpthread 1>&5
/usr/qt/3/lib/libqt-mt.so: undefined reference to `__pthread_register_cancel@GLI
BC_2.3.3'
/usr/qt/3/lib/libqt-mt.so: undefined reference to `__pthread_unregister_cancel@G
LIBC_2.3.3' |
Now I'm gonna rebuild qt |
|
Back to top |
|
|
ahood n00b
Joined: 27 May 2004 Posts: 8 Location: ENGLAND
|
Posted: Tue Mar 22, 2005 2:51 pm Post subject: |
|
|
I had same problem with kaffine and rebuilding qt-3.3.4-r2 has solved the problem. Thanks for your help. |
|
Back to top |
|
|
|