From owner-freebsd-current@FreeBSD.ORG Fri Aug 4 08:20:59 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E0F8F16A4DD; Fri, 4 Aug 2006 08:20:58 +0000 (UTC) (envelope-from kostikbel@gmail.com) Received: from fw.zoral.com.ua (fw.zoral.com.ua [213.186.206.134]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1FDA543D49; Fri, 4 Aug 2006 08:20:57 +0000 (GMT) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (root@deviant.kiev.zoral.com.ua [10.1.1.148]) by fw.zoral.com.ua (8.13.4/8.13.4) with ESMTP id k748P9U3057410 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 11:25:10 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: from deviant.kiev.zoral.com.ua (kostik@localhost [127.0.0.1]) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6) with ESMTP id k748KqtP038057; Fri, 4 Aug 2006 11:20:52 +0300 (EEST) (envelope-from kostikbel@gmail.com) Received: (from kostik@localhost) by deviant.kiev.zoral.com.ua (8.13.6/8.13.6/Submit) id k748Ko5D038056; Fri, 4 Aug 2006 11:20:50 +0300 (EEST) (envelope-from kostikbel@gmail.com) X-Authentication-Warning: deviant.kiev.zoral.com.ua: kostik set sender to kostikbel@gmail.com using -f Date: Fri, 4 Aug 2006 11:20:50 +0300 From: Kostik Belousov To: Steve Kargl , Daniel Eischen , freebsd-current@freebsd.org, Andrew Thompson , "Matthew D. Fuller" , kan@freebsd.org Message-ID: <20060804082050.GE59809@deviant.kiev.zoral.com.ua> References: <20060801204501.GA19647@troutmask.apl.washington.edu> <20060801211657.GA29737@troutmask.apl.washington.edu> <20060801212742.GB13841@heff.fud.org.nz> <20060801213803.GB9583@troutmask.apl.washington.edu> <20060802144255.GU69505@over-yonder.net> <20060802165604.GA970@troutmask.apl.washington.edu> <20060802172505.GA1935@troutmask.apl.washington.edu> <20060804050242.GC58082@funkthat.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VMt1DrMGOVs3KQwf" Content-Disposition: inline In-Reply-To: <20060804050242.GC58082@funkthat.com> User-Agent: Mutt/1.4.2.2i X-Virus-Scanned: ClamAV version 0.88.2, clamav-milter version 0.88.2 on fw.zoral.com.ua X-Virus-Status: Clean X-Spam-Status: No, score=0.4 required=5.0 tests=ALL_TRUSTED, DNS_FROM_RFC_ABUSE,SPF_NEUTRAL autolearn=no version=3.1.3 X-Spam-Checker-Version: SpamAssassin 3.1.3 (2006-06-01) on fw.zoral.com.ua Cc: Subject: Re: Where is thr_getscheduler X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 04 Aug 2006 08:20:59 -0000 --VMt1DrMGOVs3KQwf Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Aug 03, 2006 at 10:02:43PM -0700, John-Mark Gurney wrote: > Steve Kargl wrote this message on Wed, Aug 02, 2006 at 10:25 -0700: > > Almost everything on a FreeBSD system depends on libc. Bumping > > its version number without careful coordination of bumping all > > other version numbers is full of landmines. Falling back of the > > retort "this is -current expect problesm" just glosses over what > > appears to be sloppy planning.=20 >=20 > Ummm.. don't we have have symbol versioning? isn't this exactly > what symbol versioning is for? I haven't been following this > particular discussion, but I thought now that we have symbol versioning > in the tree that we never have to bump the numbers? or is this failure > to have a proper document to tell someone what to do when they change > the API and provide the correct hooks for the new versions? The situation on the problematic machine is follows: /lib contains libc.so.7, libc.so.6 and libthr.so.2 (version number for libthr is not bumped still). libc.so.7 and libpthread.so.2 contain versioned symbols, libc.so.6 is not versioned. Old build of the application linked against libc.so.6 and libthr.so.2. References to symbols in libthr.so.2 are satisfied by default version of the symbols.=20 Missing are two things: 1. libpthread/libthr are still not linked against libc (as well as most shared libraries). Correspondingly, version information for referenced libc symbols is absent in the shared libraries. 2. check for presence of the required version in the depended libraries is absent too, IMHO. Given these two issues are resolved, libthr.so.2 (and libpthread.so.2) references to libc would be unsatisfied with different diagnostic. I added kan@ to the mail loop, but he seems to be unreacheable for some time now. --VMt1DrMGOVs3KQwf Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE0wNgC3+MBN1Mb4gRAgqeAKCfIODC2cR9sXqkDzJwF6skB/ay6ACfZB/X IbcSGs/saBrqv6C3kn26gDY= =Vd28 -----END PGP SIGNATURE----- --VMt1DrMGOVs3KQwf--