Sane way to resolve potential conflicts in the system

Odhiambo Washington odhiambo at
Sat Apr 23 12:00:52 UTC 2016

On 23 April 2016 at 14:35, Ben Woods <woodsb02 at> wrote:

> On 23 April 2016 at 13:03, Odhiambo Washington <odhiambo at> wrote:
>> I quite often get the following warning:
>> /usr/bin/ld: warning:, needed by /usr/local/lib/, may
>> conflict with
>> /usr/bin/ld: warning:, needed by /usr/local/lib/,
>> may
>> conflict with
>> 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

I always do that.

> 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.

I believe that explains it. I should plan a portupgrade -a one of these
days I suppose. However, doing that on a production server (from remote) is
such a scary thing:)
Is there a way to address just these two cases for now?


Best regards,
+254 7 3200 0004/+254 7 2274 3223
"Oh, the cruft."

More information about the freebsd-questions mailing list