Re: configure: error: header file is required for OpenSSL - Mailing list pgsql-general

From Jean-Michel POURE
Subject Re: configure: error: header file is required for OpenSSL
Date
Msg-id 200204220954.44715.jmpoure@translationforge.com
Whole thread Raw
In response to configure: error: header file is required for OpenSSL  (Peter Peltonen <peter.peltonen@fivetec.com>)
Responses OT: Re: configure: error: header file is required for OpenSSL
Re: configure: error: header file is
List pgsql-general
Le Lundi 22 Avril 2002 09:23, Peter Peltonen a écrit :
> --enable-multibyte=LATIN1

1) Multibyte

Latin1 is not a multi-byte character. This is not the way to create a Latin1
database. Creating a Latin1 database is done by CREATE DATABASE foo WITH
ENCODING = "Latin1". Anyway, it is now recommanded to use Latin9 (Latin1 +
euro support) instead of Latin1.

Why don't you simply --enable-multibyte? Then, you will be able to create a
Latin1, Latin9 (=Latin1+euro) or Unicode database. PostgreSQL offers
automatic recoding between server and client using SET CLIENT_ENCODING =
"Latin9".

2) RPMs
If you are new to PostgreSQL, why don't you install RPMs? They can be
downloaded directly from PostgreSQL FTP or from http://www.rpmfind.net.

RPMs answer most needs

a) Binary packages installation
According to your distributions, binary packages can be downloaded and
installed. To install or upgrade, enter "rpm -Uvh package_name1,
package_name2 [...] package_nameN". All packages should be installed at once.

For Mandrake, my list of installed RPMs is as follows:
libecpg3-7.2.1-1mdk.i586.rpm
libpgperl-7.2.1-1mdk.i586.rpm
libpgsql2-7.2.1-1mdk.i586.rpm
libpgsqlodbc0-7.2.1-1mdk.i586.rpm
libpgtcl2-7.2.1-1mdk.i586.rpm
postgresql-7.2.1-1mdk.i586.rpm
postgresql-contrib-7.2.1-1mdk.i586.rpm
postgresql-devel-7.2.1-1mdk.i586.rpm
postgresql-docs-7.2.1-1mdk.i586.rpm
postgresql-jdbc-7.2.1-1mdk.i586.rpm
postgresql-python-7.2.1-1mdk.i586.rpm
postgresql-server-7.2.1-1mdk.i586.rpm
postgresql-tcl-7.2.1-1mdk.i586.rpm
postgresql-test-7.2.1-1mdk.i586.rpm
postgresql-tk-7.2.1-1mdk.i586.rpm

b) Package recompilation
If you have a custom architecture (ex: double-processor), it is recommanded to
recompile packages. Just download PostgreSQL source package and enter : "rpm
--rebuild --target i586 postgresql.src.rpm". Go to /usr/src/RPM/RPMS/i586 to
retrieve binary packages.

c) Package customization
The advantage of RPMs is that you can easily create you own packages with
custom compilation options. To do so:
- install PostgreSQL source RPM : rpm -Uvh postgresql.src.rpm
- modify compilation options in /usr/src/RPM/SPECS/postgresql.spec
- enter rpm -ba /usr/src/RPM/SPECS/postgresql.spec
  This will recreate both source package (*.src.rpm) and binary packages
(*.i586.rpm). therefore you will be able to do several installations without
bothering.

Debian distributions also have their own packages (.deb).

So why bother with source code compilation unless you are a hacker and whish
to contribute source code to PostgreSQL?

Cheers,
Jean-Michel

pgsql-general by date:

Previous
From: "Tille, Andreas"
Date:
Subject: Locale settings
Next
From: "Jacob Vennervald Madsen"
Date:
Subject: Foreign keys