postgresql/doc/FAQ_Solaris

82 lines
2.6 KiB
Plaintext
Raw Normal View History

2001-03-13 21:42:11 +01:00
============================================================
2001-12-10 14:03:12 +01:00
Frequently Asked Questions (FAQ) for PostgreSQL 7.2
2001-03-13 21:42:11 +01:00
Sun Solaris specific
to be read in conjunction with the installation instructions
============================================================
last updated: $Date: 2002/02/12 22:35:07 $
1999-09-27 05:34:54 +02:00
2001-12-10 14:03:12 +01:00
current maintainer: Peter Eisentraut <peter_e@gmx.net>
1999-09-27 05:34:54 +02:00
Contents:
2001-03-13 21:42:11 +01:00
1) What tools do I need to build and install PostgreSQL on Solaris?
2) Why do I get problems when building with OpenSSL support?
2001-04-04 22:02:31 +02:00
3) Why does configure complain about a failed test program?
4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
2001-03-13 21:42:11 +01:00
1) What tools do I need to build and install PostgreSQL on Solaris?
1999-09-27 05:34:54 +02:00
You will need
2001-03-13 21:42:11 +01:00
- GNU zip (for installing the documentation)
1999-09-27 05:34:54 +02:00
- GNU make
2001-03-13 21:42:11 +01:00
- GNU readline library (optional)
- GCC (if you don't have Sun's compiler)
1999-09-27 05:34:54 +02:00
If you like Solaris packages, you can find these tools here:
http://www.sunfreeware.com
If you prefer sources, look here:
http://www.gnu.org/order/ftp.html
You can build with either GCC or Sun's compiler suite.
If you are using Sun's compiler, be careful *not* to select /usr/ucb/cc;
use /opt/SUNWspro/bin/cc.
1999-09-27 05:34:54 +02:00
2001-03-13 21:42:11 +01:00
2) Why do I get problems when building with OpenSSL support?
1999-09-27 05:34:54 +02:00
When you build PostgreSQL with OpenSSL support you might get
2001-03-13 21:42:11 +01:00
compilation errors in the following files:
1999-09-27 05:34:54 +02:00
2001-03-13 21:42:11 +01:00
src/backend/libpq/crypt.c
src/backend/libpq/password.c
src/interfaces/libpq/fe-auth.c
src/interfaces/libpq/fe-connect.c
1999-09-27 05:34:54 +02:00
2001-03-13 21:42:11 +01:00
This is because of a namespace conflict between the standard
/usr/include/crypt.h header and the header files provided by OpenSSL.
1999-09-27 05:34:54 +02:00
Upgrading your OpenSSL installation to version 0.9.6a fixes this
problem.
2001-04-04 22:02:31 +02:00
3) Why does configure complain about a failed test program?
This is probably a case of the run-time linker being unable to find
libz or some other non-standard library, such as libssl. To point it
to the right location, set the LD_LIBRARY_PATH environment variable,
e.g.,
LD_LIBRARY_PATH=/usr/local/lib:/usr/local/ssl/lib
export LD_LIBRARY_PATH
and restart configure. You will also have to keep this setting
whenever you run any of the installed PostgreSQL programs.
2001-12-10 14:03:12 +01:00
Alternatively, set the environment variable LD_RUN_PATH. See the
ld(1) man page for more information.
4) How do I ensure that pg_dump and pg_restore can handle files > 2 Gb?
By default, gcc will build programs that only handle 32-bit file offsets.
This is not a real problem for the server but can easily be trouble for
pg_dump and pg_restore. Before running 'configure', set your CFLAGS variable
to specify support for files with 64-bit offsets. This has been verified
to work on Solaris 7:
CFLAGS="`getconf LFS_CFLAGS`"; export CFLAGS