From owner-freebsd-arch@FreeBSD.ORG Fri Apr 22 18:27:27 2005 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 CF1EF16A4CE; Fri, 22 Apr 2005 18:27:27 +0000 (GMT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id A715243D39; Fri, 22 Apr 2005 18:27:27 +0000 (GMT) (envelope-from sgk@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) j3MIRRSO002833; Fri, 22 Apr 2005 11:27:27 -0700 (PDT) (envelope-from sgk@troutmask.apl.washington.edu) Received: (from sgk@localhost)j3MIRRgb002832; Fri, 22 Apr 2005 11:27:27 -0700 (PDT) (envelope-from sgk) Date: Fri, 22 Apr 2005 11:27:27 -0700 From: Steve Kargl To: Scott Long Message-ID: <20050422182727.GA2753@troutmask.apl.washington.edu> References: <20050422103141.F5855@carver.gumbysoft.com> <20050422174209.GA97721@troutmask.apl.washington.edu> <42693837.7090400@samsco.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <42693837.7090400@samsco.org> User-Agent: Mutt/1.4.2.1i cc: peter@freebsd.org cc: freebsd-arch@freebsd.org Subject: Re: libpthread version bump 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: Fri, 22 Apr 2005 18:27:27 -0000 On Fri, Apr 22, 2005 at 11:45:27AM -0600, Scott Long wrote: > Steve Kargl wrote: > > > >A workaround may be the use of libmap.conf to map libc.so.5 > >to libc.so.6. > > > > Well, we are talking about formally ensuring that 5.x compatibility > works for 6.0 when it's released. Telling users to do a hack with > libmap doesn't really match what we need. > Having lived through the std{io,err,out} libc snafu, the libm.so.2 snafu, and now the libc.so.5/libpthread.so.1 problem, I will once again suggest that *ALL* library version numbers should be bumped when a new branch is created. Yes, the above suggestion is a hack workaround, but I know that it works for me with one commercial application that I can't simply recompile. -- Steve