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