On Fri, 14 Dec 2007, Alexander Kabaev wrote: > On Fri, 14 Dec 2007 00:48:51 -0500 (EST) > Daniel Eischen <[EMAIL PROTECTED]> wrote: > > On Thu, 13 Dec 2007, Alexander Kabaev wrote: > > > > At a minimum, we need to create one new namespace in each > > release branched from -current when there is one or more > > ABI changes from the prior release. Perhaps we should just > > move to FBSD_1.1 now in 8-current just to make things easier. > > When we go to 9-current, we move to FBSD_1.2, etc. If you > > need to backport changes back to 7.x, then you also have to > > create the matching version in 7.x. > > I think this was our understanding last time, but I wanted to check > that I didn't forget anything. Adding symbols o FBSD_1.0 does not > technically breaks ABI, but creates namespace that is a superset of one > existing in 7.0. The 'classic' use of symbol versioning requires rtld > to check all the namespace dependencies recorded for the binary, and > the fact that namespace X exists in some library indicates that _all_ > symbols from X are there and binary can run with this particular > version of the library. Extending FBSD_1.0 breaks this.
But won't MFCing a subset of FBSD_1.1 from 8-CURRENT to 7.1-RELEASE result in the same problem? FBSD_1.1 will exist in the library, but the library won't have any symbols from FBSD_1.1 that haven't been MFCed (probably most of them). -- David Taylor _______________________________________________ cvs-all@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/cvs-all To unsubscribe, send any mail to "[EMAIL PROTECTED]"