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

    core-8.7.80.119 difficult to build but succeeded

    Kopano Groupware Core
    2
    12
    598
    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.
    • jengelh
      jengelh Banned @tjoen last edited by

      @tjoen said in core-8.7.80.119 difficult to build but succeeded:

      make attempts to link with old lib*.so.0

      make does not do anything in that regard, it’s just a trivial program invoking other commands.

      lib*.so.0 (not lib*.so)

      That just makes no sense on its own.

      tjoen 1 Reply Last reply Reply Quote 0
      • tjoen
        tjoen @jengelh last edited by

        @jengelh
        Something wrong in the Makefiles. If headers, lib*.so and lib*.la are removed then the build should not link to system lib*.so.0
        I haven’t looked at the details how that is possible but removing/uninstalling kopano’s lib*.so.* was the easiest way to get it built

        1 Reply Last reply Reply Quote 0
        • jengelh
          jengelh Banned last edited by

          There is nothing wrong in the Makefile, the project looks like any other that uses automake.

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

            So why is my first build linking to system kopano-libs?

            1 Reply Last reply Reply Quote 0
            • jengelh
              jengelh Banned last edited by

              You fiddled with some part of your system, I suppose.

              tjoen 1 Reply Last reply Reply Quote 0
              • tjoen
                tjoen @jengelh last edited by tjoen

                @jengelh

                /root/.bash_history:
rpm -e kopanocore-devel
rpm -U vmime-0.9.2-3.x86_64.rpm 
cd /etc/systemd/system/multi-user.target.wants/
for i in kopano-* ; do systemctl stop $i ; done
cd -
rpm -i libHX-3.24-1.x86_64.rpm 
rpm -e kopanocore
rpm -i kopanocore-8.7.80.119-1.x86_64.rpm

                Other packages don’t have that problem:

                # grep "^rpm -[Ui]" .bash_history |grep x86_64
rpm -U libepoxy-1.5.3-1.x86_64.rpm 
rpm -U libsoup-2.64.2-1.x86_64.rpm 
rpm -U shared-mime-info-1.10-1.x86_64.rpm 
rpm -U fribidi-1.0.5-1.x86_64.rpm 
rpm -U cairo-1.15.14-1.x86_64.rpm 
rpm -U gtk3-3.24.1-1.x86_64.rpm 
rpm -U xkbcomp-1.4.2-1.x86_64.rpm 
rpm -U --nodeps xkbcomp-1.4.2-1.x86_64.rpm 
rpm -U vim-8.1.0513-1.x86_64.rpm 
rpm -U avahi-0.7-3.x86_64.rpm 
rpm -U gstreamer-1.14.4-1.x86_64.rpm 
rpm -U gst-plugins-base-1.14.4-1.x86_64.rpm 
rpm -U librsvg-2.44.8-1.x86_64.rpm 
rpm -U soundtouch-2.1.0-1.x86_64.rpm 
rpm -U gst-plugins-bad-1.14.4-1.x86_64.rpm 
rpm -U MarkupSafe-1.1.0-1.x86_64.rpm 
rpm -U libinput-1.12.3-1.x86_64.rpm 
rpm -U DBI-1.642-1.x86_64.rpm 
rpm -U mariadb-10.3.10-1.x86_64.rpm 
rpm -U libical-3.0.4-1.x86_64.rpm 
rpm -U bluez-5.50-1.x86_64.rpm 
rpm -U yaml-0.2.1-1.x86_64.rpm 
rpm -U PyYAML-3.13-1.x86_64.rpm 
rpm -U lirc-0.10.1-2.x86_64.rpm 
rpm -U pulseaudio-12.2-1.x86_64.rpm 
rpm -i --force  pulseaudio-12.2-1.x86_64.rpm 
rpm -i pygpgme-0.3-1.x86_64.rpm 
rpm -U qt-everywhere-5.11.2-1.x86_64.rpm 
rpm -U gpgme-1.12.0-1.x86_64.rpm 
rpm -U ldb-1.4.2-1.x86_64.rpm 
rpm -i rpcsvc-proto-1.4-1.x86_64.rpm 
rpm -U samba-4.9.1-1.x86_64.rpm 
rpm -U dbus-python-1.2.8-2.x86_64.rpm 
rpm -U boost-1.68.0-1.x86_64.rpm 
rpm -U boost-1.68.0-1.x86_64.rpm > ~tdance/log 2>&1
rpm -i --force boost-1.68.0-1.x86_64.rpm > ~tdance/log 2>&1
rpm -i boost-devel-1.68.0-1.x86_64.rpm 
rpm -U ruby-2.5.3-1.x86_64.rpm 
rpm -U numpy-1.15.4-1.x86_64.rpm 
rpm -U wrapt-1.10.11-3.x86_64.rpm 
rpm -U webkitgtk-2.22.3-1.x86_64.rpm 
rpm -U lxml-4.2.5-1.x86_64.rpm 
rpm -U leatherman-1.5.3-1.x86_64.rpm 
rpm -U facter-3.12.1-1.x86_64.rpm 
rpm -U netifaces-0.10.7-1.x86_64.rpm 
rpm -U msgpack-python-0.5.6-2.x86_64.rpm 
rpm -U msgpack-python-0.5.6-2.x86_64.rpm 
rpm -U msgpack-0.5.6-1.x86_64.rpm 
rpm -U --nodeps msgpack-0.5.6-1.x86_64.rpm 
rpm -U cffi-1.11.5-2.x86_64.rpm 
rpm -U cryptography-2.3.1-1.x86_64.rpm 
rpm -U greenlet-0.4.15-1.x86_64.rpm 
rpm -U PyNaCl-1.3.0-1.x86_64.rpm 
rpm -U bcrypt-3.1.4-2.x86_64.rpm 
rpm -U SQLAlchemy-1.2.13-1.x86_64.rpm 
rpm -U psutil-5.4.8-1.x86_64.rpm 
rpm -U simplejson-3.16.0-1.x86_64.rpm 
rpm -U mod_wsgi-4.6.5-1.x86_64.rpm 
rpm -U pycrypto-2.6.1-2.x86_64.rpm 
rpm -U zope.interface-4.6.0-1.x86_64.rpm 
rpm -U memcached-1.5.12-1.x86_64.rpm 
rpm -U scrypt-0.8.6-2.x86_64.rpm 
rpm -U dmidecode-3.2-1.x86_64.rpm 
rpm -U iptables-1.8.2-1.x86_64.rpm 
rpm -U iptables-1.8.2-1.x86_64.rpm 
rpm -U --nodeps iptables-1.8.2-1.x86_64.rpm 
rpm -U libvirt-4.9.0-1.x86_64.rpm 
rpm -U libvirt-devel-4.9.0-1.x86_64.rpm 
rpm -U libvirt-python-4.9.0-1.x86_64.rpm 
rpm -U texinfo-6.5-2.x86_64.rpm 
rpm -U qemu-3.0.0-1.x86_64.rpm 
rpm -U postgresql-11.1-1.x86_64.rpm 
rpm -U mdadm-4.1-1.x86_64.rpm 
rpm -U exim-4.91-2.x86_64.rpm 
rpm -U vmime-0.9.2-3.x86_64.rpm 
rpm -i libHX-3.24-1.x86_64.rpm 
rpm -i kopanocore-8.7.80.119-1.x86_64.rpm 
rpm -U binutils-2.31.1-1.x86_64.rpm 
rpm -U bison-3.2.1-1.x86_64.rpm 
rpm -i lzip-1.20-1.x86_64.rpm 
rpm -U ed-1.14.2-1.x86_64.rpm 
rpm -U go-1.11.2-1.x86_64.rpm 
rpm -U libuv-v1.24.0-1.x86_64.rpm 
rpm -U cmake-3.12.4-1.x86_64.rpm
                1 Reply Last reply Reply Quote 0
                • jengelh
                  jengelh Banned last edited by

                  rpm -i kopanocore-8.7.80.119-1.x86_64.rpm

                  That is not one of our packages, and since I (also) have not looked at its contents, I can not say for sure what effects its presence has on building KC from source.

                  tjoen 1 Reply Last reply Reply Quote 0
                  • tjoen
                    tjoen @jengelh last edited by

                    @jengelh said

                    since I (also) have not looked at its contents, I can not say for sure what effects its presence has on building KC from source.

                    You had to say that in the first place instead of blaming my system

                    1 Reply Last reply Reply Quote 0
                    • jengelh
                      jengelh Banned last edited by

                      You’re not really giving me much to work with. The answer will necessarily be fuzzy and encompass everything under the sun. It just so happens that the of installed packages, files and their contents does comprise a “system”, so short of blaming the user, blaming the system is accurate.

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

                        On my LFS system kopanocore is the first package that links to system kopanocore-libs even after uninstalling kopanocore-devel package. For me it was a surprise. My posting is to help others who try to build kopano from source.

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

                          Just found in my notitions that net-snmp has the same problem. Needs to uninstall the whole pacckage before building

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