Date: Fri, 01 Jun 2012 10:15:19 +0100 From: Matthew Seaman <matthew@FreeBSD.org> To: Damien Fleuriot <ml@my.gd> Cc: freebsd-stable@FreeBSD.org, Jim Ohlstein <jim@ohlste.in> Subject: Re: Why Are You Using FreeBSD? Message-ID: <4FC88827.8020003@FreeBSD.org> In-Reply-To: <4FC87A60.3020102@my.gd> References: <C480320C-0CD9-4B61-8AFB-37085C820AB7@FreeBSD.org> <4FC779C0.7020801@ohlste.in> <4FC77EAD.1090900@my.gd> <4FC78A94.8070008@ohlste.in> <4FC79136.6000205@my.gd> <4FC7B4CC.1070507@FreeBSD.org> <4FC87A60.3020102@my.gd>
next in thread | previous in thread | raw e-mail | index | archive | help
This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig70901832685804646AC5AAAC Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On 01/06/2012 09:16, Damien Fleuriot wrote: > The reason I rebuild the ports last is because, unless I'm wrong, any > port that's statically linked to a system library would be linked to th= e > old library from the old world. Uh -- if it's statically linked, then the object code is copied from the library into the executable image. There's no dependency between the static library and the executable once the executable has been produced. However, ports very rarely use static linkage, and even more rarely use static linkage against system libraries. Even if the system library did change, that wouldn't trigger a rebuild of the port, as there's no version number to trigger it. You could, I suppose, rebuild every port for every system update, but this would be a huge waste of time and CPU power. There have been occasions where eg. there has been a security update to one of the OpenSSL libraries in base, and the security advisory has recommended rebuilding statically linked binaries, but that only happened once in about 10 years. Cheers, Matthew --=20 Dr Matthew J Seaman MA, D.Phil. PGP: http://www.infracaninophile.co.uk/pgpkey --------------enig70901832685804646AC5AAAC Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.16 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk/IiC8ACgkQ8Mjk52CukIznfgCeKzKZT+ncTRJYvk24jR5xRA+b Ue8An18YUMZ5a04WFmKwo0lRiM/d//PM =dpcs -----END PGP SIGNATURE----- --------------enig70901832685804646AC5AAAC--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4FC88827.8020003>