[SOLVED] next problem zarafa 7.1 on slackcurrent

carlitoco · 03-05-2013, 02:32 PM

Hey now I have the next Problem with SlackwareCurrent.
Zarafa confog stops like this...

Code:

checking for the toolset name used by Boost for g++... configure: WARNING: could not figure out which toolset name to use for g++

checking boost/system/error_code.hpp usability... yes
checking boost/system/error_code.hpp presence... yes
checking for boost/system/error_code.hpp... yes
checking for the Boost system library... yes
checking boost/filesystem/path.hpp usability... yes
checking boost/filesystem/path.hpp presence... yes
checking for boost/filesystem/path.hpp... yes
checking for the Boost filesystem library... yes
checking boost/date_time/posix_time/posix_time.hpp usability... yes
checking boost/date_time/posix_time/posix_time.hpp presence... yes
checking for boost/date_time/posix_time/posix_time.hpp... yes
checking for the Boost date_time library... yes
checking boost version compatibility... adding backward compatible flags
checking for boost filesystem version 2 presence... configure: error: no, boost is too new

I dont know what does it mean but perhaps you?
thank you in advance !

Should I change to stable Slackware 14?

Didier Spaier · 03-05-2013, 03:06 PM

Quote:

Originally Posted by carlitoco

Should I change to stable Slackware 14?

If you want to use zarafa 7.1, yes (I'm assuming that you were using the SlackBuild provided by http://slackbuilds.org).

Bear in mind that slackbuilds.org provides slackbuilds for stable versions only. You may try some on -current but there is no guarantee and there are chances that the build will fail. That is actually not a problem with Slackware-current.

More generally -current is provided for testing purposes : if you want stability and do not intent to participate in testing, better stick to -stable releases of Slackware.

PS and yes, boost have changed in -current, this is stated in the ChangeLog.

carlitoco · 03-05-2013, 03:54 PM

Okay that's why I should read the changelog

Thank you to take time !

carlitoco · 03-06-2013, 07:02 AM

I got these error during make

Code:

Making all in inetmapi
make[2]: Entering directory `/tmp/SBo/zarafa-7.1.0/inetmapi'
  CXX    ECMapiUtils.lo
  CXX    ECVMIMEUtils.lo
  CXX    MAPIToVMIME.lo
  CXX    VMIMEToMAPI.lo
  CXX    outputStreamMAPIAdapter.lo
  CXX    inputStreamMAPIAdapter.lo
  CXX    mapiAttachment.lo
  CXX    mapiTextPart.lo
  CXX    MAPISMTPTransport.lo
  CXX    inetmapi.lo
  CXX    tnef.lo
  CXX    SMIMEMessage.lo
  CXXLD  libinetmapi.la
/usr/lib/gcc/i486-slackware-linux/4.7.1/../../../../i486-slackware-linux/bin/ld: cannot find -lvmime
collect2: error: ld returned 1 exit status
make[2]: *** [libinetmapi.la] Error 1
make[2]: Leaving directory `/tmp/SBo/zarafa-7.1.0/inetmapi'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/SBo/zarafa-7.1.0'
make: *** [all] Error 2

Didier Spaier · 03-06-2013, 07:53 AM

Quote:

Originally Posted by carlitoco

/usr/lib/gcc/i486-slackware-linux/4.7.1/../../../../i486-slackware-linux/bin/ld: cannot find -lvmime

Most probably you didn't first install libvmime-zarafa, which is a required dependency of zarafa as stated here.

PS Don't forget to install kyotocabinet before building zarafa as well. And as stated there install libgsasl before building libvmime-zarafa

carlitoco · 03-06-2013, 08:30 AM

It is already installed, thats my problem
and I checked the dependency again "libgsasl" is also installed.

For kyotocabinet I use this post kyotocabinet 1.2.76 from ponce.

thank you ...

carlitoco · 03-06-2013, 08:40 AM

Code:

================+

Installation prefix      : /usr
Debugging mode           : no
Messaging support        : yes
     * protocols         : pop3 smtp imap maildir sendmail
File-system support      : yes
Platform handlers        : posix
SASL support             : yes
TLS/SSL support          : yes

Didier Spaier · 03-06-2013, 08:41 AM

To be 150% sure, please send output of following commands:

Code:

ls -l /var/log/packages/{*zarafa*,libgsasl*}

I ask that because It happened to me more than once to forget installing freshly built packages

carlitoco · 03-06-2013, 09:27 AM

Here is my output.

Code:

root@horde:/var/www/htdocs# ls -l /var/log/packages/{*zarafa*,libgsasl*}
-rw-r--r-- 1 root root  3118 Mar  6 15:37 /var/log/packages/libgsasl-1.8.0-i486-1_SBo
-rw-r--r-- 1 root root 11307 Mar  6 16:05 /var/log/packages/libvmime-zarafa-0.9.2_svn603-i486-1_SBo

Didier Spaier · 03-06-2013, 12:00 PM

Same error here.

But I see that the libvmime-zarafa package includes /usr/lib/libvmime_zarafa.so.0.0.0

So I would try either to adapt some configure option accordingly (unfortunately I don't know how to do that), or to symlink /usr/lib/libvmime to /usr/lib/libvmime_zarafa.so.0.0.0

In any case, better ask for help to the maintainer of the zarafa package or on IRC #slackbuilds.

Didier Spaier · 03-06-2013, 12:27 PM

I blindly did that

Code:

cd /usr/lib
ln -s libvmime_zarafa.so.0.0.0 libvmime.so.0
ln -s libvmime_zarafa.so.0.0.0 libvmime.so

then, the build succeeded:

Code:

bash-4.2# ls -l /var/log/packages/zarafa*
-rw-r--r-- 1 root root 17228 mars   6 19:19 /var/log/packages/zarafa-7.1.0-i486-1_SBo

Now I'm going to uninstall that stuff which I don't need

carlitoco · 03-07-2013, 02:30 AM

I need it for my Phone, some Family and Friends. I gonna try it out now.

Thank you

Didier Spaier · 03-07-2013, 02:50 AM

Also, run "ldonfig" as root *before* building it. It never hurts to do that whenever you add a library.