(*** This bug was imported into bugs.kde.org ***) Package: kivio Version: 0.1 (using KDE 2.2.0 beta1) Severity: normal Installed from: compiled sources Compiler: gcc version 2.95.3 20010315 (release) OS: Linux (i686) release 2.4.6 OS/Compiler notes: Building koffice fails for kivio plugins on Slackware-8 system due to link errors (linker cannot resolve db_open). I used following patch to workaround a problem: koffice/kivio/kiviopart/Makefile.am~1 Tue May 29 00:18:29 2001 +++ koffice/kivio/kiviopart/Makefile.am Wed Jul 11 09:14:53 2001 @@ -1317 +1317 @@ kivio_la_LDFLAGS = $(all_libraries) -module -avoid-version kivio_la_LIBADD = ../../lib/kofficecore/libkofficecore.la -libkiviopart_la_LDFLAGS = -avoid-version -module $(LIB_KOFFICEUI) $(all_libraries) +libkiviopart_la_LDFLAGS = -avoid-version -module $(LIB_KOFFICEUI) $(all_libraries) -ldb2 bin_PROGRAMS = kivio kivio_SOURCES = dummy.cpp Of course I understand it's only a workaround and I'm including this patch only as ilustration for a problem. I had this problem already for some time and it's still present in CVS version updated in July 10th Andris (Submitted via bugs.kde.org) (Called from KBugReport dialog)
Hello I'm probably doing something nasty by mailing to two bug in-trays at the same time but I've had similar problems with KOffice 1.1 (KDE 2.2.1). What happens is that I configure KOffice and then start the build process; it crashes out in kivio/plugins when building the libraries. The only way to make the build process "happy" is to find a variable in the Makefile that libtool (I suppose) actually uses. Thus I modified the LDFLAGS variable in kivio/plugins/*/Makefile to get the plugins to build correctly. Modifying LIBPYTHON or anything else doesn't seem to work - libtool doesn't pick the flags up. Later on in the build process a similar problem arises with kivio/kiviopart. Here adding the extra flags to LIBPYTHON does make the build process move on. I looked inside my Python distribution's Modules/Makefile for any flags which might be of importance. For me there were many of them including: -L/usr/X11R6/lib -L/usr/local/ssl/lib -lpthread -lm -ldb -ldl -lutil -lssl -ltk8.0 -ltcl8.0 I wonder if it's possible to get Python to reveal its flags. Until very recently anything building Python would make use of Python's own configuration artifacts along with "standard" Makefile.pre.in and Setup.in files. The SWIG documentation (amongst others) must have some information on such issues too. Anyway after all this I do avoid unresolved symbol errors (dbopen and various Tcl-related stuff) in the build process but I still can't run the application - I just get more unresolved symbol complaints. (I'll try and mail a log of these at some point.) I'm using Red Hat 6.1 on Intel with the provided gcc (2.95.x I think) and libc (2.1). Python 2.0 is configured with threads OpenSSL support and Tkinter. Regards Paul -- Get your firstname@lastname email for FREE at http://Nameplanet.com/?su
Is this still reproducable with 1.3beta2 or cvs?
Subject: Re: Build failures in kivio/plugins On Wednesday 02 July 2003 01:36, Peter Simonsson wrote: > ------- You are receiving this mail because: ------- > You reported the bug, or are watching the reporter. > > http://bugs.kde.org/show_bug.cgi?id=28703 > > > > > ------- Additional Comments From psn@linux.se 2003-07-02 00:36 ------- > Is this still reproducable with 1.3beta2 or cvs? I haven't seen this problem already for a long time. KOffice-1.2.1 and 1.3b2 builds Ok (with KDE-3.1.2) Andris
*** Bug has been marked as fixed ***.