ok, on second thought, I figured the issue. I assume you have statically
linked PROJ or have explicitly enabled EMBED_RESOURCE_FILES=ON when
building it (cf
https://proj.org/en/latest/install.html#cmdoption-arg-EMBED_RESOURCE_FILES).
At least I can reproduce those test failures with
EMBED_RESOURCE_FILES=ON. Those tests aren't compatible with that
configuration of PROJ. Ideally we should have some mechanism to skip
them, but that would require that PROJ exposes how it has been built. In
any case, this isn't something to worry about, just a testing issue.
Le 12/03/2025 à 18:53, Roger Bivand a écrit :
On Wed, 12 Mar 2025, Even Rouault wrote:
Le 12/03/2025 à 18:07, Roger Bivand a écrit :
On Wed, 12 Mar 2025, Even Rouault wrote:
unset PROJ_LIB ; ctest for example. Should I add the complete
output of
running ctest to this thread (490 lines)?
maybe paste it some paste service (github gist, etc) and link it
to it.
https://gist.github.com/rsbivand/09bd9e998889a44d2eecbb842c1a5168
sorry, no clue. I doubt this is 9.6.0 related
There are no such errors with PROJ 9.5.1 and GDAL 3.10.2 on the same
platform, so the only obvious change is building GDAL with 9.5.1 or
9.6.0RC2. That is why I waited, as the airport internet I was
depending on before I got to my desktop could have been a factor. For
9.5.1:
Start 35: test-osr-set-proj-search-paths
35/46 Test #35: test-osr-set-proj-search-paths ... Passed 0.12 sec
Start 40: autotest_gdrivers
40/46 Test #40: autotest_gdrivers ................ Passed 125.56 sec
Start 43: autotest_osr
43/46 Test #43: autotest_osr ..................... Passed 4.14 sec
Roger
--
http://www.spatialys.com
My software is free, but my time generally not.
_______________________________________________
PROJ mailing list
PROJ@lists.osgeo.org
https://lists.osgeo.org/mailman/listinfo/proj
