bug in 3.2 configure

[Zachary Loafman]

> -----Original Message-----
> From: Andrew Bartlett
> Sent: Thursday, July 10, 2008 12:45 AM
> 
> On Thu, 2008-07-03 at 03:43 +0200, Timur I. Bakeyev wrote:
> > On Wed, Jul 2, 2008 at 7:27 PM, Jeremy Allison <jra at samba.org>
wrote:
> > > On Tue, Jul 01, 2008 at 06:47:08PM -0700, Herb Lewis wrote:
> > >> It is supposed to be MAXPATH size.
> > >>
> > >> Reading configure a little closer, it looks like we are testing
if
> > >> realpath allows a NULL argument.
> > >>
> > >> Still seems like a bad test if it causes a core dump. Why do we
care
> > >> if we can use a NULL?
> > >
> > > This is very useful, and we have a code path to use it.
> >
> > Personally, I see no problem with core dumps in the configure tests,
> > as soon as they don't collapes the whole box :)
> 
> We have avoided them in the past, when a non-coredump test would
> indicate the same result, but adding a signal handler to a configure
> test would seem overkill...

I'll probably patch it later today and submit something. Core files on
our system end up in /var/crash (rather than the execution directory),
and people get tetchy when random cores appear.

...Zach