Date: Sat, 23 Apr 2016 13:35:00 +0200 From: Ben Woods <woodsb02@gmail.com> To: Odhiambo Washington <odhiambo@gmail.com> Cc: User Questions <freebsd-questions@freebsd.org> Subject: Re: Sane way to resolve potential conflicts in the system Message-ID: <CAOc73CC57yjqteXrZZd%2Bs2Z353r9AycG39mf9f136hGaY=iTzQ@mail.gmail.com> In-Reply-To: <CAAdA2WPZiBYxK9XL_ToAvWtQOiJ0Da7fqVBinyq10%2BMC10zz6A@mail.gmail.com> References: <CAAdA2WPZiBYxK9XL_ToAvWtQOiJ0Da7fqVBinyq10%2BMC10zz6A@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 April 2016 at 13:03, Odhiambo Washington <odhiambo@gmail.com> wrote: > I quite often get the following warning: > > /usr/bin/ld: warning: libz.so.5, needed by /usr/local/lib/libcurl.so, may > conflict with libz.so.6 > /usr/bin/ld: warning: libz.so.4, needed by /usr/local/lib/libssh2.so.1, may > conflict with libz.so.6 > > What is the best way to resolve the two? It looks like you have not been removing old libraries when updating your base system. Have you been updating from source? If so, one of the last steps you should follow (after reboot and rebuilding all packages to suit the new system), you should be using: $ cd /usr/src $ make check-old-libs $ make delete-old-libs Beware - if you haven't rebuild your packages on the new source tree, they may be linking to old base system libraries, and break if you now remove them. Rebuild all packages first. Regards, Ben
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAOc73CC57yjqteXrZZd%2Bs2Z353r9AycG39mf9f136hGaY=iTzQ>