[MacPorts] #45521: osxfuse fails to load on Yosemite due to unsigned kext

[MacPorts]

#45521: osxfuse fails to load on Yosemite due to unsigned kext
---------------------------------+----------------------
  Reporter:  nicolas.stransky@…  |      Owner:  dports@…
      Type:  defect              |     Status:  closed
  Priority:  Normal              |  Milestone:
 Component:  ports               |    Version:  2.3.2
Resolution:  fixed               |   Keywords:  yosemite
      Port:  osxfuse             |
---------------------------------+----------------------

Comment (by fw@…):

 Replying to [comment:29 macosx12345@…]:
 > Replying to [comment:5 macports.org@…]:
 > > Meanwhile, I have used the following workaround:
 > >
 > > 1. Install the upstream (i.e. "official") ''osxfuse'' binary from
 https://osxfuse.github.io/ that corresponds to what MacPorts is using. At
 the time of this writing, it is 2.7.0.
 > > 2. In the shell, replace the MacPorts ''osxfuse'' with the signed
 binary:
 > > {{{
 > > $ cd /opt/local/Library/Filesystems
 > > $ sudo mv osxfusefs.fs osxfusefs.fs.macports
 > > $ sudo ln -s /Library/Filesystems/osxfusefs.fs osxfusefs.fs
 > > }}}
 > >
 > > Any port that has a dependency on
 /opt/local/Library/Filesystems/osxfusefs.fs/... should now work.
 >
 > Since an upgrade of osxfuse a couple of weeks ago, even under Mac OS
 10.6.8 I got the same error message when trying to load osxfuse
 (```/opt/local/Library/Filesystems/osxfusefs.fs/Support/osxfusefs.kext
 failed to load - (libkern/kext) not loadable (reason unspecified); check
 the system/kernel logs for errors or try kextutil(8). the OSXFUSE file
 system is not available (71)```). The workaround above solves the issue
 for me (with, at the time of this writing, the official 2.7.5 binary
 osxfuse and the port of osxfuse 2.7.5 installed). Thanks!
 >
 > Therefore, I suggest extending the solution adopted in r129493 to Mac OS
 10.6.

 It's certainly not exactly the same issue, since 10.6 has no kext signing
 requirement.  Perhaps there's something wrong with your build system that
 causes kexts to build incorrectly.  You don't mention using kextutil to
 see what OSX was complaining about.

-- 
Ticket URL: <https://trac.macports.org/ticket/45521#comment:31>
MacPorts <https://www.macports.org/>
Ports system for OS X