[Bug 226962] databases/postgis24 Question: How to run postgis24 with postgresql10 ?

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Tue May 1 19:40:53 UTC 2018


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=226962

John Parkey <john at acru.co.uk> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |john at acru.co.uk

--- Comment #3 from John Parkey <john at acru.co.uk> ---
I am having a similar problem.  I am building using synth, on FreeBSD 11.1.

My /etc/make.conf contains a line to add DEFAULT_VERSIONS+=pgsql=10

I have cleared down the whole environment, so that I am building everything
from scratch.  First I build postgresql10-server, -client, -contrib, to make
sure that they are all there.  If I then try to build postgis24, something in
the dependency tree causes postgresql95-server to be pulled in.

I stripped it right back and found that graphics/gdal pulls in 17 dependencies,
and this results in postgresql95-server being built again.  I edited the
Makefile for graphics/gdal to include 'pgsql' in the USES directive, but this
didn't solve the problem.  Looking at the dependencies, it wasn't clear to me
what was causing this - I thought that it might be something to do with
graphics/libgeotiff, but I couldn't find anything definitive (and, to be
honest, I don't really know what I am looking for).

I edited /usr/ports/Mk/bsd.default-versions.mk and set PGSQL_DEFAULT?= 10 -
this allowed graphics/gdal to build, and so then I tried databases/postgis24
which pulled in a further 168 dependencies, and everything built cleanly
(hurrah! finally some progress after two days).  The remaining 728 packages are
building now, so I am hopeful that they will complete without postgresql95
being pulled in again.

Clearly what I have done is a bit of a hack, and I risk the
bsd.default-versions.mk file being overwritten at some point when I refresh the
ports, but hopefully it will help to narrow down the source of the problem.

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-ports-bugs mailing list