> Justin Clift ([EMAIL PROTECTED]) reports a bug with a severity of 3
> When testing which ./configure options work, I've just discovered that something in
>the ./configure process generates the incorrect options when with --with-python and
>--with-openssl are given, such that the python interface doesn't find the openssl
>headers when it wants them.
Looks like interface/python's GNUmakefile and Setup.in.raw need to
cooperate to pass additional -I fields to the compiler. Perhaps
-e 's%@INCLUDES@%$(filter -I%, $(CPPFLAGS))%g' \
in GNUmakefile and the obvious thing in Setup.in.raw. Would this allow
removing either of the explicit -I switches in Setup.in.raw?
regards, tom lane
---------------------------(end of broadcast)---------------------------
TIP 4: Don't 'kill -9' the postmaster
