New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
pgrouting extension not creating on OS X #685
Comments
@JamesMilnerUK |
@JamesMilnerUK I'm wondering if you have multiple versions of PostgreSQL and brew installed into a different location. I thought brew installed PostgreSQL in something like Cellar, which doesn't seem to match what you have. Did you install your PostgreSQL using homebrew as well, or did you get that elsewhere? |
@cvvergara it will be the latest version available on brew so: https://homebrew.bintray.com/bottles/pgrouting-2.2.4_1.el_capitan.bottle.tar.gz I assume that's 2.2.4 @robe2 I think you might be on to something. I installed PostgreSQL from the official website using the Enterprise DB installer / Stackbuilder, which might put PostgreSQL in a different location to what pgrouting expects. Postgres appears in: /Library/PostgreSQL/9.5/data Where as PostGIS and pgrouting seems to be installed to: /usr/local/Cellar/postgis/2.2.2_2 I think brew sets up a symbolic link however? |
latest: 2.3.0 |
Expected behavior and actual behavior
using
brew install pgrouting
after
brew install postgis
and using
to install the respective extensions. In this case the command to install pgrouting gives the error:
ERROR: could not open extension control file "/Library/PostgreSQL/9.5/share/postgresql/extension/pgrouting.control": No such file or directory
I have also tried building manually and get the same error. Any ideas?
Specifications like the version of pgRouting/PostGIS and PostgreSQL as well as Operating System
OS: Mac 10.11.2 (15C50)
PG and PostGIS:
"POSTGIS="2.2.2 r14797" GEOS="3.4.2-CAPI-1.8.2 r3921" PROJ="Rel. 4.9.1, 04 March 2015" GDAL="GDAL 1.11.2, released 2015/02/10 GDAL_DATA not found" LIBXML="2.9.2" LIBJSON="0.12" RASTER"
The text was updated successfully, but these errors were encountered: