|
1 |
| -<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.194 2004/02/03 17:34:02 tgl Exp $ --> |
| 1 | +<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.195 2004/02/26 02:09:40 momjian Exp $ --> |
2 | 2 |
|
3 | 3 | <chapter id="installation">
|
4 | 4 | <title><![%standalone-include[<productname>PostgreSQL</>]]>
|
@@ -193,14 +193,11 @@ su - postgres
|
193 | 193 | </para>
|
194 | 194 |
|
195 | 195 | <para>
|
196 |
| - The catch is that the Python distribution or the Python |
197 |
| - maintainers do not provide any direct way to do this. The |
198 |
| - closest thing we can offer you is the information in <ulink |
199 |
| - url="http://www.python.org/doc/FAQ.html#3.30">Python FAQ |
200 |
| - 3.30</ulink>. On some operating systems you don't really have |
201 |
| - to build a shared library, but then you will have to convince |
202 |
| - the <productname>PostgreSQL</> build system of this. Consult |
203 |
| - the <filename>Makefile</filename> in the |
| 196 | + If you have problems, try running Python's configure using the |
| 197 | + <literal>--enable-shared</> flag. On some operating systems you |
| 198 | + don't really have to build a shared library, but you will have |
| 199 | + to convince the <productname>PostgreSQL</> build system of this. |
| 200 | + Consult the <filename>Makefile</filename> in the |
204 | 201 | <filename>src/pl/plpython</filename> directory for details.
|
205 | 202 | </para>
|
206 | 203 | </listitem>
|
|