blob: 1652bc305b6685201ae5ca94fd12217230455ff8 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
|
=======================================================
Frequently Asked Questions (FAQ) for PostgreSQL V6.5
Sun Solaris Specific
TO BE READ IN CONJUNCTION WITH THE NORMAL FAQ
=======================================================
last updated: $Date: 2000/10/19 03:18:56 $
current maintainer: Marc Liyanage (liyanage@access.ch)
original author: Marc Liyanage (liyanage@access.ch)
Contents:
1.1) What tools do I need to build and install PostgreSQL on Solaris?
1.2) What else do I have to do before building PostgreSQL?
Notes:
- The commands given here are for the bash shell. If you use
a different shell, you'll have to change the commands accordingly,
especially these regarding environment variables.
- These instructions are written for Solaris 2.6
----------------------------------------------------------------------
Section 1: Building and Installing PostgreSQL
----------------------------------------------------------------------
1.1) What tools do I need to build and install PostgreSQL on Solaris?
You will need
- GNU flex 2.5.4 or better (the lex included in Solaris 2.6 won't work)
- GNU bison (the yacc included in Solaris 2.6 won't work)
- GNU zip (gzip and especially gunzip for installing the docs)
- GNU make
- GNU readline library
We also used
- GNU cc (gcc 2.8.1)
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
1.2) What else do I have to do before building PostgreSQL?
Shared libraries
----------------
The default installation procedure puts the shared libraries
into "/usr/local/pgsql/lib", but the dynamic loader won't
find them there at runtime unless you use some hack like
symlinking the libraries in /usr/lib or setting LD_LIBRARY_PATH
for every user that will use the DB system.
The first time you'll encounter this problem is usually when
running "initdb". It will fail with something like
ld.so.1: pg_id: fatal: libpq.so: open failed: No such file or directory
We recommend that you store the path of the directory containing
the libraries in the environment variable LD_RUN_PATH *before*
starting the build. This will cause the linker to store this
path in the binaries.
Do this:
# export LD_RUN_PATH=/usr/local/pgsql/lib
(or wherever you choose to put the libraries)
There is some good information about this here:
http://www.visi.com/~barr/ldpath.html
|
