Re: testing for usable C compiler

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: pgsql-hackers(at)postgreSQL(dot)org
Subject: Re: testing for usable C compiler
Date: 2003-09-03 19:37:46
Message-ID: Pine.LNX.4.44.0309032126590.1035-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Tom Lane writes:

> Yeah. I would suggest doing it at the "check that C compiler still
> works" stage, after we think we have all the CFLAGS. Couldn't we just
> throw a prototyped function into that test program?

The standard Autoconf prototype test is pretty involved (see
AC_PROG_CC_STDC in /usr/local/share/autoconf/autoconf/c.m4 or whatever).
Maybe you can come up with a smaller test for now that fails on the
lame-excuse compiler on HP-UX? If you don't want to merge it in yourself,
feel free to just send me a .c file that fails to compile and I'll
integrate it.

But: What's the error message going to be? Is "compiler does not accept
prototypes" going to be clearer for the user than what he gets now?
(What does he get now anyway? Does it fail to compile something down the
road?)

--
Peter Eisentraut peter_e(at)gmx(dot)net

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Sean Chittenden 2003-09-03 19:44:53 Re: Win32 native port
Previous Message Bruce Momjian 2003-09-03 19:36:53 Re: Unixware Patch (Was: Re: Beta2 Tag'd and Bundled ...)