Policy on static linking ?

Jim Pingle lists at pingle.org
Sat Jan 15 16:35:45 UTC 2011

On 1/15/2011 5:11 AM, Jean-Yves Avenard wrote:
> If I compile openldap-client against openssl from ports, then it
> creates massive problems elsewhere.
[snip problems]
> I dislike this method, because should openldap gets upgraded again and
> be linked against openssl port, I will lock myself out of the machine
> again due to sshd crashing. Just like what happened today :(

Problems like that are why I do my package compiling in a jail, or a VM,
and not on a live system. Jails are simple to setup these days and it's
handy to be able to just blow away the jail and recreate it if things go
wonky with dependencies when experimenting with package builds. (Or
snapshot a VM before trying)

I've taken a stab or two at compiling ports static in the past and also
came up empty.

It would be really nice to be able to build a single tbz package that
would run once installed and that didn't have to pull down every other
dependency individually. There are a number of ways that dependency
tracking with packages can go sideways, and it isn't fun when trying to
ensure that said packages install OK when transplanting them to other


More information about the freebsd-stable mailing list