core-8.7.80.119 difficult to build but succeeded
-
@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 -
There is nothing wrong in the Makefile, the project looks like any other that uses automake.
-
So why is my first build linking to system kopano-libs?
-
You fiddled with some part of your system, I suppose.
-
/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
-
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.
-
@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
-
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.
-
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.
-
Just found in my notitions that net-snmp has the same problem. Needs to uninstall the whole pacckage before building