[torquedev] Release Candidate for TORQUE 2.5.8

Ken Nielson knielson at adaptivecomputing.com
Tue Aug 23 14:26:07 MDT 2011


Thanks for chiming in. GCC warnings did get turned off by default with one of the fixes to the RPM build files. We noticed it a month or two after the patch was committed. Now we usually build with gcc-warnings enabled but we do forget sometimes. It is good to have the community point out when these errors occur. That is why we make release candidates.



----- Original Message -----
> From: "Michael Jennings" <mej at lbl.gov>
> To: torquedev at supercluster.org
> Sent: Tuesday, August 23, 2011 12:04:11 PM
> Subject: Re: [torquedev] Release Candidate for TORQUE 2.5.8
> On Tuesday, 23 August 2011, at 06:47:51 (-0400),
> Glen Beane wrote:
> > You make some good points. I hope all developers use
> > --enable-gcc-warnings (it looks like some warnings did slip through
> > though). It is also helpful to have people out in the community
> > reporting warnings back to the developers.
> I agree. It would be good for the Adaptive folks and other
> contributors to build with warnings so that potential missteps can be
> corrected early. But it's important to keep in mind that gcc's
> warning settings (defaults, groupings, and available options) change
> with every release, and code that built warning-free in a previous
> version will often have warnings (and sometimes even errors!) in newer
> versions. So we should endeavour to quantify expectations and targets
> (and be realistic about the fact that "no warnings" is very much a
> moving target). :-)
> Michael
> --
> Michael Jennings <mej at lbl.gov>
> Linux Systems and Cluster Engineer
> High-Performance Computing Services
> Bldg 50B-3209E W: 510-495-2687
> MS 050C-3396 F: 510-486-8615
> _______________________________________________
> torquedev mailing list
> torquedev at supercluster.org
> http://www.supercluster.org/mailman/listinfo/torquedev

More information about the torquedev mailing list