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

Building Proj4 on Windows fails due to linking issues #21

Closed
felixcremer opened this issue Jan 11, 2019 · 3 comments · Fixed by #22
Closed

Building Proj4 on Windows fails due to linking issues #21

felixcremer opened this issue Jan 11, 2019 · 3 comments · Fixed by #22

Comments

@felixcremer
Copy link
Member

If I try to build Proj4 on Windows it fails with the following error, but it works if I run it as administrator:

┌ Error: Error building Proj4:
│ ┌ Warning: On Windows, creating file symlinks requires Administrator privileges
│ └ @ Base.Filesystem file.jl:789
│ ┌ Warning: platform_key() is deprecated, use platform_key_abi() from now on
│ │ caller = ip:0x0
│ └ @ Core :-1
│ [ Info: Downloading https://github.com/JuliaGeo/PROJBuilder/releases/download/v4.9.3-3/PROJ.v4.9.3.x86_64-w64-mingw32.tar.gz to C:\Users\user.julia\packag
es\Proj4\GICw3\deps\usr\downloads\PROJ.v4.9.3.x86_64-w64-mingw32.tar.gz...
│ ERROR: LoadError: Could not unpack C:\Users\user.julia\packages\Proj4\GICw3\deps\usr\downloads\PROJ.v4.9.3.x86_64-w64-mingw32.tar.gz into C:\Users\user
.julia\packages\Proj4\GICw3\deps\usr
│ Stacktrace:
│ [1] error(::String) at .\error.jl:33
│ [2] #unpack#98(::Bool, ::Function, ::String, ::String) at C:\Users\user.julia\packages\BinaryProvider\4F5Hq\src\PlatformEngines.jl:660
│ [3] #unpack at .\none:0 [inlined]
│ [4] #install#133(::Prefix, ::String, ::Bool, ::Bool, ::Bool, ::Function, ::String, ::String) at C:\Users\user.julia\packages\BinaryProvider\4F5Hq\src\Pre
fix.jl:347
│ [5] (::getfield(BinaryProvider, Symbol("#kw##install")))(::NamedTuple{(:prefix, :force, :verbose),Tuple{Prefix,Bool,Bool}}, ::typeof(install), ::String, ::St
ring) at .\none:0
│ [6] top-level scope at C:\Users\user.julia\packages\Proj4\GICw3\deps\build.jl:43
│ [7] include at .\boot.jl:317 [inlined]
│ [8] include_relative(::Module, ::String) at .\loading.jl:1044
│ [9] include(::Module, ::String) at .\sysimg.jl:29
│ [10] include(::String) at .\client.jl:392
│ [11] top-level scope at none:0
│ in expression starting at C:\Users\user.julia\packages\Proj4\GICw3\deps\build.jl:39

│ 7-Zip [64] 16.04 : Copyright (c) 1999-2016 Igor Pavlov : 2016-10-04


│ Extracting archive:
│ ERROR: Can not create symbolic link : Access is denied. : C:\Users\user.julia\packages\Proj4\GICw3\deps\usr\bin\invproj.exe
│ --
│ Path =
│ Type = tar
│ Code Page = UTF-8

│ ERROR: Can not create symbolic link : Access is denied. : C:\Users\user.julia\packages\Proj4\GICw3\deps\usr\bin\invgeod.exe

│ Sub items Errors: 2

│ Archives with Errors: 1

│ Sub items Errors: 2
└ @ Pkg.Operations C:\cygwin\home\Administrator\buildbot\worker\package_win64\build\usr\share\julia\stdlib\v1.0\Pkg\src\Operations.jl:1097

@visr
Copy link
Member

visr commented Jan 11, 2019

Thanks for reporting. I've been trying to make a new BinaryBuilder build which will hopefully fix this issue, but did not manage to get a build complete on all platforms:

https://travis-ci.org/JuliaGeo/PROJBuilder

I guess we could try rebuilding the current PROJ version as well, not sure if that will help though.

@evetion
Copy link
Member

evetion commented Jan 20, 2019

According to your error, it seems that:
Warning: On Windows, creating file symlinks requires Administrator privileges

So you could try running Julia as admin and try to build this package again.

@visr
Copy link
Member

visr commented Jan 20, 2019

Yeah he did so as mentioned above. However for those with no admin rights it is still an issue. Nowadays BinaryBuilder avoids symlinks for this reason, so if we can get a new build this should be fixed.

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