Starting julia from anywhere except julia_home crashes

[ViralBShah]

This may be a mac specific problem with finding libraries.

$ ./julia/julia
dyld: Library not loaded: libjulia-release.dylib
Referenced from: /Users/viral/./julia/julia
Reason: image not found
Trace/BPT trap (core dumped)

$ otool -L julia
julia:
libjulia-release.dylib (compatibility version 0.0.0, current version 0.0.0)
/Users/viral/julia/external/../external/root/lib/libreadline.6.2.dylib (compatibility version 6.0.0, current version 6.2.0)
/usr/lib/libutil.dylib (compatibility version 1.0.0, current version 1.0.0)
/usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 125.2.10)
/System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices (compatibility version 1.0.0, current version 38.0.0)
/System/Library/Frameworks/vecLib.framework/Versions/A/vecLib (compatibility version 1.0.0, current version 268.0.1)

[JeffBezanson]

Things are a little more difficult now that the executable depends on libjulia. On linux, julia is linked against the absolute path of the library. This works, but it does prevent you from moving the directory. Maybe we need to start julia with a shell script?

[ViralBShah]

We may need a shell script. Anyways, this is only an issue when we come closer to release.

-viral

On May 13, 2011, at 6:34 AM, JeffBezanson wrote:

Things are a little more difficult now that the executable depends on libjulia. On linux, julia is linked against the absolute path of the library. This works, but it does prevent you from moving the directory. Maybe we need to start julia with a shell script?

Reply to this email directly or view it on GitHub:
#19 (comment)

[ViralBShah]

Fixed by linking absolute path.