From owner-freebsd-arch@FreeBSD.ORG Mon Jun 13 17:10:54 2005 Return-Path: X-Original-To: arch@freebsd.org Delivered-To: freebsd-arch@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 416F116A41C; Mon, 13 Jun 2005 17:10:54 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from mail.qubesoft.com (gate.qubesoft.com [217.169.36.34]) by mx1.FreeBSD.org (Postfix) with ESMTP id A4A8C43D48; Mon, 13 Jun 2005 17:10:53 +0000 (GMT) (envelope-from dfr@nlsystems.com) Received: from [192.168.1.254] (dhcp254.qubesoft.com [192.168.1.254]) by mail.qubesoft.com (8.13.3/8.13.3) with ESMTP id j5DHAYjf013371; Mon, 13 Jun 2005 18:10:35 +0100 (BST) (envelope-from dfr@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> Mime-Version: 1.0 (Apple Message framework v622) Content-Type: text/plain; charset=ISO-8859-1; format=flowed Message-Id: <8510490ff3a56e4ffcc127064b260caf@nlsystems.com> Content-Transfer-Encoding: quoted-printable From: Doug Rabson Date: Mon, 13 Jun 2005 18:10:34 +0100 To: des@des.no (=?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?=) X-Mailer: Apple Mail (2.622) X-Spam-Status: No, score=-2.8 required=5.0 tests=ALL_TRUSTED autolearn=failed version=3.0.1 X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on mail.qubesoft.com Cc: arch@freebsd.org, Julian Elischer , freebsd-arch@freebsd.org Subject: Re: Retiring static libpam support X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 13 Jun 2005 17:10:54 -0000 On 13 Jun 2005, at 17:49, Dag-Erling Sm=F8rgrav wrote: > Doug Rabson 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.