Date: Mon, 13 Jun 2005 18:10:34 +0100 From: Doug Rabson <dfr@nlsystems.com> To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) Cc: arch@freebsd.org, Julian Elischer <julian@elischer.org>, freebsd-arch@freebsd.org Subject: Re: Retiring static libpam support Message-ID: <8510490ff3a56e4ffcc127064b260caf@nlsystems.com> In-Reply-To: <86ll5eyzg0.fsf@xps.des.no> References: <864qc9mgqc.fsf@xps.des.no> <42A75303.2090203@elischer.org> <42A75591.7080502@elischer.org> <200506130849.26026.dfr@nlsystems.com> <86ll5eyzg0.fsf@xps.des.no>
next in thread | previous in thread | raw e-mail | index | archive | help
On 13 Jun 2005, at 17:49, Dag-Erling Sm=F8rgrav wrote: > Doug Rabson <dfr@nlsystems.com> writes: >> You can link statically to some libraries and dynamically to others >> - that might work quite well. You would probably end up linking >> dynamically to libc otherwise you might get two copies of libc when >> you load a pam module. > > That won't help. You'll still end up with two copies of *libpam*. It depends exactly what Julian needs to link with statically - it=20 wasn't clear. When I build my own software 'statically' I tend to still=20= link to the system libraries dynamically.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8510490ff3a56e4ffcc127064b260caf>