From owner-freebsd-current@FreeBSD.ORG Fri Aug 4 14:37:41 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 E58A416A4DA; Fri, 4 Aug 2006 14:37:40 +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 2474E43D49; Fri, 4 Aug 2006 14:37:39 +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 k74EfwBe068087 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 4 Aug 2006 17:41:58 +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 k74EbYNN046494; Fri, 4 Aug 2006 17:37:34 +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 k74EbWgF046493; Fri, 4 Aug 2006 17:37:32 +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 17:37:32 +0300 From: Kostik Belousov To: Daniel Eischen Message-ID: <20060804143732.GG59809@deviant.kiev.zoral.com.ua> References: <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="IvGM3kKqwtniy32b" Content-Disposition: inline In-Reply-To: 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: John-Mark Gurney , freebsd-current@freebsd.org, Steve Kargl , Andrew Thompson , "Matthew D. Fuller" 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 14:37:41 -0000 --IvGM3kKqwtniy32b Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Fri, Aug 04, 2006 at 08:57:52AM -0400, Daniel Eischen wrote: > On Thu, 3 Aug 2006, John-Mark Gurney wrote: >=20 > >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. > > > >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? >=20 > We have symbol versioning but it isn't enabled by default > yet. We're waiting for the library versions to be bumped > before enabling it. We can't support old non-symbol-versioned > ABIs (e.g. libc.so.6) in a symbol-versioned library so we > need to bump the library versions before enabling it. Hmm, yes, libc versioning is disabled. I looked at the libpthread/libthr. Then, why versioning for threaded libraries is on ? BTW, as far as I know, there is technical possibility to declare the "unspecified" version for the symbol (like .symver XXX_old,XXX@ ), but I agree that deciding when to do that when libc.so.7 already broke the ABI in unknown locations is too hard. --IvGM3kKqwtniy32b Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (FreeBSD) iD8DBQFE01usC3+MBN1Mb4gRAujmAJ4wPw1b4KkeKjuqAioK9sL3X2a1cwCdGZXr TDZlJvz6ViLrxDobSHLE/Lw= =LVDq -----END PGP SIGNATURE----- --IvGM3kKqwtniy32b--