Date: Mon, 13 Jun 2005 18:49:19 +0200 From: des@des.no (=?iso-8859-1?q?Dag-Erling_Sm=F8rgrav?=) To: Doug Rabson <dfr@nlsystems.com> Cc: arch@freebsd.org, Julian Elischer <julian@elischer.org>, freebsd-arch@freebsd.org Subject: Re: Retiring static libpam support Message-ID: <86ll5eyzg0.fsf@xps.des.no> In-Reply-To: <200506130849.26026.dfr@nlsystems.com> (Doug Rabson's message of "Mon, 13 Jun 2005 08:49:25 %2B0100") References: <864qc9mgqc.fsf@xps.des.no> <42A75303.2090203@elischer.org> <42A75591.7080502@elischer.org> <200506130849.26026.dfr@nlsystems.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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*. DES --=20 Dag-Erling Sm=F8rgrav - des@des.no
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?86ll5eyzg0.fsf>