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
Builtin pathname for Graphics library wrong #6192
Comments
Comment author: @glondu Without using admin rights, have you tried using DYLD_LIBRARY_PATH? install_name_tool? I think the proper "Mac OS X" way of doing things would be to call install_name_tool at install time. |
Comment author: norm I have tried neither. When I am more awake I will study these questions. |
Comment author: norm The line "export DYLD_LIBRARY_PATH=/opt/X11/lib" added to file .bash_profile is also a workaround. |
Comment author: norm Now, with Mac OS X 10.8 above workaround fails. |
Comment author: @damiendoligez I would like to know if this was specific to the precompiled binaries, or if it still occurs on an OCaml compiled and installed through OPAM. |
Comment author: @xavierleroy This looks like a problem with precompiled MacOS X binaries that were built against a different installation of the X11 libraries than that on the user's machine. Since we no longer distribute precompiled MacOS X binaries, I'm marking this PR as resolved. |
Original bug ID: 6192
Reporter: norm
Status: closed (set by @xavierleroy on 2017-02-16T14:16:39Z)
Resolution: not a bug
Priority: high
Severity: minor
Platform: Macintosh
OS: OS X
OS Version: 10.8.5
Version: 4.01.0
Target version: 4.03.0+dev / +beta1
Category: otherlibs
Monitored by: @glondu
Bug description
Just now the shell command:
ocamlmktop -o mytop graphics.cma
produced an "Error on dynamically loaded library".
Steps to reproduce
After standard install type shell command:
ocamlmktop -o mytop graphics.cma
Additional information
I found a work-around:
mkdir /opt/local
mkdir /opt/local/lib
ln -s /opt/X11/lib/libX11.dylib /opt/local/lib/libX11.6.dylib
but I hesitate to advise users to use sudo privilege.
The text was updated successfully, but these errors were encountered: