Version: 0.12.6 (using KDE Devel) Installed from: Compiled sources Compiler: gcc version 4.1.2 20061115 (prerelease) (SUSE Linux) OS: Linux Late july, 14th, a big GNOME update has come on openSUSE 10.2 repository. I could see quickly that GNOME (glib) libraries have been deeply reorganized : glib 1.2 and glib 2.0 includes are now completely separates (no more default includes like include/glib/glib.h) and many libraries like glib, gthreads, gtk+ ... have moved from /opt/gnome/lib to /usr/lib; As a consequence, /opt/gnome/lib search path is no more valid for gtk+ library. I have previously deleted kdenetwork directory and get back sources with a checkout command from svn kopete repository to be clean. Next, I have followed generation instructions from kopete website. Here's the backtraces : ------------------------------------------ Making all in nowlistening make[4]: entrant dans le répertoire « /home/gilles/kdenetwork/kopete/plugins/nowlistening » /bin/sh ../../../libtool --silent --tag=CXX --mode=link g++ -Wno-long-long -Wundef -ansi -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W -Wpointer-arith -fno-builtin -g -O2 -fno-schedule-insns -fno-inline -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor -fno-reorder-blocks -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -o kopete_nowlistening.la -rpath /opt/kde3/lib/kde3 -module -avoid-version -module -no-undefined -Wl,--no-undefined -Wl,--allow-shlib-undefined -R /opt/kde3/lib -R /opt/kde3/lib -R /usr/lib/qt3/lib -rdynamic -L/opt/kde3/lib -L/usr/lib/qt3/lib nowlisteningplugin.lo nlkscd.lo nlnoatun.lo nlxmms.lo nowlisteningguiclient.lo nljuk.lo nlamarok.lo nlkaffeine.lo nowlisteningconfig.lo ../../libkopete/libkopete.la -L/usr/lib -lgtk -lgdk -lgmodule -lglib -ldl -lXi -lXext -lX11 -lm -lxmms grep: /opt/gnome/lib/libgtk.la: No such file or directory /usr/bin/sed: can't read /opt/gnome/lib/libgtk.la: No such file or directory libtool: link: `/opt/gnome/lib/libgtk.la' is not a valid libtool archive make[4]: *** [kopete_nowlistening.la] Erreur 1 make[4]: quittant le répertoire « /home/gilles/kdenetwork/kopete/plugins/nowlistening » make[3]: *** [all-recursive] Erreur 1 make[3]: quittant le répertoire « /home/gilles/kdenetwork/kopete/plugins » make[2]: *** [all-recursive] Erreur 1 make[2]: quittant le répertoire « /home/gilles/kdenetwork/kopete » make[1]: *** [all-recursive] Erreur 1 make[1]: quittant le répertoire « /home/gilles/kdenetwork » make: *** [all] Erreur 2 ------------------------------------------ "pkg-config --libs gtk+" command reports : "-lgtk -lgdk -lXi -lXext -lX11 -lm -lglib" there is no more "-L/opt/gnome/lib" library flag. We can confirm that with a ls command : ls -l /usr/lib/libgtk.la -rwxr-xr-x 1 root root 961 jui 13 18:45 /usr/lib/libgtk.la
not a bug in kopete's code. looks like a packaging problem to me. Something is expecting the old paths for the GTK libraries. My guess is XMMS.
"RESOLVED INVALID"? and " looks like "; " My guess " => are you sure enough to close this bug report ? can't you be more precise ? Looks like : " I'm not sure but I don't want to search, and then this is surely the buddy's fault !! " for me ! the least should be to perform a real technical analysis on this problem !
It's likely a local or distro-specific issue... not a kde bug, and the error lies elsewhere, which is why it was marked invalid. Now, If you can provide evidence to the contrary, please do so.
Can you provide evidence on what you say ?????? No, I don't think so! I am here because I need help! I am not writting back because of understanding problem on what your colleague has written down and explained what is your bug management !! This is the new spirit of the open source ? no thanks !
Sabourin, look at it this way, if you go to your doctor to report that your car won't run, what do you expect to happen?
Dieter, keep your poor comparison to a child. Don't be silly. Do you know software integration and functional validation ? If no, ask your colleagues. This was my job for 15 years as an engineer. Integration is a difficult discipline. Since an interface could be broken because of misconception, bad implementation, inconsistency or regression, what would you do ? You need to have a look on your piece of software as well as the other piece of software, not immediatly in your backyard. You can't say : I have the absolute truth; my job does not need to be rewieved, and this is only your fault. With this attitude it is like " trick or treat ". If you're right, your colleague can admit, but if you're wrong you would lose your credibility for a long time. A real software integrator would have proposed a technical way to investigate, if he doesn't want to do the job himself. Of course, you are proud of KDE team works, and you're right. But this is the normal life of a software to be rewieved, especially when it is open source software : best test effort has to be performed by the community. Ok, we can leave now on these thoughts, without resentment.
If you need help, do not file a bug report. Instead post a message on a forum or on the kopete-devel mailing list.