[MacPorts] #25759: sshfs cannot find 'fuse' but 'macfuse' is installed
MacPorts
noreply at macports.org
Wed Oct 13 07:43:11 PDT 2010
#25759: sshfs cannot find 'fuse' but 'macfuse' is installed
-------------------------------+--------------------------------------------
Reporter: george@… | Owner: dports@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 1.9.1
Resolution: invalid | Keywords:
Port: sshfs |
-------------------------------+--------------------------------------------
Comment(by macosx12345@…):
Although my $prefix is the standard /opt/local, I had the problem too. The
first time I ran `port -vu install macfuse` (actually, I ran `port -vu
install sshfs` which triggered the installation of macfuse), it finished
the installation but then sshfs failed to install, claiming that fuse was
not installed. The contents of the macfuse port were the same as above (no
headers and libraries in $prefix/include and $prefix/lib and no fuse.pc
file).
Then I uninstalled macfuse (`port uninstall macfuse`) and reinstalled it
straight away (without any `port sync` in between) and the second time the
installation was complete.
Since I had run port in a screen session, I could look into the output of
the first `port install` command and I noticed that there were lots of
error messages like `../libtool: line 816: X--tag=CC: command not found`.
At the end this prevented the compilation of the library, but port kept
going with staging into destroot and installed the parts of the package
that go into /Liibrary/Filesystems.
I attach the outputs of the two runs of `port -vu install macfuse`: the
first one which "silently" failed and the second one which succeeded. HTH.
--
Ticket URL: <https://trac.macports.org/ticket/25759#comment:13>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list