Discussion:
[MacPorts] #54939: osxfuse not building under High Sierra
MacPorts
2017-09-29 01:59:18 UTC
Permalink
#54939: osxfuse not building under High Sierra
----------------------+---------------------
Reporter: pmetzger | Owner:
Type: defect | Status: new
Priority: Normal | Milestone:
Component: ports | Version:
Keywords: | Port: osxfuse
----------------------+---------------------
osxfuse won't build under High Sierra. I get the following error near the
end of my main.log:

{{{
:info:build
/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,
9): Library not loaded: @rpath/libclang.dylib (LoadError)
:info:build Referenced from:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
:info:build Reason: image not found -
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
}}}

This is especially weird because the file
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle is
definitely there.

--
Ticket URL: <https://trac.macports.org/ticket/54939>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-09-29 12:02:49 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* keywords: => highsierra
* owner: => drkp
* status: new => assigned


Comment:

Yes, /System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle is
there. But, unlike on macOS Sierra, on High Sierra the
bridgesupportparser.bundle links with libclang.dylib, and that's what it
thinks doesn't exist ("Library not loaded: @rpath/libclang.dylib
(LoadError)"), at least not in whatever directory "@rpath" expands to in
this context. I see libclang.dylib in the following locations on High
Sierra:

*
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib
* /Applications/Xcode.app/Contents/Frameworks/libclang.dylib
* /Library/Developer/CommandLineTools/usr/lib/libclang.dylib

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:1>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-09-29 12:16:17 UTC
Permalink
#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):

What version of Xcode are you using? For High Sierra, you'll need at least
Xcode 9.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:2>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-09-29 17:36:49 UTC
Permalink
#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 pmetzger):

I'm on Xcode 9. Everything is fresh and up to date. Which isn't to say
that I might not be doing something else wrong.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:3>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-09-29 18:50:46 UTC
Permalink
#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
MacPorts
2017-09-29 20:20:33 UTC
Permalink
#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 pmetzger):

Looks hard to fix inside the MacPorts codebase, too. Thoughts?

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:5>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-06 04:48:39 UTC
Permalink
#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 hardwhack):

Workaround until this is settled according to link given above which in
turn links to:
https://github.com/amirrajan/rubymotion-applied/issues/18

Can fix/workaround using:

{{{
cd /Applications/Xcode.app/Contents/Developer/Toolchains
sudo ln -s XcodeDefault.xctoolchain OSX10.13.xctoolchain
}}}

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:9>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-14 15:59:01 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* cc: gavaza (added)


Comment:

Has duplicate #55093.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:11>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-14 17:46:01 UTC
Permalink
#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 kencu):

This is a minor macOS bug. The rpath in
`/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle` points
towards a non-existant path in the released version of Xcode 9, and there
is no copy of libclang.dylib in the default search paths `/usr/lib` and
`/usr/local/lib`

{{{
$ otool -l
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle | grep
-A2 LC_RPATH
cmd LC_RPATH
cmdsize 96
path
/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.13.xctoolchain/usr/lib
(offset 12)
}}}
but
{{{
$ cd /Applications/Xcode.app/Contents/Developer/Toolchains
$ ls
XcodeDefault.xctoolchain
}}}

You should be able to fix it by adding or replacing the rpath, like this
for exampe:
{{{
$ sudo install_name_tool -add_rpath
/Applications/Xcode.app/Contents/Frameworks/
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
}}}
but SIP, presumably, stops you:
{{{
error: install_name_tool: can't open input file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle for
writing (Operation not permitted)
error: install_name_tool: can't lseek to offset: 4096 in file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle for
writing (Bad file descriptor)
error: install_name_tool: can't write new headers in file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle (Bad
file descriptor)
error: install_name_tool: can't lseek to offset: 151552 in file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle for
writing (Bad file descriptor)
error: install_name_tool: can't write new headers in file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle (Bad
file descriptor)
error: install_name_tool: can't close written on input file:
/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle (Bad
file descriptor)
}}}

I thought that setting the fallback path might work:
{{{
post-patch {
system "export
DYLD_FALLBACK_LIBRARY_PATH=/Applications/Xcode.app/Contents/Frameworks/"
}
}}}
but it doesn't seem to, for some reason. That would be our main hope of
fixing in the current Portfile.

Making the symbolic link as noted above fixes the missing path, so it
works. SIP doesn't stop you from messing in the XCode directory.

I suspect this will be fixed in some soon-to-be-released macOS update.

Another method of making the libclang.dylib available without disabling
SIP is to symlink it into the default rpath search path:
{{{
sudo mkdir /usr/local/lib
sudo ln -s /Applications/Xcode.app/Contents/Frameworks/libclang.dylib
/usr/local/lib/libclang.dylib
}}}

I don't immediately see how to fix this in the Portfile, though.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-14 18:33:06 UTC
Permalink
#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 kencu):

Aha: any dynamic linker (dyld) environment variables, such as
DYLD_LIBRARY_PATH, are purged when launching protected processes.

<https://developer.apple.com/library/content/documentation/Security/Conceptual/System_Integrity_Protection_Guide/RuntimeProtections/RuntimeProtections.html>

That would be why setting the fallback doesn't work any more. The portfile
could make the symlink, build the port, and then delete the symlink I
guess. Or we can wait for Apple's no-doubt-upcoming fix, which is what I
assume we'll be doing :>

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:13>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-15 13:32:36 UTC
Permalink
#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 |
-----------------------+------------------------
Found a workaround until a real fix comes along. According to link given
https://github.com/amirrajan/rubymotion-applied/issues/18
{{{
cd /Applications/Xcode.app/Contents/Developer/Toolchains
sudo ln -s XcodeDefault.xctoolchain OSX10.13.xctoolchain
}}}
For what it is worth, I can confirm that this workaround has worked for
me. After installing osxfuse I was able to delete the symlink and I am
able to use the newly installed osxfuse. I hope that ensures things work
automatically when the issue has been fixed upstream. Thank you for
sharing.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:15>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-17 14:25:29 UTC
Permalink
#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 pmetzger):

Note that XCode 9.0.1 came out today, and the bug still seems to be there,
so we probably need to assume it may be a while before Apple fixes it. Is
there any possible workaround we can put into the Portfile on our own?

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:16>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-17 18:14:51 UTC
Permalink
#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 kencu):

Sure, it would be possible to make the symlink in the portfile in a `post-
extract` block maybe, build and install the port, and then perhaps delete
the symlink in a `post-destroot` block, but it's pretty hacky to do that.

Any reason not to just make the symlink
[ticket:54939#comment:9 as noted above] yourself, then build the port with
the portfile as it is? Anything else that uses
`/System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle` is
broken until that gets fixed anyway, not just this port...

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:17>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-10-17 18:33:24 UTC
Permalink
#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 pmetzger):

I've already built it myself. This isn't for my benefit as such. I don't
like leaving ports broken. But I assume that short of the symlink there's
no fix here, yes? And that doesn't seem like a good answer.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:18>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-11-14 15:14:34 UTC
Permalink
#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 basmac):

{{{
Causes others to fail
---> Computing dependencies for sshfs
---> Dependencies to be installed: osxfuse
---> Building osxfuse
Error: Failed to build osxfuse: command execution failed
}}}

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:23>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-11-30 17:32:30 UTC
Permalink
#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 |
-----------------------+------------------------
just to confirm, i did the symlink and it then build and installed.
Worked for me. Thanks.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:27>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-12-16 09:06:36 UTC
Permalink
#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 nbenm):

It worked for me too.[[BR]]
What will happen when the issue will be solved? I think I will not
remember to remove the symlink.[[BR]]
Thanks

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:29>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2017-12-21 12:28:52 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* cc: porchy13 (added)


Comment:

Has duplicate #55561.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:30>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-02-14 01:30:25 UTC
Permalink
#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 kencu):

has duplicate [ticket:55817]

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:34>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-02-25 02:14:59 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* cc: leondong (added)


Comment:

Has duplicate #55892.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:35>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-03-09 00:06:51 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* cc: LizardM4 (added)


Comment:

Has duplicate #55996.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:37>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-03-22 13:08:48 UTC
Permalink
#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 raimue):

Has duplicate #56118.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:38>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-03-22 15:38:09 UTC
Permalink
#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 kencu):

I assume there is a radar item for this bug. I would have guessed a fix to
be rolled out by this point, as there have been several Xcode updates
since this was identified.

--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:39>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-04-17 23:58:58 UTC
Permalink
#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 |
-----------------------+------------------------
Changes (by ryandesign):

* cc: willbprog127 (added)


Comment:

Has duplicate #56316.
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:42>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-05-05 12:02:33 UTC
Permalink
#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 TauSodan):

"""""""
PhaseScriptExecution BridgeSupport\ Metadata
build/OSXFUSE.build/Release/OSXFUSE.build/Script-
28D525C40EA8076400B7CF7B.sh
cd
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work
/osxfuse-osxfuse-431bdc5/framework
/bin/sh -c
/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_fuse_osxfuse/osxfuse/work
/osxfuse-osxfuse-
431bdc5/framework/build/OSXFUSE.build/Release/OSXFUSE.build/Script-
28D525C40EA8076400B7CF7B.sh
/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
"""""

This:

/Applications/Xcode.app/Contents/Developer/Toolchains/OSX10.13.xctoolchain/

Does not exist. The Toolchains directory only contains:

XcodeDefault.xctoolchain

The rest of that directory structure is the same.
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:43>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-05-07 16:13:51 UTC
Permalink
#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 pmetzger):

See: https://github.com/macports/macports-ports/pull/1749 which proposes a
workaround for this bug for the medium term, in the form of a slightly
hacky patch for the CI system and a message alerting users to the
workaround if they attempt to install osxfuse on the problematic macOS
versions.
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:44>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-06-27 16:50:09 UTC
Permalink
#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 kencu):

has duplicate [ticket:56744]
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:55>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-09-19 13:09:20 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------
Changes (by ryandesign):

* keywords: highsierra => highsierra mojave


Comment:

The second fix—the one added to the notes in
[b4e61d9f372b7ec38201038e15c6eb713482d7e6/macports-ports]—is needed on
macOS Mojave.
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:58>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-09-24 09:27:36 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------

Comment (by svalgaard):

After an upgrade to Xcode 10.0 building osxfuse failed - I tried all 3
fixes mentioned above.
**Rebooting** the mac made it work.

I used the fix mentioned by ryandesign above, i.e.,
{{{
mkdir -p /usr/local/lib/
sudo ln -s "$(xcode-select
-p)/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib"
/usr/local/lib/
}}}
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:59>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-10-06 16:21:40 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------

Comment (by ztalbot2000):

I came across the exact same error building with High Sierra, but the
workaround of "ln -s XcodeDefault.xctoolchain OSX10.13.xctoolchain" was
not enough. Like many developers I have multiple versions of Xcode
installed as Xcode7.3.1.app, Xcode8.3.3.app, Xcode9.4.1.app and
Xcode10.0.app. None of which are Xcode.app. xcode-select points to
Xcode9.4.1. \\

I also had to create the symbolic link of Xcode9.4.1..app -> Xcode.app for
osxfuse to build.\\

I'm just pointing this out in case others still have the issue.\\

John Talbot
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:60>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-10-08 01:21:53 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------

Comment (by ryandesign):

In [changeset:"2f27b9efd9e35826ea04c615281f5bfc653f3f49/macports-ports"
2f27b9efd9e35826ea04c615281f5bfc653f3f49/macports-ports] (master):
{{{
#!ConfigurableCommitTicketReference repository="macports-ports"
revision="2f27b9efd9e35826ea04c615281f5bfc653f3f49"
osxfuse: Apply gen_bridge_metadata workaround on Mojave

The problem still exists on Mojave, so include that in the check.

The problem will cause a build failure, so don't even try to build if
the workaround has not been performed.

Clean up the suggested workaround commands.

Move the detection of the problem from post-extract to pre-build since
that's where it's actually needed.

See: https://trac.macports.org/ticket/54939
}}}
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:62>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-12-06 05:34:11 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------

Comment (by ryandesign):

Since Apple still hasn't fixed it and it still affects High Sierra and
Mojave, I reported the bug to Apple as rdar://46511701. Looks like
yan12125 previously reported it as rdar://40649128.
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:64>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-12-06 05:50:40 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------
Post by MacPorts
Since Apple still hasn't fixed it and it still affects High Sierra and
Mojave, I reported the bug to Apple as rdar://46511701. Looks like
yan12125 previously reported it as rdar://40649128.

Yep, I've also copied the report to https://openradar.appspot.com/40649128
--
Ticket URL: <https://trac.macports.org/ticket/54939#comment:66>
MacPorts <https://www.macports.org/>
Ports system for macOS
MacPorts
2018-12-06 11:37:54 UTC
Permalink
#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 mojave
Port: osxfuse |
-----------------------+-------------------------------

Comment (by ryandesign):

In [changeset:"b66d28709bf066163009ac7160ed3bf90a27373e/macports-ports"
b66d28709bf066163009ac7160ed3bf90a27373e/macports-ports] (master):
{{{
#!ConfigurableCommitTicketReference repository="macports-ports"
revision="b66d28709bf066163009ac7160ed3bf90a27373e"
Travis: Generalize gen_bridge_metadata fix

Generalize the workaround for the broken gen_bridge_metadata /
bridgesupportparser.bundle since it affects both High Sierra and Mojave.

Decide when to apply the workaround not based on OS_MAJOR but based on
whether gen_bridge_metadata works or not.

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