You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2023. It is now read-only.
Encountered in compiling visr/GDAL.jl, partly due to #40
When using both 0.7 and 1.1 (common for backward compatability) and a package that is shared between those versions the generated deps.jl can include Julia *LIBRARY_PATHs other than the version in use.
Steps to reproduce:
build GDAL on 0.7
build GDAL on 1.1 (overwriting shared deps.jl)
use GDAL on 0.7
leads to:
Error: Error building `GDAL`:
│ ERROR: could not load library "/Applications/Julia-0.7.app/Contents/Resources/julia/lib/julia/sys.dylib"
│ dlopen(/Applications/Julia-0.7.app/Contents/Resources/julia/lib/julia/sys.dylib, 6): Symbol not found: _jl_current_exception
│ Referenced from:/Applications/Julia-1.1.app/Contents/Resources/julia/lib/julia/sys.dylib
│ Expected in:/Applications/Julia-0.7.app/Contents/Resources/julia/bin/../lib/libjulia.dylib
│ in/Applications/Julia-1.1.app/Contents/Resources/julia/lib/julia/sys.dylib
└ @ Pkg.Operations /Users/osx/buildbot/slave/package_osx64/build/usr/share/julia/stdlib/v0.7/Pkg/src/Operations.jl:1068
The text was updated successfully, but these errors were encountered:
* First try at "Building tips" documentation
The intent is to provide tips for common build scenarios. If common items keep appearing, they could be baked into the environment.
* Updates based on input from Elliot and David
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Encountered in compiling visr/GDAL.jl, partly due to #40
When using both 0.7 and 1.1 (common for backward compatability) and a package that is shared between those versions the generated
deps.jl
can include Julia*LIBRARY_PATH
s other than the version in use.Steps to reproduce:
deps.jl
)leads to:
The text was updated successfully, but these errors were encountered: