From owner-freebsd-arch@FreeBSD.ORG Wed Mar 26 12:30:13 2003 Return-Path: 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 CF1DC37B404 for ; Wed, 26 Mar 2003 12:30:13 -0800 (PST) Received: from harmony.village.org (rover.bsdimp.com [204.144.255.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15C8543F85 for ; Wed, 26 Mar 2003 12:30:13 -0800 (PST) (envelope-from imp@harmony.village.org) Received: from harmony.village.org (localhost [127.0.0.1]) by harmony.village.org (8.12.8/8.12.3) with ESMTP id h2QKU6A7089578; Wed, 26 Mar 2003 13:30:06 -0700 (MST) (envelope-from imp@harmony.village.org) Message-Id: <200303262030.h2QKU6A7089578@harmony.village.org> To: Daniel Eischen In-reply-to: Your message of "Wed, 26 Mar 2003 13:51:39 EST." <3E81F6BB.BFFE3F33@vigrid.com> References: <3E81F6BB.BFFE3F33@vigrid.com> Date: Wed, 26 Mar 2003 13:30:06 -0700 From: Warner Losh X-Spam-Status: No, hits=-9.9 required=5.0 tests=IN_REP_TO,REFERENCES autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: arch@freebsd.org cc: kse@elischer.org Subject: Re: Not providing static libraries (libkse/libpthread) X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 20:30:14 -0000 In message <3E81F6BB.BFFE3F33@vigrid.com> Daniel Eischen writes: : Is there a good reason for providing static libraries for : libpthread/libkse? I'd like to not support them to get : rid of some hacks to make sure certain symbols are present : in the static library case. That would be a big hassle for the company I work for. We have many static binaries that are threaded and providing a dynamic one has a performance impact of a few percent. While we have done dynamic linking in the past, and have the infrastructure to do so in the future in our build process, this may cause us problems in the future if we need to deploy a static binary (which tends to be safer to do once a long period of time has passed between the generation of the system and the deployment of the updated binary). How gross are the hacks? Warner