Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: "Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)at>
Cc: "Alexandra Roy *EXTERN*" <Alexandra(dot)Roy(at)bull(dot)net>, "pgsql general" <pgsql-general(at)postgresql(dot)org>, pgsql-hackers(at)postgresql(dot)org
Subject: Re: [HACKERS] PostgreSQL 8.3.8 on AIX5.3 : compilation failed
Date: 2009-11-10 16:36:03
Message-ID: 560.1257870963@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general pgsql-hackers

"Albe Laurenz" <laurenz(dot)albe(at)wien(dot)gv(dot)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

In response to

Responses

Browse pgsql-general by date

  From Date Subject
Next Message Antonio Ruggiero 2009-11-10 17:02:13 Re: -c argument not recognized
Previous Message Scott Mead 2009-11-10 16:24:45 Re: Incremental Backups in postgres

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2009-11-10 16:54:44 Re: Tightening binary receive functions
Previous Message Tom Lane 2009-11-10 16:19:45 Re: Query::targetList and RETURNING