Docu question
In manage-ag.sgml our docs says:
[...]
risk. To allow it, you must compile <productname>PostgreSQL</> with
the C preprocessor macro <literal>ALLOW_ABSOLUTE_DBPATHS</>
defined. One way to do this is to run the compilation step like
this:
<programlisting>
gmake CPPFLAGS=-DALLOW_ABSOLUTE_DBPATHS all
</programlisting>
[...]
I wonder if there's a reason to suggest this gmake call. After all it
makes gmake disregard the CPPFLAGS settings in the Makefile. This for
instance breaks ecpg compilation on Linux as -D_GNU_SOURCE as defined in the
Makefiles is needed for LONG_LONG_MIN.
I think we should either change the docs or start using "override" in
the Makefiles.
Michael
--
Michael Meskes
Email: Michael at Fam-Meskes dot De
ICQ: 179140304, AIM/Yahoo: michaelmeskes, Jabber: meskes@jabber.org
Go SF 49ers! Go Rhein Fire! Use Debian GNU/Linux! Use PostgreSQL!
Michael Meskes wrote:
In manage-ag.sgml our docs says:
[...]
risk. To allow it, you must compile <productname>PostgreSQL</> with
the C preprocessor macro <literal>ALLOW_ABSOLUTE_DBPATHS</>
defined. One way to do this is to run the compilation step like
this:
<programlisting>
gmake CPPFLAGS=-DALLOW_ABSOLUTE_DBPATHS all
</programlisting>
[...]I wonder if there's a reason to suggest this gmake call. After all it
makes gmake disregard the CPPFLAGS settings in the Makefile. This for
instance breaks ecpg compilation on Linux as -D_GNU_SOURCE as defined in the
Makefiles is needed for LONG_LONG_MIN.I think we should either change the docs or start using "override" in
the Makefiles.
Agreed. This is a problem.
--
Bruce Momjian | http://candle.pha.pa.us
pgman@candle.pha.pa.us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073