Autobuilders should test debug builds

[Olly Betts]

We ought to ensure we've at least one autobuilder which uses a non-GNU make and a shell which isn't just bash pretending to be sh. That should help to catch any new unportable bits which slip in. Both Solaris and FreeBSD should allow this, but we need to be careful which tools we're picking up.

Also ought to have VPATH and non-VPATH builds, debug builds, and a build with the muscat36 backend enabled.

[Olly Betts]

Leave this until we've switched to buildbot (or investigated and decided not to)

[Olly Betts]

Ubuntu's /bin/sh is now dash (fairly pure POSIX shell) rather than bash from edgy onwards, so sh portability is taken care of on my dev box! Several of the HP testdrive hosts have non-GNU make, so that's covered.

And the Muscat 3.6 backend has now gone.

That leaves:

• Non-VPATH build (the tinderbox always builds VPATH currently).

• Debug builds.

[Richard Boulton]

We now have a buildbot, which runs non-VPATH builds by default, but also performs a make distcheck (which does a VPATH build). It also runs one of the builds on an Ubuntu box, so this covers using a non-bash shell.

I'll add a debug build to the configuration.

[Olly Betts]

One with --enable-assertions and one with --enable-log would be useful. Or perhaps just one with both?

Reassigning to you...

[Richard Boulton]

I'll set up a reasonably frequent build with both --enable-log and --enable-assertions, and 2 infrequent builds (ie, with a long tree-stable time), one for each of the options; we might as well cover all the options, since it doesn't cost much.

[Richard Boulton]

This is implemented (in the buildbot).