From owner-freebsd-arch@FreeBSD.ORG Mon Jun 13 17:34:11 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 90AAC16A420; Mon, 13 Jun 2005 17:34:11 +0000 (GMT) (envelope-from julian@elischer.org) Received: from bigwoop.vicor-nb.com (bigwoop.vicor-nb.com [208.206.78.2]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4026143D5C; Mon, 13 Jun 2005 17:34:11 +0000 (GMT) (envelope-from julian@elischer.org) Received: from [208.206.78.97] (julian.vicor-nb.com [208.206.78.97]) by bigwoop.vicor-nb.com (Postfix) with ESMTP id 222807A403; Mon, 13 Jun 2005 10:34:11 -0700 (PDT) Message-ID: <42ADC393.5080706@elischer.org> Date: Mon, 13 Jun 2005 10:34:11 -0700 From: Julian Elischer User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.7) Gecko/20050423 X-Accept-Language: en, hu MIME-Version: 1.0 To: Doug Rabson References: <864qc9mgqc.fsf@xps.des.no> <42A75303.2090203@elischer.org> <42A75591.7080502@elischer.org> <200506130849.26026.dfr@nlsystems.com> <86ll5eyzg0.fsf@xps.des.no> <8510490ff3a56e4ffcc127064b260caf@nlsystems.com> In-Reply-To: <8510490ff3a56e4ffcc127064b260caf@nlsystems.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit Cc: =?ISO-8859-1?Q?Dag-Erling_Sm=F8rgrav?= , freebsd-arch@freebsd.org, 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:34:11 -0000 Doug Rabson wrote: > > On 13 Jun 2005, at 17:49, Dag-Erling Smørgrav 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 > wasn't clear. When I build my own software 'statically' I tend to > still link to the system libraries dynamically. We tend to try build fully static binaries as that reduces the number of support calls we get due to mismatched libraries. the answer may be to staticaly link 90%.. i.e everything except libc or something similar.