> -----Original Message----- > From: [email protected] [mailto:[email protected]] On > Behalf Of Natanael Copa > Sent: den 9 april 2010 10:08 > To: Bernhard Reutner-Fischer > Cc: [email protected] > Subject: Re: problems with gnu make and stdout with uclibc nptl > > On Thu, Apr 8, 2010 at 8:40 AM, Natanael Copa <[email protected]> > wrote: > > On Wed, Apr 7, 2010 at 11:20 PM, Bernhard Reutner-Fischer > > <[email protected]> wrote: > >> Does it still happen if you build master with LT_OLD and O0 (i.e. > >> DODEBUG set)? > > > > Enabling runtime assertions did give an interesting result: > > > > make: libc/stdio/_stdio.c: 326: _stdio_validate_FILE: Assertion > > `stream->__modeflags == (0x0020U|0x0010U)' failed. > > The problem comes from 885f507317b6c8576ba2e298c2249d27ea6f8404 which > breaks ABI compat and the gnu make i used was built against previous > uclibc headers things went wrong. > > I think it would be nice if the MAJOR_VERSION changed every time the > ABI changed as it gives people who does not do firmware style upgrades > (i.e package managers) a chance to do clean upgrades. > > I think this alone is more than good enough reason to let next release > be 1.x in stead of 0.9.32. (It still leaves 0.9.31 release as > non-upgradeable) > > thanks! > > -- > Natanael Copa
Unless it has changed in the last years, there are no expressed guarantees regarding API and ABI stability for the 0.x.y releases of uClibc. AFAIK the stable API/ABI is intended for the 1.0.0 release. And with the upcoming integration of the NPTL support, I do not see this as the right time to go to 1.0.0 and lock down the API/ABI... //Peter _______________________________________________ uClibc mailing list [email protected] http://lists.busybox.net/mailman/listinfo/uclibc
