[torquedev] Release Candidate for TORQUE 2.5.8

Ken Nielson knielson at adaptivecomputing.com
Wed Aug 24 16:35:49 MDT 2011

----- Original Message -----
> From: "Martin Siegert" <siegert at sfu.ca>
> To: "Torque Developers mailing list" <torquedev at supercluster.org>
> Sent: Thursday, August 18, 2011 2:48:38 PM
> Subject: Re: [torquedev] Release Candidate for TORQUE 2.5.8
> On Tue, Aug 16, 2011 at 04:04:26PM -0600, Ken Nielson wrote:
> >
> I just compiled this by accident with gcc-4.4.0 (instead of gcc-4.1.2
> which I usually use). gcc-4.4.0 spits out even more errors:
> cc1: warnings being treated as errors
> job_route.c: In function ‘initialize_procct’:
> job_route.c:210: error: ‘pprocsp’ may be used uninitialized in this
> function
> make[2]: *** [job_route.o] Error 1
> This can be fixed by adding a line
> pprocsp = NULL;
> before the
> if(pprocs_def != NULL)
> statement.
> But then:
> cc1: warnings being treated as errors
> process_request.c: In function ‘get_creds’:
> process_request.c:288: error: dereferencing type-punned pointer will
> break strict-aliasing rules
> make[2]: *** [process_request.o] Error 1
> Which can be fixed by dropping the optimization flag below -O2.
> Don't know whether there is a better way to solve this one.
> - Martin

I set --enable-unixsockets in my configure line and got a boatload of errors related to this code. I am using gcc version 4.5.2. 

I found I could get the code to compile successfully if I manually added _GNU_SOURCE to the Makefile. Otherwise "struct ucred" does not get defined leading to the type-punned kind of error and many others. I do not know if this is a gcc header bug or not.

We could add _GNU_SOURCE as a configure option. But what about other OS versions. Do we fix them one at a time as they come up?

I am appealing to those with more compiler and build expertise than me.



More information about the torquedev mailing list