Opened 6 years ago

Closed 6 years ago

Last modified 6 years ago

#57126 closed defect (fixed)

osxfuse update to 3.8.2 fails

Reported by: dershow Owned by: drkp (Dan Ports)
Priority: Normal Milestone:
Component: ports Version:
Keywords: Cc: yan12125 (Chih-Hsuan Yen), michaellass (Michael Lass)
Port: osxfuse

Description (last modified by mf2k (Frank Schima))

I have OSXFuse 3.8.0 installed and tried to upgrade to 3.8.2. But, the upgrade fails. During the build it does explain:

--->  Extracting osxfuse
If building this port fails, consider applying the following workaround:

    cd /usr/local/lib
    sudo ln -s $(xcode-select -p)/Toolchains/XcodeDefault.xctoolchain/usr/lib/libclang.dylib

See https://trac.macports.org/ticket/54939 for more information.

So, I tried that, but, it still failed. Thus, it seems to be a different issue from this one #54939 I've attached the build log.

Attachments (1)

main.log (694.8 KB) - added by dershow 6 years ago.

Download all attachments as: .zip

Change History (11)

Changed 6 years ago by dershow

Attachment: main.log added

comment:1 Changed 6 years ago by mf2k (Frank Schima)

Cc: dports@… removed
Description: modified (diff)
Owner: set to drkp
Status: newassigned

comment:2 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)

@dershow: Could you run gen_bridge_metadata --version and paste the output?

comment:3 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)

Cc: yan12125 added

comment:4 Changed 6 years ago by dershow

$ gen_bridge_metadata --version
/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)
  Referenced from: /System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
  Reason: image not found - /System/Library/BridgeSupport/ruby-2.3/bridgesupportparser.bundle
	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>'
Last edited 6 years ago by ryandesign (Ryan Carsten Schmidt) (previous) (diff)

comment:5 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)

I'm afraid it might be inevitable to skip gen_bridge_metadata to make osxfuse build on High Sierra...

Here's a proof-of-concept: https://github.com/yan12125/macports-ports/commit/4ca380c85cdfea2d40f79b585e194ee8ff90ace0

comment:6 in reply to:  5 Changed 6 years ago by michaellass (Michael Lass)

Replying to yan12125:

I'm afraid it might be inevitable to skip gen_bridge_metadata to make osxfuse build on High Sierra...

For me, building osxfuse @3.8.2_0 worked on MacOS 10.13.6 using the work-around that was proposed in earlier versions, i.e.

cd $(xcode-select -p)/Toolchains
sudo ln -s XcodeDefault.xctoolchain OSX10.13.xctoolchain

I did not apply the newer workaround since it was not necessary.

$ xcodebuild -version
Xcode 9.4.1
Build version 9F2000
$ gen_bridge_metadata --version
1.0

Any further information I can provide to help with this?

(Edited the output of gen_bridge_metadata because it was run in the wrong environment and therefore used a different ruby version).

Last edited 6 years ago by michaellass (Michael Lass) (previous) (diff)

comment:7 Changed 6 years ago by michaellass (Michael Lass)

Cc: michaellass added

comment:8 Changed 6 years ago by dershow

I just tried the older work-around, as @yan12125 suggested, and that also does work for me. Also, after doing that I do see:

$ gen_bridge_metadata --version 
1.0

comment:9 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)

Thanks for testing! I've added the original workaround back in https://github.com/macports/macports-ports/pull/2571

comment:10 Changed 6 years ago by yan12125 (Chih-Hsuan Yen)

Resolution: fixed
Status: assignedclosed

In 8fc6dead76cf1b9581a83f708f76522a7ba95837/macports-ports (master):

osxfuse: add the old workaround back

As reported in #57126#comment:8, the
original workaround works in some cases.

Closes: #57126

Note: See TracTickets for help on using tickets.