Re: AW: AW: AW: Re: tinterval - operator problems on AIX

From: Peter Eisentraut <peter_e(at)gmx(dot)net>
To: Ian Lance Taylor <ian(at)airs(dot)com>
Cc: Thomas Lockhart <lockhart(at)alumni(dot)caltech(dot)edu>, Pete Forman <pete(dot)forman(at)westerngeco(dot)com>, Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at>, <lockhart(at)fourpalms(dot)org>, "'pgsql-hackers(at)postgresql(dot)org'" <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: AW: AW: AW: Re: tinterval - operator problems on AIX
Date: 2001-01-19 23:24:15
Message-ID: Pine.LNX.4.30.0101200000150.1322-100000@peter.localdomain
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

Ian Lance Taylor writes:

> An approach I've followed in the past is to use three-way logic. If
> configuring for a native system, compile and run a program which
> provides a yes or no answer. When using cross-configuration, set the
> configuration variable to ``don't know'' (or, since this a database
> group, NULL).

This would seem to be the right answer, but unfortunately Autoconf is not
smart enough to detect marginal cross-compilation cases in all situations.
Someone had zlib installed in a location where gcc would find it (compiles
okay) but the run-time linker would not (does not run). This is not
detected when AC_PROG_CC runs, but only later on after you have checked
for the libraries.

--
Peter Eisentraut peter_e(at)gmx(dot)net http://yi.org/peter-e/

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Tom Lane 2001-01-20 00:53:32 Re: "initdb -t" destroys all databases
Previous Message Tom Lane 2001-01-19 23:00:56 Re: A couple of fishy-looking critical sections