chri...@gmail.com
unread,Nov 1, 2021, 4:33:26 AM11/1/21Sign in to reply to author
Sign in to forward
You do not have permission to delete messages in this group
Either email addresses are anonymous for this group or you need the view member email addresses permission to view the original message
to sv...@googlegroups.com
Hello Folks,
Several people have reported that svnX (v2.0.1) fails to launch on macOS 12.0.
Multiple reports indicate ‘Symbol not found: _svn_client_version’.
The issue appears to be the same on X86 & M1 CPUs.
I believe this affects all users of svnX and macOS 12.0 the same.
Currently I do not know what, exactly, the problem is, or how best to fix it.
The function ‘_svn_client_version’ is contained within one of Subversion’s libraries.
SvnX weak links against the Subversion libraries to enable support for the ‘Call Subversion libraries directly’ feature (in Preferences > General).
If the libraries are not where they are expected to be or don’t contain the required symbols (i.e. symbol(s) not found) or fail to meet other criteria then that option should simply appear disabled in the Preferences window.
On macOS 12.0 this seems not to be working as it has always worked.
Could someone please try the following and report back. (Either directly to me or via the list.)
1. Make sure you have the following libraries (installed as part of an Subversion) before launching svnX:
/opt/subversion/lib/libapr-1.0.dylib
/opt/subversion/lib/libsvn_client-1.0.dylib
/opt/subversion/lib/libsvn_fs-1.0.dylib
/opt/subversion/lib/libsvn_subr-1.0.dylib
These don’t need to be for the Subversion you (or svnX) actually use as long as ‘Call Subversion libraries directly’ is subsequently unchecked.
Also check you have the correct read & exec privileges using something like:
ls -l /opt/subversion/lib/lib*-1.0.dylib
2. Try removing the symlinks that svnX uses to reach those libraries. These are:
svnX.app/Contents/Frameworks/libapr.dylib
svnX.app/Contents/Frameworks/libsvn_client.dylib
svnX.app/Contents/Frameworks/libsvn_fs.dylib
svnX.app/Contents/Frameworks/libsvn_subr.dylib
You can simply move them out of the folder (on to the Desktop for instance) and then try launching svnX.
Did either of these make a difference? Possibly only in the error message (but still important).
Thanks for the feedback.
CHRIS