vmime issues while compiling

joepadmiraal

I tried to compile the release branch of Kopano on Ubuntu 16.04.
I discovered vmime from the repository is too old (0.9.1) so I compiled vmime 0.9.2 and did a make install.

That went fine so I continued with Kopano.
The make command runs for a while and ends with a lot of lines which look like this:

GEN kopano-dagent.ldx
undefined symbol: typeinfo for vmime::object (/home/adminjoep/build_from_source/kopanocore/.libs/libkcinetmapi.so.0)
undefined symbol: typeinfo for vmime::net::transport (/home/adminjoep/build_from_source/kopanocore/.libs/libkcinetmapi.so.0)
undefined symbol: typeinfo for vmime::net::transport (/home/adminjoep/build_from_source/kopanocore/.libs/libkcinetmapi.so.0)

Is this still due to an incompatible vmime installation?
If so, which version is required to compile Kopano?

I have a full compile log but I don’t see any way to upload it to this forum.

Thanks,
Joep

bosim

Hi Joep

Are you absolutely sure you removed the old vmime packages? and also did a “make clean” in the kopano build directory after the vmime make install.

Bo

joepadmiraal

Hi Bo,

Thanks for answering.

To remove the old vmime I did:
sudo apt-get remove libvmime-dev
sudo apt-get remove libvmime0

I cloned the Kopano repository again just to be sure there are no compile left overs from the old vmime.

bosim

Hi again Joep

@joepadmiraal said in vmime issues while compiling:

To remove the old vmime I did:
sudo apt-get remove libvmime-dev
sudo apt-get remove libvmime0

Could you check if there is remainings from the old vmime installation, i.e.
sudo find /usr -iname libvmime*

Bo

joepadmiraal

I tried a clean install in a Vagrant machine.
Here I am able to compile with vmime from source.
I had to use the gsoap packages from the kopano debs.

So the problem I have on my production machine are probably due to the old vmime installation.
I’ll try to clean that up and report back here when I have more info.

bosim

@joepadmiraal said in vmime issues while compiling:

I tried a clean install in a Vagrant machine.
Here I am able to compile with vmime from source.
I had to use the gsoap packages from the kopano debs.

So the problem I have on my production machine are probably due to the old vmime installation.
I’ll try to clean that up and report back here when I have more info.

That good to hear Joep.

Have a nice weekend.

Bo

joepadmiraal

I cleaned everything on the production machine and compiling went fine.
Now make install seems to have some problems.
Both on the clean Vagrant machine as on the production machine.
It seems to miss some doc files.
I also noticed it’s saying xmlto is needed for the manual pages.
I don’t know if that’s related but I don’t want to install this if it’s not necessary as installing xmlto requires 1.5GB extra data.

…
GEN doc/kopano.0
Please install xmlto to generate manual pages
/bin/mkdir -p ‘/usr/local/share/man/man1’
/usr/bin/install -c -m 644 ./doc/kopano-fsck.1 ./doc/kopano-passwd.1 ./doc/kopano-set-oof.1 ./doc/kopano-stats.1 ‘/usr/local/share/man/man1’
/usr/bin/install: cannot stat ‘./doc/kopano-fsck.1’: No such file or directory
/usr/bin/install: cannot stat ‘./doc/kopano-passwd.1’: No such file or directory
/usr/bin/install: cannot stat ‘./doc/kopano-set-oof.1’: No such file or directory
/usr/bin/install: cannot stat ‘./doc/kopano-stats.1’: No such file or directory
…

Do you have any suggestions?

Thanks,
Joep

bosim

Hi Joep

We removed the xmlto dependency in the master. If you want to cherry-pick the commit it is here:

https://stash.kopano.io/projects/KC/repos/kopanocore/commits/fc3a8387e802875fa99025345fbcffa044ba5431

Bo

joepadmiraal

thanks I will give it a try