#19206 closed defect (invalid)
subversion-1.6.0 linked against libgssapi?
Reported by: | macosforge.org@… | Owned by: | macports-tickets@… |
---|---|---|---|
Priority: | Normal | Milestone: | |
Component: | ports | Version: | 1.7.1 |
Keywords: | Cc: | ||
Port: |
Description
I am trying to build subversion-python25bindings but the result is unusable:
$ /opt/local/bin/python2.5 -c "import svn.core; print svn.core.SVN_VER_MINOR" Traceback (most recent call last): File "<string>", line 1, in <module> File "/opt/local/lib/svn-python/svn/core.py", line 19, in <module> File "/opt/local/lib/svn-python/libsvn/core.py", line 7, in <module> ImportError: dlopen(/opt/local/lib/svn-python2.5/libsvn/_core.so, 2): Library not loaded: /opt/local/lib/libgssapi.4.dylib Referenced from: /opt/local/lib/libsvn_client-1.0.dylib Reason: image not found
Indeed, according to otool, libgssapi is a dependency for libsvn_client:
$ otool -L /opt/local/lib/libsvn_client-1.0.dylib | grep libgssapi /opt/local/lib/libgssapi.4.dylib (compatibility version 5.0.0, current version 5.0.0)
This sounds to me like it may be a repeat of #12270.
Change History (5)
comment:1 follow-up: 2 Changed 16 years ago by danielluke (Daniel J. Luke)
comment:2 Changed 16 years ago by macosforge.org@…
Replying to dluke@…:
Can you run otool -L on libneon?
$ otool -L /opt/local/lib/libneon.dylib /opt/local/lib/libneon.dylib: /opt/local/lib/libneon.27.dylib (compatibility version 29.0.0, current version 29.4.0) /opt/local/lib/libintl.8.dylib (compatibility version 9.0.0, current version 9.2.0) /opt/local/lib/libiconv.2.dylib (compatibility version 7.0.0, current version 7.0.0) /usr/lib/libSystem.B.dylib (compatibility version 1.0.0, current version 111.1.3) /opt/local/lib/libssl.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /opt/local/lib/libcrypto.0.9.8.dylib (compatibility version 0.9.8, current version 0.9.8) /opt/local/lib/libz.1.dylib (compatibility version 1.0.0, current version 1.2.3) /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos (compatibility version 5.0.0, current version 5.0.0) /usr/lib/libresolv.9.dylib (compatibility version 1.0.0, current version 25.0.2) /opt/local/lib/libexpat.1.dylib (compatibility version 7.0.0, current version 7.2.0) /usr/lib/libgcc_s.1.dylib (compatibility version 1.0.0, current version 1.0.0)
If your libneon is/was linked against libgssapi.4.dylib (which appears to no longer be there) then you'll probably just need to re-build neon, subversion, and subversion-python25bindings.
I had already rebuilt these to see if this problem would go away, including rebuilding heimdal.
I'm not sure which port installs libgssapi.4.dylib (the neon configure change for issue #12270 was removed once the heimdal port's install location was moved to help prevent this kind of issue).
Here are the lib dependencies:
$ otool -L /opt/local/lib/lib*.dylib | grep -B 32 libgssapi | grep : /opt/local/lib/libstartup-notification-1.dylib: /opt/local/lib/libsvn_client-1.0.0.0.dylib: /opt/local/lib/libsvn_client-1.0.dylib: /opt/local/lib/libsvn_client-1.dylib: /opt/local/lib/libsvn_fs_util-1.dylib: /opt/local/lib/libsvn_ra-1.0.0.0.dylib: /opt/local/lib/libsvn_ra-1.0.dylib: /opt/local/lib/libsvn_ra-1.dylib: /opt/local/lib/libsvn_ra_neon-1.0.0.0.dylib: /opt/local/lib/libsvn_ra_neon-1.0.dylib: /opt/local/lib/libsvn_ra_neon-1.dylib:
comment:3 Changed 16 years ago by macosforge.org@…
False alarm. It turns out the old version of subversion was still installed, I had not properly forced the uninstall, after another port -f uninstall subversion; port instatll subversion the dependency is gone.
comment:4 Changed 16 years ago by danielluke (Daniel J. Luke)
Resolution: | → invalid |
---|---|
Status: | new → closed |
Can you run otool -L on libneon?
If your libneon is/was linked against libgssapi.4.dylib (which appears to no longer be there) then you'll probably just need to re-build neon, subversion, and subversion-python25bindings.
I'm not sure which port installs libgssapi.4.dylib (the neon configure change for issue #12270 was removed once the heimdal port's install location was moved to help prevent this kind of issue).