On Sun, November 15, 2009 5:10 am, Stefan Endrullis wrote: > Hello kopete users, > > if you are using the cryptoplugin of kopete you might be also annoyed by > the visual overhead ("Outgoing Encrypted Message:") which is constantly > printed with each incoming and outgoing message and consumes more space > than the real messages. Long ago there has been a bug report on this issue > (https://bugs.kde.org/show_bug.cgi?id=77486), a patch was submitted and > the bug was closed as fixed, but the patch never came into a final Debian > or Ubuntu release, I think because of KDE4. But what about applying this > patch against the KDE3 remix repository now? > > The patch is hosted here: > http://kde-apps.org/content/show.php?content=40844&vote=good&tan=7513769 > > I also would like to help getting this patch applied. But I had some > problem with the compilation of the kopete package. Normally I just do > > apt-get build-dep <package> > apt-get -b source <package> > > and the binary package is generated from the source package. But in case > of kopete-kde3 the compilation fails with this error: > > [...] > g++ -DHAVE_CONFIG_H -I. > -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise > -I../../../.. -I../../../../kopete/protocols/gadu/libgadu > -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/qca/src > -I/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise > -I/opt/kde3/include/kde -I/usr/share/qt3/include -I. -DQT_THREAD_SUPPORT > -D_REENTRANT -D_LARGE_FILES=1 -Wno-long-long -Wundef -ansi > -D_XOPEN_SOURCE=500 -D_BSD_SOURCE -Wcast-align -Wchar-subscripts -Wall -W > -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 -g -O2 -g -Wall -O2 > -Wformat-security -Wmissing-format-attribute -Wno-non-virtual-dtor > -fno-exceptions -fno-check-new -fno-common -DQT_CLEAN_NAMESPACE > -DQT_NO_ASCII_CAST -DQT_NO_STL -DQT_NO_COMPAT -DQT_NO_TRANSLATION -c > /home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/./kopete/protocols/groupwise/libgroupwise/rtf.cc > -fPIC -DPIC -o .libs/rtf.o > rtf.ll: In member function 'void RTF2HTML::PrintUnquoted(const char*, > ...)': > rtf.ll:316: warning: function might be possible candidate for 'gnu_printf' > format attribute > rtf.ll: In member function 'void Level::setText(const char*)': > rtf.ll:574: error: invalid conversion from 'const char*' to 'char*' > make[7]: *** [rtf.lo] Error 1 > make[7]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' > make[6]: *** [all-recursive] Error 1 > make[6]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise/libgroupwise' > make[5]: *** [all-recursive] Error 1 > make[5]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols/groupwise' > make[4]: *** [all-recursive] Error 1 > make[4]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete/protocols' > make[3]: *** [all-recursive] Error 1 > make[3]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu/kopete' > make[2]: *** [all-recursive] Error 1 > make[2]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' > make[1]: *** [all] Error 2 > make[1]: Leaving directory > `/home/stefan/programmierung/c/kdenetwork-kde3-3.5.10/obj-x86_64-linux-gnu' > make: *** [debian/stamp-makefile-build] Error 2 > dpkg-buildpackage: error: debian/rules build gave error exit status 2 > > I'm using karmic with some lucid packages (libc6). Is this the reason for > the error? Does somebody know who to fix it? > > Thanks in advance. > > Regards, > Stefan > Hi Stefan, GCC 4.4 changed char * strchr ( const char * str, int character ); to const char * strchr ( const char * str, int character ); This forces every instance of char xyz = strchr(...) to be changed to the (more correct) const char xyz = strchr(...). Fixing this is a simple matter of hunting down the offending line and adding a const keyword to the variable (unless, of course, the programmer was doing Bad Things with the variable, but fortunately I haven't seen too much of that in KDE3). Hope this helps, and thanks for the assistance! Timothy Pearson KDE3.5 Maintainer/Developer