[MacPorts] #30383: fuse filesystems should support fuse4x as dependency
MacPorts
noreply at macports.org
Sun Jul 31 07:56:04 PDT 2011
#30383: fuse filesystems should support fuse4x as dependency
----------------------------------------------------------------------------------------------------------------------------------+
Reporter: dports@… | Owner: dports@…
Type: defect | Status: closed
Priority: Normal | Milestone:
Component: ports | Version: 2.0.0
Resolution: fixed | Keywords:
Port: bindfs curlftpfs encfs ext2fuse fuse-bindings-python fuse-bindings-python25 mhddfs mp3fs ntfs-3g procfs spotlightfs |
----------------------------------------------------------------------------------------------------------------------------------+
Comment(by anatol.pomozov@…):
Replying to [comment:15 tristan.klocke@…]:
> Tried to build with the new dependencies but it failed. Here is the
ticket and log:
https://trac.macports.org/attachment/ticket/30428/main.3.log
From the error message I see
{{{
:info:build Undefined symbols for architecture x86_64:
526 :info:build "_fuse_sem_destroy", referenced from:
527 :info:build _sshfs_read in sshfs-sshfs.o
528 :info:build _sshfs_release in sshfs-sshfs.o
529 :info:build _process_requests in sshfs-sshfs.o
530 :info:build _clean_req in sshfs-sshfs.o
531 :info:build _sshfs_read_end in sshfs-sshfs.o
532 :info:build _sftp_request_wait in sshfs-sshfs.o
533 :info:build _submit_read in sshfs-sshfs.o
534 :info:build ...
}}}
the compiler found function _fuse_sem_destroy defined in *macfuse*
headers, but it was not able to find it in the dylib.
I also see -D__FreeBSD__=10 which is absent in the fuse4x fuse4x.pc file.
This makes me think that the issue is you have headers and fuse.pc file
from macfuse, but dylib from fuse4x.
--
Ticket URL: <https://trac.macports.org/ticket/30383#comment:18>
MacPorts <http://www.macports.org/>
Ports system for Mac OS
More information about the macports-tickets
mailing list