I've written about it before, here's the patch. It changes AC_PROG_CC_STDC
to try the `-std' flag rather than `-std1' (for OSF or Ultrix) because the
latter is kind of like 'gcc -ansi' (i.e., terminally strict).
Treat with caution, I don't actually have one of those, but that's what
we're using i
Peter Eisentraut writes:
> I've written about it before, here's the patch. It changes AC_PROG_CC_STDC
> to try the `-std' flag rather than `-std1' (for OSF or Ultrix) because the
> latter is kind of like 'gcc -ansi' (i.e., terminally strict).
I've been wondering about this for a while. And I co
>
> Peter Eisentraut writes:
> > I've written about it before, here's the patch. It changes AC_PROG_CC_STDC
> > to try the `-std' flag rather than `-std1' (for OSF or Ultrix) because the
> > latter is kind of like 'gcc -ansi' (i.e., terminally strict).
>
> I've been wondering about this f
On Apr 19, 2000, Peter Eisentraut <[EMAIL PROTECTED]> wrote:
> I've written about it before, here's the patch. It changes AC_PROG_CC_STDC
> to try the `-std' flag rather than `-std1' (for OSF or Ultrix) because the
> latter is kind of like 'gcc -ansi' (i.e., terminally strict).
Sounds good, but
If AC_FUNC_MKTIME is the only test that might use LIBOBJS, you lose
with a working mktime because LIBOBJS doesn't get substituted.
2000-04-19 Dave Love <[EMAIL PROTECTED]>
* acspecific.m4 (AC_FUNC_MKTIME): Use AC_SUBST.
Index: acspecific.m4
