various documentation, since those lists are now dead/deprecated.
Point to pgsql-bugs and/or pgsql-hackers as appropriate.
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
dnl Process this file with autoconf to produce a configure script.
-dnl $PostgreSQL: pgsql/configure.in,v 1.546.2.9 2008/10/31 02:38:33 scrappy Exp $
+dnl $PostgreSQL: pgsql/configure.in,v 1.546.2.10 2009/01/06 17:27:18 tgl Exp $
dnl
dnl Developers, please strive to achieve this order:
dnl
To try a manual configuration, look into the src/template directory
for a similar platform and use the '--with-template=' option.
rectifying this. Include the above 'checking host system type...'
line.
*******************************************************************
* accessible directory. If you want to make other assumptions,
* such as using a vendor-specific archive and access API, these
* routines are the ones you'll need to change. You're
* or personally to the current maintainer. Those changes may be
* folded in to later versions of this program.
*/
-If PostgreSQL failed to compile on your computer or you found a bug that
-is likely to be specific to one platform, then please fill out this form
-
-To report non-porting-related bugs, fill out the form below and e-mail it to
+If PostgreSQL failed to compile on your computer or you found a bug,
If your bug report has security implications and you'd prefer that it not
become immediately visible in public archives, don't send it to pgsql-bugs.
If you not only found the problem but solved it and generated a patch
command "diff -c" to generate the patch.
You may also enter a bug report at http://www.postgresql.org/ instead of
-<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.300.2.2 2008/06/05 19:56:14 alvherre Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/installation.sgml,v 1.300.2.3 2009/01/06 17:27:19 tgl Exp $ -->
<chapter id="installation">
<title><![%standalone-include[<productname>PostgreSQL</>]]>
to be supported according to recent build farm results, please report
in porting <productname>PostgreSQL</> to a new platform,
to discuss that.
</para>
</sect1>
-<!-- $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.28 2007/01/31 20:56:18 momjian Exp $ -->
+<!-- $PostgreSQL: pgsql/doc/src/sgml/problems.sgml,v 2.28.2.1 2009/01/06 17:27:19 tgl Exp $ -->
<sect1 id="bug-reporting">
<title>Bug Reporting Guidelines</title>
Please be specific about what part of the documentation you are unhappy
with.
</para>
-
+
<para>
If your bug is a portability problem on a non-supported platform,
so we (and you) can work on
porting <productname>PostgreSQL</productname> to your platform.
</para>