head	1.17;
access;
symbols
	REL7_4_29:1.12
	REL8_0_25:1.13
	REL8_1_21:1.13.6.2
	REL8_2_17:1.14.2.10
	REL8_3_11:1.16
	REL7_4_28:1.12
	REL8_0_24:1.13
	REL8_1_20:1.13.6.2
	REL8_2_16:1.14.2.10
	REL8_3_10:1.16
	REL7_4_27:1.12
	REL8_0_23:1.13
	REL8_1_19:1.13.6.2
	REL8_2_15:1.14.2.10
	REL8_3_9:1.16
	REL7_4_26:1.12
	REL8_0_22:1.13
	REL8_1_18:1.13.6.2
	REL8_2_14:1.14.2.10
	REL8_3_8:1.16
	REL7_4_25:1.12
	REL8_0_21:1.13
	REL8_1_17:1.13.6.2
	REL8_2_13:1.14.2.10
	REL8_3_7:1.16
	REL7_4_24:1.12
	REL8_0_20:1.13
	REL8_1_16:1.13.6.2
	REL8_2_12:1.14.2.10
	REL8_3_6:1.16
	REL7_4_23:1.12
	REL8_0_19:1.13
	REL8_1_15:1.13.6.2
	REL8_2_11:1.14.2.10
	REL8_3_5:1.16
	REL7_4_22:1.12
	REL8_0_18:1.13
	REL8_1_14:1.13.6.2
	REL8_2_10:1.14.2.10
	REL8_3_4:1.16
	REL7_4_21:1.12
	REL8_0_17:1.13
	REL8_1_13:1.13.6.2
	REL8_2_9:1.14.2.10
	REL8_3_3:1.16
	REL7_4_20:1.12
	REL8_0_16:1.13
	REL8_1_12:1.13.6.2
	REL8_2_8:1.14.2.10
	REL8_3_2:1.16
	REL8_2_7:1.14.2.10
	REL8_3_1:1.16
	REL8_3_STABLE:1.16.0.2
	REL8_3_0:1.16
	REL8_3_RC2:1.16
	REL7_3_21:1.11.2.5
	REL7_4_19:1.12
	REL8_0_15:1.13
	REL8_1_11:1.13.6.2
	REL8_2_6:1.14.2.10
	REL8_3_RC1:1.16
	REL8_3_BETA4:1.16
	REL8_3_BETA3:1.16
	REL8_3_BETA2:1.16
	REL8_3_BETA1:1.16
	REL7_3_20:1.11.2.5
	REL7_4_18:1.12
	REL8_0_14:1.13
	REL8_1_10:1.13.6.2
	REL8_2_5:1.14.2.10
	REL7_3_19:1.11.2.5
	REL7_4_17:1.12
	REL8_0_13:1.13
	REL8_1_9:1.13.6.2
	REL8_2_4:1.14.2.7
	REL8_0_12:1.13
	REL8_1_8:1.13.6.2
	REL8_2_3:1.14.2.6
	REL7_3_18:1.11.2.5
	REL7_4_16:1.12
	REL8_0_11:1.13
	REL8_1_7:1.13.6.2
	REL8_2_2:1.14.2.4
	REL8_0_10:1.13
	REL8_1_6:1.13.6.2
	REL8_2_1:1.14.2.3
	REL7_4_15:1.12
	REL7_3_17:1.11.2.5
	REL8_2_STABLE:1.14.0.2
	REL8_2_0:1.14
	REL8_2_RC1:1.14
	REL8_2_BETA3:1.14
	REL8_2_BETA2:1.14
	REL8_1_5:1.13.6.2
	REL8_0_9:1.13
	REL7_4_14:1.12
	REL7_3_16:1.11.2.5
	REL8_2_BETA1:1.14
	REL7_3_15:1.11.2.5
	REL7_4_13:1.12
	REL8_0_8:1.13
	REL8_1_4:1.13
	REL7_3_14:1.11.2.5
	REL7_4_12:1.12
	REL8_0_7:1.13
	REL8_1_3:1.13
	REL7_3_13:1.11.2.5
	REL7_4_11:1.12
	REL8_0_6:1.13
	REL8_1_2:1.13
	REL7_3_12:1.11.2.5
	REL7_4_10:1.12
	REL8_0_5:1.13
	REL8_1_1:1.13
	REL8_1_STABLE:1.13.0.6
	REL8_1_0:1.13
	REL8_1_0RC1:1.13
	REL8_1_0BETA4:1.13
	REL8_1_0BETA3:1.13
	REL7_3_11:1.11.2.5
	REL7_4_9:1.12
	REL8_0_4:1.13
	REL8_1_0BETA2:1.13
	REL8_1_0BETA1:1.13
	REL7_2_8:1.9
	REL7_3_10:1.11.2.5
	REL7_4_8:1.12
	REL8_0_3:1.13
	REL8_0_2:1.13
	REL7_2_7:1.9
	REL7_3_9:1.11.2.5
	REL7_4_7:1.12
	REL8_0_1:1.13
	REL8_0_STABLE:1.13.0.4
	REL8_0_0:1.13.0.2
	REL8_0_0RC5:1.13
	REL8_0_0RC4:1.13
	REL8_0_0RC3:1.13
	REL8_0_0RC2:1.13
	REL8_0_0RC1:1.13
	REL8_0_0BETA5:1.13
	REL8_0_0BETA4:1.13
	REL7_4_6:1.12
	REL7_3_8:1.11.2.5
	REL7_2_6:1.9
	REL8_0_0BETA3:1.13
	REL8_0_0BETA2:1.12
	REL7_2_5:1.9
	REL7_4_5:1.12
	REL7_3_7:1.11.2.5
	REL7_4_4:1.12
	REL8_0_0BETA1:1.12
	REL7_4_3:1.12
	REL7_4_2:1.12
	REL7_3_6:1.11.2.5
	REL7_4_1:1.12
	REL7_3_5:1.11.2.5
	REL7_4:1.12
	REL7_4_RC2:1.12
	REL7_4_STABLE:1.12.0.4
	REL7_4_RC1:1.12
	REL7_4_BETA5:1.12
	REL7_4_BETA4:1.12
	REL7_4_BETA3:1.12
	REL7_4_BETA2:1.12
	WIN32_DEV:1.12.0.2
	REL7_4_BETA1:1.12
	REL7_3_4:1.11.2.5
	REL7_3_2:1.11.2.3
	REL7_2_4:1.9
	REL7_3_STABLE:1.11.0.2
	REL7_2_3:1.9
	REL7_2_STABLE:1.9.0.4
	REL7_2:1.9
	REL7_2_RC2:1.9
	REL7_2_RC1:1.9
	REL7_2_BETA5:1.9
	REL7_2_BETA4:1.9
	REL7_2_BETA3:1.9
	REL7_2_BETA2:1.9
	REL7_2_BETA1:1.9
	REL7_1_2:1.9
	REL7_1_STABLE:1.9.0.2
	REL7_1_BETA:1.5
	REL7_1_BETA3:1.5
	REL7_1_BETA2:1.5
	REL7_1:1.8
	REL7_0_PATCHES:1.3.0.4
	REL7_0:1.3
	REL6_5_PATCHES:1.3.0.2
	REL6_5:1.3
	REL6_4:1.1.0.2;
locks; strict;
comment	@# @;


1.17
date	2008.11.21.16.46.19;	author petere;	state dead;
branches;
next	1.16;

1.16
date	2006.12.06.15.45.30;	author momjian;	state Exp;
branches;
next	1.15;

1.15
date	2006.12.05.14.47.34;	author momjian;	state Exp;
branches;
next	1.14;

1.14
date	2006.07.19.02.37.00;	author tgl;	state Exp;
branches
	1.14.2.1;
next	1.13;

1.13
date	2004.09.02.17.46.24;	author tgl;	state Exp;
branches
	1.13.6.1;
next	1.12;

1.12
date	2002.11.11.20.04.05;	author petere;	state Exp;
branches;
next	1.11;

1.11
date	2002.11.02.00.46.23;	author tgl;	state Exp;
branches
	1.11.2.1;
next	1.10;

1.10
date	2002.10.22.13.46.59;	author tgl;	state Exp;
branches;
next	1.9;

1.9
date	2001.04.30.23.55.26;	author tgl;	state Exp;
branches;
next	1.8;

1.8
date	2001.03.20.00.18.21;	author tgl;	state Exp;
branches;
next	1.7;

1.7
date	2001.02.20.19.06.16;	author tgl;	state Exp;
branches;
next	1.6;

1.6
date	2001.02.20.01.33.07;	author momjian;	state Exp;
branches;
next	1.5;

1.5
date	2000.08.26.19.34.24;	author petere;	state Exp;
branches;
next	1.4;

1.4
date	2000.07.07.15.41.41;	author momjian;	state Exp;
branches;
next	1.3;

1.3
date	99.06.05.18.24.55;	author momjian;	state Exp;
branches;
next	1.2;

1.2
date	99.06.05.03.43.05;	author momjian;	state Exp;
branches;
next	1.1;

1.1
date	98.11.28.23.10.22;	author tgl;	state Exp;
branches
	1.1.2.1;
next	;

1.1.2.1
date	98.12.18.05.25.57;	author momjian;	state Exp;
branches;
next	;

1.11.2.1
date	2002.11.11.19.59.56;	author petere;	state Exp;
branches;
next	1.11.2.2;

1.11.2.2
date	2002.11.16.02.34.22;	author momjian;	state Exp;
branches;
next	1.11.2.3;

1.11.2.3
date	2002.12.18.20.39.31;	author momjian;	state Exp;
branches;
next	1.11.2.4;

1.11.2.4
date	2003.02.14.14.05.51;	author momjian;	state Exp;
branches;
next	1.11.2.5;

1.11.2.5
date	2003.07.23.04.13.11;	author momjian;	state Exp;
branches;
next	;

1.13.6.1
date	2006.10.10.00.29.14;	author momjian;	state Exp;
branches;
next	1.13.6.2;

1.13.6.2
date	2006.10.10.20.11.44;	author momjian;	state Exp;
branches;
next	;

1.14.2.1
date	2006.12.11.22.48.07;	author momjian;	state Exp;
branches;
next	1.14.2.2;

1.14.2.2
date	2007.01.05.20.55.28;	author momjian;	state Exp;
branches;
next	1.14.2.3;

1.14.2.3
date	2007.01.05.20.57.17;	author momjian;	state Exp;
branches;
next	1.14.2.4;

1.14.2.4
date	2007.02.01.04.56.41;	author momjian;	state Exp;
branches;
next	1.14.2.5;

1.14.2.5
date	2007.02.06.18.38.04;	author momjian;	state Exp;
branches;
next	1.14.2.6;

1.14.2.6
date	2007.02.07.03.16.59;	author momjian;	state Exp;
branches;
next	1.14.2.7;

1.14.2.7
date	2007.04.19.03.07.22;	author momjian;	state Exp;
branches;
next	1.14.2.8;

1.14.2.8
date	2007.09.11.17.37.29;	author momjian;	state Exp;
branches;
next	1.14.2.9;

1.14.2.9
date	2007.09.12.03.11.49;	author momjian;	state Exp;
branches;
next	1.14.2.10;

1.14.2.10
date	2007.09.13.03.34.23;	author momjian;	state Exp;
branches;
next	;


desc
@@


1.17
log
@Include the platform "FAQs" into the installation instructions.
I weeded out some really old information along the way.
FAQ_AIX needs separate consideration and will be dealt with later.
@
text
@=======================================================
Frequently Asked Questions (FAQ) for PostgreSQL
HP-UX Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
last updated:           $Date: 2006/12/06 15:45:30 $

current maintainer:     Tom Lane (tgl@@sss.pgh.pa.us)
original author:        Tom Lane (tgl@@sss.pgh.pa.us)


Questions covered here:
1.1)	What do I need to install PostgreSQL on HP-UX?
1.2)	Anything special about the build/install procedure?
1.3)	OK, it seemed to build and install, but the regression test fails.


----------------------------------------------------------------------
Section 1:      Installing PostgreSQL
----------------------------------------------------------------------

1.1)	What do I need to install PostgreSQL on HP-UX?

PostgreSQL 7.3+ should work on Series 700/800 PA-RISC machines running
HP-UX 10.X or 11.X, given appropriate system patch levels and build
tools.  At least one developer routinely tests on HPUX 10.20 and we
have reports of successful installations on HPUX 11.00 and 11.11.

Aside from the PostgreSQL source distribution, you will need GNU make
(HP's make will not do), and either GNU gcc or HP's full ANSI C compiler.
If you intend to build from CVS sources rather than a distribution tarball,
you will also need flex (GNU lex) and bison (GNU yacc).

I'd also recommend making sure you are fairly up-to-date on HP
patches.  At a minimum, if you are building 64 bit binaries on on HPUX
11.11 you may need PHSS_30966 (11.11) or a successor patch otherwise
initdb may hang:

    PHSS_30966  s700_800 ld(1) and linker tools cumulative patch

On general principles you should be current on libc and ld/dld
patches, as well as compiler patches if you are using HP's C compiler.
See HP's support sites such as http://itrc.hp.com and
ftp://us-ffs.external.hp.com/ for free copies of their latest patches.

If you are building on a PA-RISC 2.0 machine and want to have 64-bit
binaries using GCC, you must use GCC 64-bit version. GCC binaries for
HP-UX PA-RISC and Itanium are available from http://www.hp.com/go/gcc.
Don't forget to get and install binutils at the same time.

If you are building on a HP-UX Itanium machine, you will need the
latest HP ANSI C compiler with its dependent patch or successor
patches:

    PHSS_30848  s700_800 HP C Compiler (A.05.57)
    PHSS_30849  s700_800 u2comp/be/plugin library Patch

1.2)	Anything special about the build/install procedure?

If you have both HP's C compiler and GCC's, then you might want to
explicitly select the compiler to use when you run `configure':
	./configure CC=cc
for HP's C compiler, or
	./configure CC=gcc
for GCC.  If you omit this setting, then configure will pick gcc
if it has a choice.

The default install target location is /usr/local/pgsql, which
you might want to change to something under /opt.  If so, use
the --prefix switch to configure.

If you are building on a PA-RISC 2.0 machine and want the compiled
binaries to run on PA-RISC 1.1 machines you will need to specify
+DAportable in CFLAGS.


1.3)	OK, it seemed to build and install, but the regression test fails.

There are several "expected failures" due to differences between HPUX
and the regression test reference platform used by the PostgreSQL
group.  All of these should be compensated for by the regression test
comparison mechanism, with the possible exception of some
low-order-digit differences in the geometry tests, which vary depending
on which compiler and math library versions you use.

Any other error is cause for suspicion.
@


1.16
log
@Back out mention of port success from FAQs, per Tom, added by Simon.
@
text
@d6 1
a6 1
last updated:           $Date: 2006/12/05 14:47:34 $
@


1.15
log
@Update of port patches, HEAD patch only.

Simon Riggs
@
text
@d6 1
a6 1
last updated:           $Date: 2006/07/19 02:37:00 $
a28 5
Recent port reports for PostgreSQL 8.2.0 are
  - on IA64,    HP-UX 11.23,           gcc and cc
  - on PA-RISC, HP-UX 10.20 and 11.23, gcc and cc
Tested on 2006-10-23

@


1.14
log
@Rewrite pg_regress as a C program instead of a shell script.
This allows it to be used on Windows without installing mingw
(though you do still need 'diff'), and opens the door to future
improvements such as message localization.
Magnus Hagander and Tom Lane.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL 7.3
d6 1
a6 1
last updated:           $Date: 2004/09/02 17:46:24 $
d24 1
a24 1
PostgreSQL 7.3 should work on Series 700/800 PA-RISC machines running
d29 5
@


1.14.2.1
log
@Backpatch FAQ entry for null concatenation.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL
d6 1
a6 1
last updated:           $Date: 2006/12/06 15:45:30 $
d24 1
a24 1
PostgreSQL 7.3+ should work on Series 700/800 PA-RISC machines running
@


1.14.2.2
log
@Stamp release 8.2.1.  Update FAQs.
@
text
@@


1.14.2.3
log
@Update Japanese FAQ.
@
text
@@


1.14.2.4
log
@Backpatch FAQs to stable branch.
@
text
@@


1.14.2.5
log
@Backpatch FAQs to 8.2.X branch.
@
text
@@


1.14.2.6
log
@Update FAQ for 8.2.3.
@
text
@@


1.14.2.7
log
@Stamp releases 8.2.4, 8.1.9, 8.0.13, 7.4.17, 7.3.19.
@
text
@@


1.14.2.8
log
@Stamp releases 8.2.5, 8.1.10, 8.0.14, 7.4.18, 7.3.20.

Update FAQs for 8.2.5.
@
text
@@


1.14.2.9
log
@Update Japanese FAQ to current release number.
@
text
@@


1.14.2.10
log
@Update Japanese FAQ, backpatch.

Jun Kuwamura
@
text
@@


1.13
log
@FAQ_HPUX updates from Shinji Teragaito.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/11 20:04:05 $
a86 16

The parallel regression test script (gmake check) is known to lock up
on PA-RISC when run under HP's Bourne shells: /usr/bin/sh and
/sbin/sh. To fix this problem, you will need PHCO_30269 with its
dependent patch or successor patches:

    PHCO_30269  s700_800 cumulative sh-posix(1) patch
    PHCO_29816  s700_800 rc(1M) scripts cumulative patch 

To work around this problem, use ksh to run the regression script:

	gmake SHELL=/bin/ksh check

If you see that the tests have stopped making progress and only a shell
process is consuming CPU, kill the shell process and start over with the
above command.
@


1.13.6.1
log
@Backpatch FAQs to 8.1.X.
@
text
@d6 1
a6 1
last updated:           $Date: 2006/07/19 02:37:00 $
d87 16
@


1.13.6.2
log
@Restore HPUX FAQ entry that talked about working around regression
script problems, because in 8.1.X, the regression test is still a
script.  Patch to 8.1.X only.
@
text
@d6 1
a6 1
last updated:           $Date: 2006/10/10 00:29:14 $
a86 16

The parallel regression test script (gmake check) is known to lock up
on PA-RISC when run under HP's Bourne shells: /usr/bin/sh and
/sbin/sh. To fix this problem, you will need PHCO_30269 with its
dependent patch or successor patches:

    PHCO_30269  s700_800 cumulative sh-posix(1) patch
    PHCO_29816  s700_800 rc(1M) scripts cumulative patch 

To work around this problem, use ksh to run the regression script:

	gmake SHELL=/bin/ksh check

If you see that the tests have stopped making progress and only a shell
process is consuming CPU, kill the shell process and start over with the
above command.
@


1.12
log
@Revise platform FAQs.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/02 00:46:23 $
d36 1
a36 1
11.11 you may need PHSS_26263 (11.11) or a successor patch otherwise
d39 1
a39 1
    PHSS_26263  s700_800 11.11 ld(1) and linker tools cumulative patch
d46 11
d89 9
a97 4
when run under HP's Bourne shells: /usr/bin/sh and /sbin/sh.  This is a
known defect JAGad84609, the fix for which is not yet in any released
HP-UX version or shell patches.  To work around it, use ksh to run the
regression script:
@


1.11
log
@Updates from Giles Lean.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/10/22 13:46:59 $
d51 1
a51 1
	CC=cc ./configure
d53 1
a53 1
	CC=gcc ./configure
@


1.11.2.1
log
@Revise platform FAQs.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/02 00:46:23 $
d51 1
a51 1
	./configure CC=cc
d53 1
a53 1
	./configure CC=gcc
@


1.11.2.2
log
@Update TODO/FAQ for 7.3 release.
@
text
@d6 1
a6 1
last updated:           $Date: 2002/11/11 20:04:05 $
@


1.11.2.3
log
@Update Russian FAQ.  Update all FAQ's for 7.3.X branch.
@
text
@@


1.11.2.4
log
@Update FAQ's in head and 7.3.X.
@
text
@@


1.11.2.5
log
@Update all FAQ's for 7.3.4.
@
text
@@


1.10
log
@Specify that we need bison >= 1.50.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL 7.1
d6 1
a6 1
last updated:           $Date: 2001/04/30 23:55:26 $
d15 1
a15 4
1.3)	yacc dies trying to process src/backend/parser/gram.y.
1.4)	Linking the main postgres executable fails, complaining that
	there's no "alloca" function. 
1.5)	OK, it seemed to build and install, but the regression test fails.
d24 4
a27 6
PostgreSQL 7.1 should work on Series 700/800 machines running HPUX 9.*,
10.*, or 11.*, given appropriate system patch levels and build tools.
At least one developer routinely tests on HPUX 10.20, and we have reports
of successful install on HPUX 11.  Releases before 7.1 were tested on
HPUX 9.03 and 9.05; 7.1 should still work there although no recent tests
have been reported.
d34 11
a44 12
I'd also recommend making sure you are fairly up-to-date on HP patches,
particularly if you are using HPUX 9.  At a minimum, if you are on HPUX 9,
you *must* have PHSS_4630 (libm update) or a successor patch; otherwise
Postgres' date/time functions will misbehave.  On general principles you
should be current on libc and ld/dld patches, as well as compiler patches
if you are using HP's C compiler.  (The only other presently known failure
from out-of-date system libraries is that on HPUX 10.10, the backend will
crash after the second error message in a session unless you have upgraded
libc to PHCO_16722 or later.)

See HP's support websites, such as http://us-support.external.hp.com/,
for free copies of their latest patches.
d61 3
a64 1
1.3)	yacc dies trying to process src/backend/parser/gram.y.
d66 1
a66 23
HP's yacc doesn't create its tables large enough to handle the Postgres
grammar (a lot of other vendors' yaccs have this problem too).  The
preferred solution is to use GNU bison instead.  If you don't want to
do that for some reason, it's possible to increase yacc's table sizes
enough to cope.  With a pre-6.4 PostgreSQL grammar, I was able to get
HPUX 9's yacc to work by setting YFLAGS to
	-d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
(You can edit YFLAGS either in the template file before running
configure, or in src/Makefile.global afterwards.)  Later PostgreSQL
releases might require even larger tables, but this should do for
a starting point.

Note that this shouldn't affect you if you are using a distribution
tarball, but it does matter if you pull the sources from the CVS server.
The CVS server does not store prebuilt yacc output files.


1.4)	Linking the main postgres executable fails, complaining that
	there's no "alloca" function. 

You're using an old version of GNU bison.  Update to 1.50 or later,
and re-make the bison output files.  Or build with gcc, or update to
HPUX 10, either of which will provide support for alloca.
d68 6
d75 1
a75 12
1.5)	OK, it seemed to build and install, but the regression test fails.

There are several "expected failures" due to differences between HPUX
and the regression test reference platform used by the PostgreSQL group.
All of these should be compensated for by the regression test comparison
mechanism, with the possible exception of some low-order-digit differences
in the geometry tests (depending on which compiler and math library
versions you use).

Any other error is cause for suspicion.  In particular, if you see
failures in the datetime test on HPUX 9, you probably forgot to
install the libm patch PHSS_4630 --- see item 1.1 above.
d78 4
a81 4
when run under HP's default Bourne shell, at least in HPUX 10.20.  This
appears to be a shell bug, not the fault of the script.  If you see that
the tests have stopped making progress and only a shell process is
consuming CPU, kill the shell and start over with
d83 4
a86 1
to use ksh instead.
@


1.9
log
@Update FAQ_HPUX now that we have reports of out-of-the-box build
on HPUX 11.
@
text
@d6 1
a6 1
last updated:           $Date: 2001/03/20 00:18:21 $
d90 1
a90 1
You're using an old version of GNU bison.  Update to 1.28 or later,
@


1.8
log
@Mention that parallel regress script needs to be run under ksh not sh
on HPUX.
@
text
@d6 1
a6 1
last updated:           $Date: 2001/02/20 19:06:16 $
d27 6
a32 6
PostgreSQL 7.1 is known to build and pass regression test on HPUX 10.20,
given appropriate system patch levels and build tools.  It should work on
other HPUX 9.* and 10.* releases for Series 700/800 machines, too (prior
Postgres releases were tested on 9.03 and 9.05).  I have heard nonspecific
reports of problems on HPUX 11; more info and/or patches would be
appreciated!
d60 2
a61 1
for GCC.  If you omit this setting then configure will pick gcc.
d64 2
a65 2
(particularly on HPUX 10) you might want to change to something under
/opt.  If so, use the --prefix switch to configure.
d84 1
@


1.7
log
@Remove obsolete claim that it doesn't work to use gcc with HP's C++
compiler or g++ with HP's C compiler.
@
text
@d6 1
a6 1
last updated:           $Date: 2001/02/20 01:33:07 $
d106 7
@


1.6
log
@Update HPUX FAQ.
@
text
@d6 1
a6 1
last updated:           $Date: 2001/02/19 17:30:01 $
a61 4
Note also that configure will default to no optimization for cc;
you'll probably want to override that, say with
	CC=cc CFLAGS=+O2 ./configure

a64 9

If you want to build the C++ client library (libpq++) then you need
to use a C++ compiler from the same source as the C compiler; mixing
HP and GNU compilers doesn't work. If you have both C++ compilers
in your PATH, keep an eye on whether configure picks the right one.
If it makes the wrong choice, set the environment variable CXX:
	CC=gcc CXX=g++ ./configure --with-CXX
or
	CC=cc CXX=aCC ./configure --with-CXX
@


1.5
log
@Update platform FAQs
@
text
@d6 1
a6 1
last updated:           $Date$
d27 6
a32 5
PostgreSQL 6.5 is known to build and pass regression test on HPUX 9.03,
9.05, and 10.20, given appropriate system patch levels and build tools.
It should work on other HPUX 9.* and 10.* releases for Series 700/800
machines, too.  I have heard nonspecific reports of problems on HPUX 11;
more info and/or patches would be appreciated!
d36 2
a37 2
You must also get flex (GNU lex) 2.5.4 or later --- all versions of
HP's lex fail on the Postgres lexer files.
a51 4
PostgreSQL 6.3.2 and earlier required quite a few small tweaks to
install on HPUX, so I recommend you not bother with anything older
than 6.4.

d62 4
d74 2
a75 2
To override the choice, set the environment variable CXX:
	CC=gcc CXX=g++ ./configure
d77 1
a77 1
	CC=cc CXX=aCC ./configure
d83 5
a87 14
grammar (a lot of other vendors' yaccs have this problem too).  There
are three possible workarounds:

1. The quickest answer is just to "touch" src/backend/parser/gram.c
and src/backend/parser/parse.h and repeat the build.  Any PostgreSQL
distribution file should have up-to-date copies of those files included,
so you shouldn't need to run yacc on gram.y at all ... but sometimes
gram.y mistakenly has a newer timestamp in the distribution than the
derived files do.  (If you fetched the PostgreSQL sources from the CVS
server, then you won't have these files anyway; see next choices.)

2. Increase yacc's table sizes enough to cope.  With a pre-6.4
PostgreSQL grammar, I was able to get HPUX 9's yacc to work by
setting YFLAGS to
d90 1
a90 1
configure, or in src/Makefile.global afterwards.)  Future PostgreSQL
d94 2
a95 3
3. Install "bison" (GNU yacc) and reconfigure.  Bison doesn't have a
problem with large grammars.  Note this is not the right choice if you
are using HP's cc on HPUX 9 --- see next item.
d101 3
a103 16
If you're using HP's cc on HPUX 9, it's right: there's no alloca function.
The only places in PostgreSQL that use alloca are the parser files, and
those do so only if they were generated with GNU bison.  Unfortunately the
prebuilt copies of gram.c and preproc.c are made with bison.  There are
several possible answers:

  1. Remake the files with HP's yacc: configure to use yacc with the
     above-mentioned switch settings, and remove these files before
     starting the build:
          src/backend/parser/gram.c
	  src/interfaces/ecpg/preproc/preproc.c

  2. Build with gcc, which treats alloca as a compiled-in-line function.

  3. Install HPUX 10, which has alloca.  You're gonna have to do that
     before Y2K anyway...
d110 4
a113 27
A look at the textual differences between the expected and actual
outputs will usually reveal that the differences are minor.  You should
expect these differences:

TEST(S)			COMMENTS

int2, int4:		pg_atoi generates a differently worded error
			message for integer overflow.

float8, geometry:	Lots of differences in the last digit or two
			because of different roundoff errors in floating
			arithmetic.  Also, HPUX does not distinguish
			-0 from 0 during printout, but the reference
			platform does.

float8:			In 6.4, float8 shows some differences due to
			different handling of overflow/underflow errors in
			exp() and pow().  This is fixed in 6.4.1 and later.

horology:		HPUX time library does not know about daylight
			savings time before 1970, so there are some
			places in horology where a time will be shown
			in PST instead of PDT.

The int8 regression test will fail massively on HPUX 9 with Postgres 6.4,
because sprintf/sscanf don't cope with long long int.  This is fixed in
Postgres 6.5 by not depending on the system versions of those routines.
d118 1
@


1.4
log
@Remove HTML FAQ files that are really just text files.
@
text
@d2 1
a2 1
Frequently Asked Questions (FAQ) for PostgreSQL  V6.5
d6 1
a6 1
last updated:           Sun May 23 19:48:07 EDT 1999
d58 3
a60 4
When you run configure, you will want to explicitly select either the
hpux_cc or hpux_gcc template depending on which compiler you plan to
use:
	./configure --with-template=hpux_cc
d62 2
a63 10
	./configure --with-template=hpux_gcc
for GNU gcc.  (If you omit --with-template, configure may either
default to hpux_cc or give up entirely, depending on which HPUX and
PostgreSQL releases you have.)

You may want to tweak the CFLAGS setting in template/hpux_[g]cc before
you configure.  The distributed copy of hpux_cc contains neither -O nor -g
switches, which is hardly optimal for any situation.  As of Postgres 6.5,
hpux_gcc sets CFLAGS to -O2, which is fine unless you want to do debugging;
in that case you may want -g as well (or instead).
d69 8
a76 10
If you have both HP and GNU C++ compilers in your PATH, keep an eye on
whether configure picks the right one --- you want the HP c++ if you are
using HP C, or g++ if you are using gcc.  Mixing HP and GNU compilers
won't work.  You may need to provide a --with-CXX=compiler switch to
force configure to pick the matching C++ compiler, or even say
--without-CXX if you have a C++ compiler but it doesn't match the C
compiler you want to use.

Otherwise the standard build/install procedure described in the
PostgreSQL documentation works fine.
@


1.3
log
@Update faq and hpux faq.
@
text
@a0 1
<PRE>
a173 1
</PRE>
@


1.2
log
@Update FAQ's for release.
@
text
@d1 1
a1 1

d3 1
a3 1
Frequently Asked Questions (FAQ) for PostgreSQL  V6.4
d7 1
a7 1
last updated:           Sat Nov 28 16:21:25 EST 1998
d14 6
a19 6
1.1)    What do I need to install PostgreSQL on HP-UX?
1.2)    Anything special about the build/install procedure?
1.3)    yacc dies trying to process src/backend/parser/gram.y.
1.4)    Linking the main postgres executable fails, complaining that
        there's no "alloca" function.
1.5)    OK, it seemed to build and install, but the regression test fails.
d26 1
a26 1
1.1)    What do I need to install PostgreSQL on HP-UX?
d28 1
a28 1
PostgreSQL 6.4 is known to build and pass regression test on HPUX 9.03,
d31 2
a32 5
machines, too.  (No one has reported trying it with HPUX 11 yet.)
Since this is a new FAQ, I don't yet have a lot of information about the
exact prerequisites, but I'd appreciate hearing from anyone who fails to
build a working copy, so that we can add more info about exactly what is
needed.
d34 1
a34 1
Aside from PostgreSQL 6.4 or later sources, you will need GNU make
d43 6
a48 3
should be current on libc and ld/dld patches, as well as compiler
patches if you are using HP's C compiler (but I don't currently know of
any specific failures due to not having recent patches for these files).
d57 1
a57 1
1.2)    Anything special about the build/install procedure?
d62 1
a62 1
        ./configure --with-template=hpux_cc
d64 1
a64 1
        ./configure --with-template=hpux_gcc
d70 4
a73 3
you configure; the distributed files contain neither -O nor -g switches,
which is hardly optimal for any situation.  I've seen no problems using
-O with gcc 2.7.2.*.
d91 1
a91 1
1.3)    yacc dies trying to process src/backend/parser/gram.y.
d102 2
a103 1
derived files do.
d105 1
a105 5
2. Install "bison" (GNU yacc) and reconfigure.  Bison doesn't have a
problem with large grammars.  Note this is not the right choice if you
are using HP's cc on HPUX 9 --- see next item.

3. Increase yacc's table sizes enough to cope.  With a pre-6.4
d108 1
a108 1
        -d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
d114 3
a117 2
1.4)    Linking the main postgres executable fails, complaining that
        there's no "alloca" function.
d119 2
a120 5
If you're using HP's cc on HPUX 9, it's right: there's no alloca
function.  The only place in PostgreSQL that uses alloca is the parser
(gram.c), and that does so only if it was generated with GNU bison.
Unfortunately the distribution copy of gram.c is made with bison.
There are several possible answers:
d122 11
a132 2
  1. Remake gram.c with HP's yacc (see above item for switch settings).
     You might also need to remake src/backend/bootstrap/bootparse.c.
d140 1
a140 1
1.5)    OK, it seemed to build and install, but the regression test fails.
d148 1
a148 1
TEST(S)                 COMMENTS
d150 2
a151 2
int2, int4:             pg_atoi generates a differently worded error
                        message for integer overflow.
d153 18
a170 20
float8:                 In 6.4, float8 shows some differences due to
                        different handling of overflow/underflow errors in
                        exp() and pow().  This should be fixed in 6.4.1
                        and later.

float8, geometry:       Lots of differences in the last digit or two
                        because of different roundoff errors in floating
                        arithmetic.  Also, HPUX does not distinguish
                        -0 from 0 during printout, but the reference
                        platform does.

horology:               HPUX time library does not know about daylight
                        savings time before 1970, so there are some
                        places in horology where a time will be shown
                        in PST instead of PDT.

In addition, the int8 regression test will fail massively on HPUX 9,
because int8 doesn't actually work on this platform (sprintf/sscanf
don't cope with long long int).  Either upgrade to HPUX 10, or don't
use int8 data.
d175 1
@


1.1
log
@New platform-specific FAQ for HP-UX sites.
@
text
@d1 1
d14 6
a19 6
1.1)	What do I need to install PostgreSQL on HP-UX?
1.2)	Anything special about the build/install procedure?
1.3)	yacc dies trying to process src/backend/parser/gram.y.
1.4)	Linking the main postgres executable fails, complaining that
	there's no "alloca" function. 
1.5)	OK, it seemed to build and install, but the regression test fails.
d26 1
a26 1
1.1)	What do I need to install PostgreSQL on HP-UX?
d57 1
a57 1
1.2)	Anything special about the build/install procedure?
d62 1
a62 1
	./configure --with-template=hpux_cc
d64 1
a64 1
	./configure --with-template=hpux_gcc
d90 1
a90 1
1.3)	yacc dies trying to process src/backend/parser/gram.y.
d110 1
a110 1
	-d -Np2000 -Ns3000 -Nm100000 -Nl2000 -Na30000 -Nc10000
d117 2
a118 2
1.4)	Linking the main postgres executable fails, complaining that
	there's no "alloca" function. 
d135 1
a135 1
1.5)	OK, it seemed to build and install, but the regression test fails.
d143 1
a143 1
TEST(S)			COMMENTS
d145 2
a146 2
int2, int4:		pg_atoi generates a differently worded error
			message for integer overflow.
d148 15
a162 15
float8:			In 6.4, float8 shows some differences due to
			different handling of overflow/underflow errors in
			exp() and pow().  This should be fixed in 6.4.1
			and later.

float8, geometry:	Lots of differences in the last digit or two
			because of different roundoff errors in floating
			arithmetic.  Also, HPUX does not distinguish
			-0 from 0 during printout, but the reference
			platform does.

horology:		HPUX time library does not know about daylight
			savings time before 1970, so there are some
			places in horology where a time will be shown
			in PST instead of PDT.
@


1.1.2.1
log
@Prepare for 6.4.1.
@
text
@d1 6
d8 163
a170 62
                                     User
                                       
     * Tutorial - for those not familiar with PostgreSQL
     * User's Guide - updated for PostgreSQL 6.3 (new html 98-08-16)
     * Administrator's Guide - help in installing and managing PostgreSQL
       (new html 98-08-16)
     * Programmer's Guide - for those programming in PostgreSQL, using
       various interfaces (new html 98-08-16)
     * Integrated Document (includes others above) - for those
       programming in PostgreSQL, using various interfaces (new html
       98-08-16)
     * The FAQ (Frequently Asked Questions) is available in
          + English
          + Japanese
          + Korean by Khan
     * Platform-specific FAQ's are available for
          + Linux
               o English by Andrew Martin
               o Japanese by Jun Kuwamura
               o Korean by Khan
               o Italian by Daniele Medri
          + Irix
          + HP-UX
       
   New versions of the User's Guide
   
                                  Developers
                                       
     * How PostgreSQL Processes a Query - a guide to all modules and
       directories, including a flowchart
     * Developer's FAQ
          + English by Bruce Momjian
          + Korean by Khan
     * Developer's Guide - for contributing to the PostgreSQL
       distribution
     * Anon-CVS access to source code
       
                                     Misc
                                       
   More information regarding the documentation, contact information, and
   SQL references, read the Appendices.
   
   The 6.3.2 man pages have been HTML-ized by Aleksey Dashevsky
   (lyolik@@luckynet.co.il). We are currently transitioning to the
   SGML-based documentation mentioned above. However, the man pages may
   contain information not yet in the new documentation. In particular,
   the man pages for SQL commands and for programs such as psql contain
   the best available information for now. pod2html for the perl5
   interface is also current.
   
   The TODO List includes information on what has recently been completed
   and what we are planning on doing.
     _________________________________________________________________
   
   If you have questions about this website, please contact our
   webmaster. 
   
   This page was last modified 18:00:01 on Saturday, 28 November 1998. 
   
   Copyright  1994-8 PostgreSQL Organization
   
   All rights reserved.
@
