Remove compiler warnings that we are currently suppressing

Registered by Lee Bieber on 2009-12-14

From Monty:

I've added a hudson job which builds drizzle with all of the warnings
enabled that we are currently suppressing. (except for strict-aliasing,
which I know is a lost cause at the moment)

http://hudson.drizzle.org/job/drizzle-build-all-warnings

You can see the build output here:

http://hudson.drizzle.org/job/drizzle-build-all-warnings/2/consoleFull

If anybody wants to start slowly banging out fixes to these, that would
be stellar. Most of them are not hard - so it shouldn't be to terrible
to get started.

I'd really like to be able to turn these on. I noticed from scanning
through that some of these are in new code (and some in code that I
wrote. *doh*) There's a reason we're pedantic on warnings, and it seems
like these have been neglected for far too long.

Blueprint information

Status:
Not started
Approver:
Monty Taylor
Priority:
Low
Drafter:
None
Direction:
Needs approval
Assignee:
None
Definition:
Approved
Series goal:
Accepted for trunk
Implementation:
Unknown
Milestone target:
milestone icon ongoing

Related branches

Sprints

Whiteboard

I started having a look at this as a way to see the code before i try and make any larger contributions. I'll work my way though the code from time-to-time. However, it would be helpful if the hudson build output could be fixed. It looks to me like make is running several jobs in parallel (using -j perhaps), and this is making the output very hard to follow.

Would it be possible, for this build only, to fix the output?

I've added a separate job at http://hudson.drizzle.org/job/drizzle-thomi-warnings that does not specify the -j option.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.