| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "REIX, Tony" <tony(dot)reix(at)atos(dot)net> |
| Cc: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, "APEKE, SENA (ext)" <sena(dot)apeke(dot)external(at)atos(dot)net>, Peter Eisentraut <peter_e(at)gmx(dot)net>, "Anthony Bykov" <a(dot)bykov(at)postgrespro(dot)ru>, Noah Misch <noah(at)leadboat(dot)com> |
| Subject: | Re: PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode |
| Date: | 2018-05-31 14:28:12 |
| Message-ID: | 4046.1527776892@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
"REIX, Tony" <tony(dot)reix(at)atos(dot)net> writes:
> It looks like configure does figure out that LARGE_FILES is required, only in 32bit.
> No need in 64bit.
Check ...
> However, in 32bit, though there is:
> #define _LARGE_FILES 1
> in file :
> src/include/pg_config.h
> I had to add it at the beg of file by means of a patch to several files:
This is surely not what's intended. It seems like plpython is messing
things up somehow, probably through an #include-ordering error, but
I don't see the exact problem offhand.
I wondered why the existing 32-bit AIX buildfarm machines aren't showing
problems, but looking closer at them, they are manually forcing
_LARGE_FILES, which probably is masking things:
'config_env' => {
'CC' => 'wrap-gcc -D_THREAD_SAFE=1 -D_LARGE_FILES=1 -maix32',
Noah, why'd you do that, and would you be willing to remove it? IMO
Postgres should work without that.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Ashutosh Bapat | 2018-05-31 15:34:25 | Re: Problem while updating a foreign table pointing to a partitioned table on foreign server |
| Previous Message | REIX, Tony | 2018-05-31 14:13:10 | RE:PostgreSQL 11 beta1 on AIX 7.2 : 2 failures in 32bit mode |