Navigation

    Kopano
    • Register
    • Login
    • Search
    • Categories
    • Get Official Kopano Support
    • Recent
    Statement regarding the closure of the Kopano community forum and the end of the community edition

    libkcrosie* missing from RC1 release?

    Kopano Groupware Core
    2
    4
    627
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • Wiz
      Wiz last edited by Wiz

      Hello,

      I just updated kopano 8.3.4 final to 8.4.0 RC1 and both zpush and webapp failed with an error message about a missing shared object file libkcrosie when using custom compiled mapi with php 5.6.31 or php 7.1.10 (remi) … SCL is so outdated.

      Fatal error: Unknown:0 - PHP Startup: Unable to load dynamic library '/opt/remi/php71/root/usr/lib64/php/modules/mapi.so' - libkcrosie.so.0: cannot open shared object file: No such file or directory (32)
      

      The only reference I found of libkcrosie is in the source

      if HAVE_TIDY
      COND_libkcrosie_la = libkcrosie.la
      COND_libkcrosie_ldd = libkcrosie.ldd
      endif
      
      ....
      
      #
      # libkcrosie
      #
      include_HEADERS = librosie/librosie.h
      libkcrosie_la_SOURCES = librosie/librosie.cpp
      libkcrosie_la_LIBADD  = libkcutil.la -ltidy
      libkcrosie_la_LDFLAGS = ${AM_LDFLAGS} -no-undefined -version-info 0:0:0 \
      	${default_SYFLAGS${NO_VSYM}}
      EXTRA_libkcrosie_la_DEPENDENCIES = ${default_sym}
      

      It appears libkcrosie is linked to tidy - what am I missing here? I copied the compiled libkcrosie* files from the dev server to production and was able to restore services.

      Kopano’s custom compile knowledge base page is in dire needs of an update.

      Thanks

      fbartels 1 Reply Last reply Reply Quote 0
      • fbartels
        fbartels Kopano @Wiz last edited by

        Hi @wiz ,

        are you speaking about your own builds or the official ones?

        Librosie ist part of the Core sourcecode and located at https://stash.kopano.io/projects/KC/repos/kopanocore/browse/librosie.

        If you want to work on improving the manual compiling procedures help is very much welcome. We already started shifting compiling instructions from the official documentation into https://stash.kopano.io/projects/KC/repos/kopanocore/browse/doc/install.txt. You can find pointers on how to contribute patches in https://stash.kopano.io/projects/KC/repos/kopanocore/browse/CONTRIBUTING.md.

        Regards Felix

        Resources:
        https://kopano.com/blog/how-to-get-kopano/
        https://documentation.kopano.io/
        https://kb.kopano.io/

        Support overview:
        https://kopano.com/support/

        Wiz 1 Reply Last reply Reply Quote 0
        • Wiz
          Wiz @fbartels last edited by Wiz

          @fbartels Hello. I am referring to the official ones, RC1 release, from kopano with a custom ‘mapi[dot]so’ compiled with php from Remi repo. SCL repo releases have not been updated since December 2016! SCL depends on Remi for additional features so please consider dropping SCL in favor of Remi.

          As for the compile procedures - I’ll have a look at improving them over the weekend. Obviously, this depends on whether I receive feedback/guidance from Kopano on compile-related issues.

          Thanks

          1 Reply Last reply Reply Quote 0
          • Wiz
            Wiz last edited by Wiz

            So having libtidy installed prior to compiling mapi causes librosie to get compiled and therefore becomes required by mapi… This is why librosie was not compiled and therefore required in the official kopano supported releases.

            1 Reply Last reply Reply Quote 0
            • First post
              Last post