-
Notifications
You must be signed in to change notification settings - Fork 765
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
Test failures on FreeBSD 12 #1644
Comments
You need likely to do: Automatically setting PROJ_LIB for ctest has been fixed just a few days ago in master Autotools work fine and are tested on Travis-CI. We also have a FreeBSD CI: https://cirrus-ci.com/github/OSGeo/PROJ/master , and it uses autotools. You need to use "gmake". And the build requirements are "pkg install -y autoconf automake libtool pkgconf sqlite3 unzip gmake". See https://github.com/OSGeo/PROJ/blob/master/.cirrus.yml |
Using |
I use autotools 99% of the time. You'll get verbose output with them. I guess you could with ctest also ( |
Looks like test failures are associated with the same problem that is blocking the autotools build: proj.db is not being created.
The cmake build just fails to create proj.db silently, while autotools comes to a halt. |
For the record, here's the stop in autotools
|
Do you use |
No, I used just
|
Do you have the sqlite3 binary installed ? Did you look at https://github.com/OSGeo/PROJ/blob/master/.cirrus.yml ? |
I do have sqlite3, and that CI script looks very much like what I'm doing. I will ape it and see if anything else falls out, but this is certainly curious. |
There seems to be a PROJ 6.1.1 FreeBSD package: http://www1.fr.freebsd.org/ports/graphics.html#proj-6.1.1 |
Yep, I'm just trying to track down https://trac.osgeo.org/postgis/ticket/4500 and figured build-and-regress-proj was the first step. I'll probably try the package and see if I can reproduce the ticket. It really looks like a failure to find the dictionary to me. |
proj works fine on PostGIS 2.5 for freebsd 12 and I confirmed sqlite is installed. Unfortunately I'm using pkg install (which uses binaries) and proj 6.1.1 is not yet available on that it seems. |
Sadly installing Proj 6.1.1 did not help. To get Proj 6.1.1 I had to pull it from portsnap.
|
Isn't it related to the lack of some grids (but in that case I would expect all point coordinates to differ) ? |
Confirmed without using PostGIS: FreeBSD environment is FreeBSD 12 with the Proj 6.1.1 pkg installed.
OSX environment is 10.14.6 with Proj 6.1.0 from source.
The results from the OSX run match the results in the regression tests which are generating fine on all our other platforms, so something is awry in the FreeBSD world (probably the packaging). |
Do you get the same thing if you don't use the
Obviously the axis order is switched, but otherwise the numbers are the same as the OSX result above. I am wondering if an old |
Your supposition is correct: when using explicit notation, the results on FreeBSD now match OSX.
So that leaves the question: why/where is FreeBSD picking up some different definition? (I got those explicit notations from the PostGIS Update: Using EPSG notation provides FreeBSD results that are the same as the init string results
Summary so far:
|
What does |
empty string |
Not what I expected.... Try running the above commands with a high debug level:
|
|
Right... So, initially I did this without having the Some |
The logs show that the New York grid is used
So there's no longer any mystery |
So @robe2 I think what this means for us is we need to rework those tests to avoid any geodetic transformation. Stick with cartographic reprojection in the same GCS so that we aren't getting random fails depending on the completeness of the Proj installation. |
@pramsey fine |
For those who stumble across this and are, the PostGIS resolution is here https://trac.osgeo.org/postgis/ticket/4500 |
I'm tracking down this PostGIS ticket 4500 and found that Proj 6.1.1 has unit failures on the FreeBSD 12 platform.
The OS version is
I ran build and test with cmake.
(Side issue, I could not complete a build using the
./configure
method, it died on the build ofproj.db
. If autotools are deprecated and not maintained, maybe they should be fully removed.)The text was updated successfully, but these errors were encountered: