| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Taral" <taral(at)mail(dot)utexas(dot)edu> |
| Cc: | "The Hermit Hacker" <scrappy(at)hub(dot)org>, "PostgreSQL hackers mailing list" <pgsql-hackers(at)postgreSQL(dot)org> |
| Subject: | Re: [HACKERS] 6.4 BETA2 fails to compile on Digital Unix 4.0d |
| Date: | 1998-10-29 18:23:29 |
| Message-ID: | 6556.909685409@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"Taral" <taral(at)mail(dot)utexas(dot)edu> writes:
> *** acspecific.m4.orig Thu Oct 29 12:43:02 1998
> --- acspecific.m4 Thu Oct 29 12:49:39 1998
I have just committed a configure.in fix that eliminates the need for
this change. It turns out that the shell syntax failure was just the
tip of the iceberg: the real problem is that AC_PROG_CC *must* be run
even if there is a user-supplied CC setting.
> There really needs to be a sanity check for --with-cc or whatever it is.
There is: AC_PROG_CC makes sure that the supplied CC setting works,
and incidentally discovers a few other things like whether it is gcc.
Our problem was we were bypassing that macro if --with-CC was given.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-10-29 18:25:58 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/include/catalog pg_operator.h' |
| Previous Message | Thomas G. Lockhart | 1998-10-29 18:23:00 | Re: [HACKERS] Re: [COMMITTERS] 'pgsql/src/include/catalog pg_operator.h' |