On Friday 20 August 2004 03:52, Tom Lane wrote:
> Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> > It seems that the problem is in src/template/linux:
> >
> > $ cat src/template/linux=20
> > # Force _GNU_SOURCE on; plperl is broken with Perl 5.8.0 otherwise
> > CPPFLAGS="-D_GNU_SOURCE"
> >
> > w
Stefanos Harhalakis <[EMAIL PROTECTED]> writes:
> It seems that the problem is in src/template/linux:
> $ cat src/template/linux=20
> # Force _GNU_SOURCE on; plperl is broken with Perl 5.8.0 otherwise
> CPPFLAGS="-D_GNU_SOURCE"
> which is beeing sourced by configure.in. Changing this to
> CPPFLAG
On Wednesday 18 August 2004 23:09, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > This happens because AC_CHECK_HEADERSis implemented using the
> > preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
>
> The correct variable is CPPFLAGS. Actually, you can also use
> --with-includes
On Wednesday 18 August 2004 20:14, Peter Eisentraut wrote:
> Stefanos Harhalakis wrote:
> > It seems that you've removed the possibility to add an argument to
> > --with-openssl option of the configure script. Currently I'm
> > maintaining two systems where the openssl is not somewhere in the
> >
Stefanos Harhalakis wrote:
> This happens because AC_CHECK_HEADERSis implemented using the
> preprocessor (cpp/gcc -E) without adding CFLAGS/CXXFLAGS:
The correct variable is CPPFLAGS. Actually, you can also use
--with-includes, but this is only in PostgreSQL, so I suggest you get
used to CPPFL
Stefanos Harhalakis wrote:
> It seems that you've removed the possibility to add an argument to
> --with-openssl option of the configure script. Currently I'm
> maintaining two systems where the openssl is not somewhere in the
> standard paths and thus the only way to compile with SSL seems to be
