The 7.6 Postgres module fails to build on OpenSolaris/Solaris 11. In 7.4 and 7.7 it works or does not fatally stop the compilation at least.
Could some postgres guru take a look at why 7.6 and 7.7 does not behave in the same way?
Ref:
http://pike.ida.liu.se/generated/pikefarm/7.6/490_290/makelog.html http://pike.ida.liu.se/generated/pikefarm/7.7/1558_255/makelog.html
On Mon, 29 May 2006 12:05:01 +0000 (UTC) "Peter Bortas @ Pike developers forum" 10353@lyskom.lysator.liu.se wrote:
The 7.6 Postgres module fails to build on OpenSolaris/Solaris 11. In 7.4 and 7.7 it works or does not fatally stop the compilation at least.
Could some postgres guru take a look at why 7.6 and 7.7 does not behave in the same way?
Ref:
http://pike.ida.liu.se/generated/pikefarm/7.6/490_290/makelog.html http://pike.ida.liu.se/generated/pikefarm/7.7/1558_255/makelog.html
I think its because pike 7.7 searches for more include dirs than 7.6 does. Where is openssl/ssl.h on that machine?
Adam
/usr/sfw. Rather than add that wouldn't it be better to first add the defensive aproach of configuring postgres out if the headers aren't found?
On Tue, 30 May 2006 01:15:02 +0000 (UTC) "Peter Bortas @ Pike developers forum" 10353@lyskom.lysator.liu.se wrote:
/usr/sfw. Rather than add that wouldn't it be better to first add the defensive aproach of configuring postgres out if the headers aren't found?
I'm not sure. Postgresql will only need the ssl headers if it was compiled with ssl support. So the only time this happens is when the postgresql configure script found the include dir with openssl in it, but the pike configure script doesn't find that dir.
So, its either add a check for /usr/sfw, or add a check to see if postgresql found openssl and if so, check for openssl ourselves. The former may fix other problems finding includes/libs for other modules.
Adam
pike-devel@lists.lysator.liu.se
-
Adam Montague -
Peter Bortas ＠ Pike developers forum