Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed - Mailing list pgsql-general

From Tom Lane
Subject Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Date
Msg-id 560.1257870963@sss.pgh.pa.us
Whole thread Raw
In response to Re: PostgreSQL 8.3.8 on AIX5.3 : compilation failed  ("Albe Laurenz" <laurenz.albe@wien.gv.at>)
Responses Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
List pgsql-general
"Albe Laurenz" <laurenz.albe@wien.gv.at> writes:
>> Why the "OBJECT_MODE" exported to 32 is not sufficient ?

> I dug around a little, and the problem is in psqlscan.c which is generated
> from psqlscan.l by flex.
> The problem is that both _LARGE_FILES and _LARGE_FILE_API are #defined
> in this case, which makes #include <unistd.h> fail.

Yeah.  We solved this and other problems years ago by decreeing that
we would never try to compile flex output files on their own; they'd
always be #include'd into some other source file so that pg_config.h
would get read first.  psqlscan.l seems to have escaped that dictum
somehow, but I guess we'd better make it fall into line.

In most of the other cases the #include is done in an associated .y
file, but there is none in psql.  Anyone have a thought which of
psql's .c files would be the most appropriate host?

            regards, tom lane

pgsql-general by date:

Previous
From: Alexandra Roy
Date:
Subject: Re: PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Next
From: Magnus Hagander
Date:
Subject: Re: Problem to use remote cygwin server using ssh and native psql 8.3.5