Thread: 7.2 compile problem on HP/UX

7.2 compile problem on HP/UX

From
Richard Ray
Date:
I'm trying to build 7.2 on HP/UX 10.20. I get a lot of warnings but this is a
killer.

gmake[4]: Entering directory
`/pgsql/postgresql-7.2/src/interfaces/ecpg/preproc'
cc -Ae +O2 -I./../include -I. -I../../../../src/include
-I/opt/readline/include -DMAJOR_VERSION=2 -DMINOR_VERSION=9 -DPATCHLEVEL=0
-DINCLUDE_PATH=\"/pgsql/include\"   -c -o preproc.o preproc.c
cc: error 7201: new_slc_block: out of memory. (7201)
gmake[4]: *** [preproc.o] Error 1
gmake[4]: Leaving directory
`/pgsql/postgresql-7.2/src/interfaces/ecpg/preproc'
gmake[3]: *** [all] Error 2
gmake[3]: Leaving directory `/pgsql/postgresql-7.2/src/interfaces/ecpg'
gmake[2]: *** [all] Error 2
gmake[2]: Leaving directory `/pgsql/postgresql-7.2/src/interfaces'
gmake[1]: *** [all] Error 2
gmake[1]: Leaving directory `/pgsql/postgresql-7.2/src'
gmake: *** [all] Error 2
*** Error exit code 2

Stop.


If I change to +O0 all is well. Is this the proper solution? This is my
configure string.

./configure --prefix=/pgsql --enable-odbc --enable-syslog
--with-maxbackends=128 --with-libraries=/opt/readline/lib
--with-includes=/opt/readline/include --enable-locale
--enable-multibyte

Richard Ray

Re: 7.2 compile problem on HP/UX

From
Tom Lane
Date:
Richard Ray <rray1@netdoor.com> writes:
> I'm trying to build 7.2 on HP/UX 10.20. I get a lot of warnings but this is a
> killer.

> gmake[4]: Entering directory
> `/pgsql/postgresql-7.2/src/interfaces/ecpg/preproc'
> cc -Ae +O2 -I./../include -I. -I../../../../src/include
> -I/opt/readline/include -DMAJOR_VERSION=2 -DMINOR_VERSION=9 -DPATCHLEVEL=0
> -DINCLUDE_PATH=\"/pgsql/include\"   -c -o preproc.o preproc.c
> cc: error 7201: new_slc_block: out of memory. (7201)
> gmake[4]: *** [preproc.o] Error 1

(a) Update to latest compiler version.  If problem still there,
    file a compiler bug report with HP.  (FWIW, I see no such problem
    on HPUX 10.20, using a circa-1999 compiler release.)

(b) Increasing swap space might help; not sure.

(c) Use gcc...

            regards, tom lane