Re: Please test pending bugfix release of base

[Sebastian Reitenbach]

Hi again,

On Saturday, June 18, 2011 12:10 CEST, "Sebastian Reitenbach" 
<sebastia@l00-bugdead-prods.de> wrote:

>
> Hi Richard,
>
> On Saturday, June 18, 2011 09:41 CEST, Richard Frith-Macdonald <rfm@gnu.org> 
> wrote:
>
> >
> > On 17 Jun 2011, at 11:39, Quentin Mathé wrote:
> >
> > > Hi Richard,
> > > > Le 16 juin 2011 à 09:58, Richard Frith-Macdonald a écrit :
> > > >> It's long enough now since the last release that I'd like to make a 
> > > >> bugfix release of the base library (going from 1.22.0 to 1.22.1).
> > >> This release is mostly for portability issues, but there are fixes to 
> > >> atomic operations used for retain/release safety, which would be 
> > >> important to threaded software, so we really should make a release for 
> > >> tis alone.
> > >> The idea is not to add any new features, just to make things even more 
> > >> reliable and portable.
> > >> >> Please could people (especially those with unusual hardware and/or 
> > >> >> obscure/old operating systems) give this a try so we can make this 
> > >> >> release as portable and reliable as possible.
> > >> >> You can get hold of the pre-release code using subversion from 
> > >> >> svn://svn.gna.org/svn/gnustep/libs/base/branches/stable
> > >> If there is anyone who really can't use subversion but would like to try 
> > >> this, please let me know and I'll send you a .tar.gz archive of the 
> > >> source (approx 3MB email).
> > > > > Base seems to work pretty well in my case currently.
> > > > However what I observe is that valgrind reports many memory leaks, even 
> > > > with a progam that does nothing (see code below), and this means it's 
> > > > hard to track down a memory corruption with valgrind. The output 
> > > > becomes really huge (several MB) when you run a real application or 
> > > > tool.
>
> I tested compiled it on OpenBSD sparc, and found a problem while linking 
> autogsdoc.

attached patches I also have in the ports tree since testing 
gnustep-base-1.22.0. While I was testing there with clang, I spit out a couple 
of compiler warnings, including suggestions how to fix it. So I followed the 
suggestions to shut up clang.

Sebastian

fix-compiler-warnings-with-clang.diff
Description: Binary data