[MacPorts] #54939: osxfuse @3.7.1: Library not loaded: @rpath/libclang.dylib (LoadError)

[MacPorts]

#54939: osxfuse @3.7.1: Library not loaded: @rpath/libclang.dylib (LoadError)
-----------------------+------------------------
  Reporter:  pmetzger  |      Owner:  drkp
      Type:  defect    |     Status:  assigned
  Priority:  Normal    |  Milestone:
 Component:  ports     |    Version:
Resolution:            |   Keywords:  highsierra
      Port:  osxfuse   |
-----------------------+------------------------

Comment (by ryandesign):

 I can confirm the problem on our buildbot worker:

 https://build.macports.org/builders/ports-10.13_x86_64-builder/builds/613/steps
 /install-port/logs/stdio

 Slightly different wording of the error:

 {{{
 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
 `require':
 dlopen(/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle,
 0x0009): required dylib '@rpath/libclang.dylib' not found, needed by
 '/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle'.  Did
 try: file not found
 '/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.13.xctoolchain/usr/lib/libclang.dylib',
 file not found '/usr/lib/libclang.dylib', file not found
 '/usr/local/lib/libclang.dylib' -
 /System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
 (LoadError)
         from
 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
         from
 /System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.rb:6:in `<top
 (required)>'
         from
 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
         from
 /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in
 `require'
         from /usr/bin/gen_bridge_metadata:65:in `<main>'
 Command /bin/sh failed with exit code 1
 }}}

 Here is the osxfuse bug report about this problem:

 https://github.com/osxfuse/osxfuse/issues/416

 Sounds like they are considering it a bug in macOS or Xcode.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:4>
MacPorts <https://www.macports.org/>
Ports system for macOS