flexfax: Re: HylaFAX 4.0pl2: most platforms don't have REG_STARTEND

["Jonathan I. Kamens" <jik@kamens.brookline.ma.us>]

I did a bit more debugging, and the patch I sent to fix this problem
doesn't really address the root problem.

I discovered that HylaFAX includes its own regexec implementation
which supports REG_STARTEND.  I was running into trouble because I had
TIFFINC set to /usr/include, since that's where my TIFF include files
are located.  As a result, object files were being built with
"-I/usr/include" before "-I${DEPTH}/regex", so the compiler was seeing
/usr/include/regex.h before the regex.h included with HylaFAX.  In
addition to causing the REG_STARTEND problem I previously reported, it
also prevented the compiled programs from working, because the
structures defined in /usr/include/regex.h didn't match the structured
expected by the regex routines included with HylaFAX.

The rather gross workaround I came up with was to put back the
original setting of TIFFINC to /usr/local/include.  That directory is
empty on my machine, which makes "-I/usr/local/include" a no-op, so
the correct regex.h will now be found.

A better fix would be allow the user to specify at configuration time
that certain header files are in the standard compiler include path,
i.e., no "-I" flag is needed for any of them.  There's no way to do
this now, because setting TIFFINC to an empty string causes an empty
"-I" flag to be included on the compiler command line.

  jik