Re: [Xlog-discussion] KPSK with Xlog remote logging

[Joop Stakenborg]

On Sun, 08 Feb 2004 21:09:13 -0500
David Kjellquist <address@hidden> wrote:

> This afternoon I committed to the KPSK CVS on sourceforge.net the
> source code implementing remote logging using Xlog.
> 
> To get a copy of the code you will have to do a CVS snapshot until we
> have more testing to support a formal release.
> 
> I request everyone to give it a good test and post any comments to
> kpsk development list on sourceforge
> 
>               Dave (oldcyberdude) WB5NHL
>  
> 

Here is a short summary of things and commands needed:

cvs -d:pserver:address@hidden:/cvsroot/kpsk login
<hit enter>
cvs -z3 -d:pserver:address@hidden:/cvsroot/kpsk co kpsk
cd kpsk
<you need version 1.4 of automake>
autoheader
aclocal
automake
autoconf
<next install the qt3, the kde development packages and version 4.0 of
the berkeley db, don't know the rpm commands, sorry :-)> 
apt-get install libqt3-mt-dev kdelibs4-dev libdb4.0-dev
make

That should do it. However, I get problems when linking, about 20
pages of errors. Here is a short extract:

usexlogdlg.o(.text+0xe6): In function
`usexlogDlg::usexlogDlg[not-in-charge](QWidget*)':: undefined reference
to `vtable for usexlogDlg' usexlogdlg.o(.text+0xed): In function
`usexlogDlg::usexlogDlg[not-in-charge](QWidget*)':: undefined reference
to `vtable for usexlogDlg' usexlogdlg.o(.text+0x356): In function
`usexlogDlg::usexlogDlg[in-charge](QWidget*)':: undefined reference to
`vtable for usexlogDlg' usexlogdlg.o(.text+0x35d): In function
`usexlogDlg::usexlogDlg[in-charge](QWidget*)':: undefined reference to
`vtable for usexlogDlg' usexlogdlg.o(.text+0x4eb): In function
`usexlogDlg::~usexlogDlg [not-in-charge]()':: undefined reference to
`vtable for usexlogDlg' usexlogdlg.o(.text+0x4f2): more undefined
references to `vtable for usexlogDlg' follow kpskmeter.o(.text+0x28): In
function `kpskmeter::kpskmeter[not-in-charge](QWidget*)':: undefined
reference to `vtable for kpskmeter'

Using gcc-3.3.3, kdelibs 3.1.5 and qt-3.2.3.
Any idea what causes this?

Thanks,
Joop