On Sat, Jan 12, 2008 at 05:18:58PM +0300, Pereresus ne Vlezaet Buggy wrote: > Here are updates to libkdcraw & libkexiv2, which are dependencies > to digikam. Nowadays digikam do not even get built because current > port lib versions are out of date. (But it's configure script > doesn't report this as an error... So I cranked LIB_DEPENDS. All > those patches go inline at the end of this letter. > > Also there is a patch for KDE port that makes patch-ac_include_m4 > grow, so configure script doesn't say now that c++ linker cannot > build shared libraries.
You're not saying which libraries you're talking about. This is something that gets solved locally by linking the required libraries in kdcraw/digikam. > digikam itself build still fails, now with failures like this: > > c++ -Wno-long-long -Wundef -Wall -W -Wpointer-arith -DNDEBUG -DNO_DEBUG -O2 > -O2 -pipe -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 -DQT_CLEAN_NAMESPACE -o .libs/digikamthemedesigner > digikamthemedesigner.all_cpp.o -pthread -L/usr/local/lib/qt3 > -L/usr/local/lib -L/usr/X11R6/lib -L/usr/local/lib/db4 -L/usr/local/lib/samba > -L../../digikam/digikam/.libs -ldigikam > -L/usr/obj/i386/lcms-1.15/lcms-1.15/src/.libs -lgphoto2 -lexif -lgphoto2_port > -lltdl -ltiff -ljasper -lkexiv2 -lexiv2 -lkdcraw -llcms -lkipi -lkhtml > -lkutils -lkdeprint -lkparts -lkjs -lpcreposix -lpcre -lkabc -lkresources > -lkio -lfam -lrpcsvc -lstdc++ -lkwalletclient -lkdesu -lkdeui -lvcard > -lkdecore -lkdefx -lXrender -lidn -liconv -lintl -lart_lgpl_2 -lutil -lDCOP > -pthread -lSM -lICE -lXext -lX11 -lXdmcp -lXau -lm -lz -lpng -ljpeg -lqt-mt > -lsqlite3 -Wl,-rpath,/usr/local/lib -Wl,-rpath,/usr/X11R6/lib > -Wl,-rpath,/usr/local/lib/qt3 -Wl,-rpath,/usr/local/lib/db4 > -Wl,-rpath,/usr/local/lib/samba > ../../digikam/digikam/.libs/libdigikam.so.3.1: warning: vsprintf() is often > misused, please use vsnprintf() > /usr/local/lib/libjasper.so.2.0: warning: tmpnam() possibly used unsafely; > consider using mkstemp() > ../../digikam/digikam/.libs/libdigikam.so.3.1: warning: strcpy() is almost > always misused, please use strlcpy() > ../../digikam/digikam/.libs/libdigikam.so.3.1: warning: sprintf() is often > misused, please use snprintf() > ../../digikam/digikam/.libs/libdigikam.so.3.1: warning: strcat() is almost > always misused, please use strlcat() > digikamthemedesigner.all_cpp.o(.text+0x67c2): In function > `__static_initialization_and_destruction_0(int, int)': > : undefined reference to `__dso_handle' > digikamthemedesigner.all_cpp.o(.text+0x67f1): In function > `__static_initialization_and_destruction_0(int, int)': > : undefined reference to `__dso_handle' > collect2: ld returned 1 exit status > gmake[3]: *** [digikamthemedesigner] Error 1 > gmake[3]: Leaving directory > `/home/h/src/ports/graphics/digikam/w-digikam-0.9.3p0/digikam-0.9.3/digikam/themedesigner' > Builds here, don't know what's wrong on your system. Probably a side effect of your acinclude.m4 patch... > Also, digiKam building requires that previous requires that previous > version is removed from the system is this OK? And, if not, could > anyone give a clue where to dig to avoid this behavior? This is a general problem, this will get solved when we finally switch to our own libtool. Don't spend any time trying to work around it, it's not worth it.
