Skip to content
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

Vagrant: missing proj6 #1281

Closed
rcoup opened this issue Feb 7, 2019 · 2 comments · Fixed by #1291
Closed

Vagrant: missing proj6 #1281

rcoup opened this issue Feb 7, 2019 · 2 comments · Fixed by #1291

Comments

@rcoup
Copy link
Member

rcoup commented Feb 7, 2019

@miurahr @rouault

Expected behavior and actual behavior.

Clean vagrant dev environment provisioning:

$ vagrant up
...
==> default: Running provisioner: shell...
    default: Running: /var/folders/4z/cqv7pdjj0hvfj3c15bwy9g4r0000gn/T/vagrant-shell20190208-56589-89bd8w.sh
    default: + NUMTHREADS=2
    default: + [[ -f /sys/devices/system/cpu/online ]]
    default: ++ cut -f 2 -d - /sys/devices/system/cpu/online
    default: + NUMTHREADS=3
    default: + export NUMTHREADS
    default: + rsync -a /vagrant/gdal/ /home/vagrant/gnumake-build-gcc4.8
    default: + rsync -a --exclude=__pycache__ /vagrant/autotest/ /home/vagrant/gnumake-build-gcc4.8/autotest
    default: + echo rsync -a /vagrant/gdal/ /home/vagrant/gnumake-build-gcc4.8/
    default: + echo rsync -a --exclude=__pycache__ /vagrant/autotest/ /home/vagrant/gnumake-build-gcc4.8/autotest
    default: + chmod +x /home/vagrant/gnumake-build-gcc4.8/resync.sh
    default: + cd /home/vagrant/gnumake-build-gcc4.8
    default: + export CCACHE_CPP2=yes
    default: + CCACHE_CPP2=yes
    default: + ARCH_FLAGS=
    default: + AVX2_AVAIL=1
    default: + grep avx2 /proc/cpuinfo
    default: + [[ 1 == \1 ]]
    default: + ARCH_FLAGS=-mavx2
    default: + echo 'AVX2 available on CPU'
    default: AVX2 available on CPU
    default: + CFLAGS=-mavx2
    default: + CXXFLAGS=-mavx2
    default: + CC='ccache gcc'
    default: + CXX='ccache g++'
    default: + LDFLAGS=-lstdc++
    default: + ./configure --prefix=/usr --without-libtool --enable-debug --with-jpeg12 --with-python --with-poppler --with-podofo --with-spatialite --with-java --with-mdb --with-jvm-lib-add-rpath --with-epsilon --with-gta --with-mysql --with-liblzma --with-webp --with-libkml --with-openjpeg=/usr/local --with-armadillo
...
    default: checking for iconv...
    default: yes
    default: checking for working iconv...
    default: yes
    default: checking for iconv declaration...
    default:          extern size_t iconv (iconv_t cd, char * *inbuf, size_t *inbytesleft, char * *outbuf, size_t *outbytesleft);
    default: using ICONV_CPP_CONST=""
    default: checking for PROJ >= 6 library...
    default: checking for proj_create_from_wkt in -lproj...
    default: no
    default: checking for internal_proj_create_from_wkt in -lproj...
    default: no
    default: checking for internal_proj_create_from_wkt in -linternalproj...
    default: no
    default: configure: error: PROJ 6 symbols not found
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

I guess proj6 needs installing in gdal/scripts/vagrant/gdal.sh?

Operating system

Vagrant (Ubuntu 14.04/64bit)

GDAL version and provenance

master @ 4ee1c99

@miurahr
Copy link
Contributor

miurahr commented Feb 12, 2019

I know GDAL 2.4.0 now include a [RFC73[(https://github.com//pull/1185): Integration of PROJ6 for WKT2 and now requires proj6 but Vagrant scripts have been with proj4, which is provided by ubuntugis project and my PPA for mingw compilation.

It is a big changes in dependencies and we may need to update many of packages based on proj6. How can we provide proj6?

Now proj project has an option to RENAME_SYMBOLS in git HEAD, that is used in Travis-CI scripts. Do we do same way, compiling proj with it, on Vagrant?

@rouault
Copy link
Member

rouault commented Feb 12, 2019

Now proj project has an option to RENAME_SYMBOLS in git HEAD, that is used in Travis-CI scripts. Do we do same way, compiling proj with it, on Vagrant?

I'd suggest so. Recompiling all other dependencies against PROJ master would be unpractical

@miurahr miurahr mentioned this issue Feb 13, 2019
5 tasks
miurahr added a commit to miurahr/gdal that referenced this issue Feb 13, 2019
- Install proj.6 library from git HEAD
- Build sqlite3 and proj.6 with mingw32-w64
- Install mingw32-w64 binaries into /usr/local/x86_64-w64-mingw32/
- Fixed OSGeo#1281

Signed-off-by: Hiroshi Miura <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants