Sane way to resolve potential conflicts in the system

Roland Smith rsmith at
Sun Apr 24 22:42:27 UTC 2016

On Sat, Apr 23, 2016 at 02:03:40PM +0300, Odhiambo Washington 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

Looks like your ports need updating!

> What is the best way to resolve the two?

Use a local server (or a jail on your workstation) as a build and test server.
On that server, keep the ports tree up-to-date and use e.g. portmaster to
build all ports you need on *any* server.

Then use rsync to distribute that server's /usr/local/ and /var/db/pkg/ to
other servers. This is relatively fast and easy to automate. Of course this
only works if all machines run the same architecture and major version.

Note that after the /usr/local update, you need to re-install the local
configuration files in /usr/local/etc and re-start the services running from
/usr/local on every machine.

This does mean that some machines will have software installed that they don't
need.  But as long as any services among them aren't enabled in rc.conf, I'd
consider that acceptable for the sake of simplicity.  But if necessary, you
could make scripts to ‘pkg delete’ the stuff you don't need on a per-machine

[plain text _non-HTML_ PGP/GnuPG encrypted/signed email much appreciated]
pgp: 5753 3324 1661 B0FE 8D93  FCED 40F6 D5DC A38A 33E0 (keyID: A38A33E0)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <>

More information about the freebsd-questions mailing list