@@ -169,32 +169,22 @@ su - postgres
169169 also on most platforms. This appears to be the default in
170170 recent <productname>Perl</productname> versions, but it was not
171171 in earlier versions, and in any case it is the choice of whomever
172- installed Perl at your site.
172+ installed Perl at your site. <filename>configure</filename> will fail
173+ if building <application>PL/Perl</application> is selected but it cannot
174+ find a shared <filename>libperl</filename>. In that case, you will have
175+ to rebuild and install <productname>Perl</productname> manually to be
176+ able to build <application>PL/Perl</application>. During the
177+ configuration process for <productname>Perl</productname>, request a
178+ shared library.
179+ </para>
180+
181+ <para>
173182 If you intend to make more than incidental use of
174183 <application>PL/Perl</application>, you should ensure that the
175184 <productname>Perl</productname> installation was built with the
176185 <literal>usemultiplicity</> option enabled (<literal>perl -V</>
177186 will show whether this is the case).
178187 </para>
179-
180- <para>
181- If you don't have the shared library but you need one, a message
182- like this will appear during the <productname>PostgreSQL</>
183- build to point out this fact:
184- <screen>
185- *** Cannot build PL/Perl because libperl is not a shared library.
186- *** You might have to rebuild your Perl installation. Refer to
187- *** the documentation for details.
188- </screen>
189- (If you don't follow the on-screen output you will merely notice
190- that the <application>PL/Perl</application> library object,
191- <filename>plperl.so</filename> or similar, will not be
192- installed.) If you see this, you will have to rebuild and
193- install <productname>Perl</productname> manually to be able to
194- build <application>PL/Perl</application>. During the
195- configuration process for <productname>Perl</productname>,
196- request a shared library.
197- </para>
198188 </listitem>
199189
200190 <listitem>
@@ -220,28 +210,15 @@ su - postgres
220210 library, the <indexterm><primary>libpython</primary></indexterm>
221211 <filename>libpython</filename> library must be a shared library
222212 also on most platforms. This is not the case in a default
223- <productname>Python</productname> installation. If after
224- building and installing <productname>PostgreSQL</> you have a file called
225- <filename>plpython.so</filename> (possibly a different
226- extension), then everything went well. Otherwise you should
227- have seen a notice like this flying by:
228- <screen>
229- *** Cannot build PL/Python because libpython is not a shared library.
230- *** You might have to rebuild your Python installation. Refer to
231- *** the documentation for details.
232- </screen>
233- That means you have to rebuild (part of) your
234- <productname>Python</productname> installation to create this
235- shared library.
236- </para>
237-
238- <para>
239- If you have problems, run <productname>Python</> 2.3 or later's
240- configure using the <literal>--enable-shared</> flag. On some
241- operating systems you don't have to build a shared library, but
242- you will have to convince the <productname>PostgreSQL</> build
243- system of this. Consult the <filename>Makefile</filename> in
244- the <filename>src/pl/plpython</filename> directory for details.
213+ <productname>Python</productname> installation built from source, but a
214+ shared library is available in many operating system
215+ distributions. <filename>configure</filename> will fail if
216+ building <application>PL/Python</application> is selected but it cannot
217+ find a shared <filename>libpython</filename>. That might mean that you
218+ either have to install additional packages or rebuild (part of) your
219+ <productname>Python</productname> installation to provide this shared
220+ library. When building from source, run <productname>Python</>'s
221+ configure with the <literal>--enable-shared</> flag.
245222 </para>
246223 </listitem>
247224