Date: Fri, 4 Aug 2006 17:37:32 +0300 From: Kostik Belousov <kostikbel@gmail.com> To: Daniel Eischen <deischen@freebsd.org> Cc: John-Mark Gurney <gurney_j@resnet.uoregon.edu>, freebsd-current@freebsd.org, Steve Kargl <sgk@troutmask.apl.washington.edu>, Andrew Thompson <thompsa@freebsd.org>, "Matthew D. Fuller" <fullermd@over-yonder.net> Subject: Re: Where is thr_getscheduler Message-ID: <20060804143732.GG59809@deviant.kiev.zoral.com.ua> In-Reply-To: <Pine.GSO.4.64.0608040851320.18587@sea.ntplx.net> References: <Pine.GSO.4.64.0608011657040.1810@sea.ntplx.net> <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> <Pine.GSO.4.64.0608021303120.7796@sea.ntplx.net> <20060802172505.GA1935@troutmask.apl.washington.edu> <20060804050242.GC58082@funkthat.com> <Pine.GSO.4.64.0608040851320.18587@sea.ntplx.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060804143732.GG59809>