#30537 closed defect (fixed)
sshfs: build fails with fuse4x when standalone MacFUSE installed
| Reported by: | tristan.klocke@… | Owned by: | drkp (Dan Ports) |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 2.0.0 |
| Keywords: | lion | Cc: | petri@… |
| Port: | sshfs fuse4x |
Description
I already reported this on a closed ticket but nobody noticed.
Building sshfs on Lion (10.7) results in an error. See the main.log. Seems to be connected to the recent changes in the dependencies for fuse4x.
Attachments (1)
Change History (9)
Changed 13 years ago by tristan.klocke@…
comment:1 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | dports@… added |
|---|---|
| Summary: | sshfs Mac OS X Lion build error → sshfs: build fails with fuse4x |
comment:2 Changed 13 years ago by ryandesign (Ryan Carsten Schmidt)
| Keywords: | lion added; sshfs fuse4x fuse removed |
|---|---|
| Port: | fuse4x added |
comment:3 Changed 13 years ago by drkp (Dan Ports)
It's suspicious that -D__FreeBSD__=10 appears in your cflags, and more suspicious that -I/usr/local/include/fuse does. Do you have a non-MacPorts installation of MacFUSE installed?
comment:4 follow-up: 5 Changed 13 years ago by tristan.klocke@…
Yeah, I thought this could happily coexist together ... Since TrueCrypt requires the old MacFuse I installed the latest Tuxera Release from http://groups.google.com/group/macfuse/browse_thread/thread/7d44fb2335c0dd99
There is so much confusion. I would be really glad if all fuse implementations change their dependencie to fuse4x.
comment:5 Changed 13 years ago by drkp (Dan Ports)
| Cc: | dports@… removed |
|---|---|
| Owner: | changed from macports-tickets@… to dports@… |
| Status: | new → assigned |
Replying to tristan.klocke@…:
Yeah, I thought this could happily coexist together ... Since TrueCrypt requires the old MacFuse I installed the latest Tuxera Release from http://groups.google.com/group/macfuse/browse_thread/thread/7d44fb2335c0dd99
I expected that they could. Actually, I'm surprised by this problem. I'm guessing MacFUSE has installed a pkgconfig file in /usr/local/lib/pkgconfig/fuse.pc, fuse4x has installed one into /opt/local/lib/pkgconfig/fuse.pc, and pkg-config is finding the former. I would have expected it to prefer the latter. I'll take a closer look later.
There is so much confusion. I would be really glad if all fuse implementations change their dependencie to fuse4x.
Yeah, the current situation is a mess. Unfortunately, it looks like it will get worse, given that Fuse4X is not the only fork of MacFUSE: there's also OSXFUSE.
comment:6 Changed 13 years ago by anatol (Anatol Pomozov)
Since TrueCrypt requires the old MacFuse I installed the latest Tuxera Release
I wish this ticket to be resolved #25914 So people can install TrueCrypt via macoprts and forget about installing macfuse/fuse4x via binary packages.
comment:7 Changed 13 years ago by drkp (Dan Ports)
| Resolution: | → fixed |
|---|---|
| Status: | assigned → closed |
| Summary: | sshfs: build fails with fuse4x → sshfs: build fails with fuse4x when standalone MacFUSE installed |
r81064 should fix this. There seems to be a similar problem with ntfs-3g too.
comment:8 Changed 13 years ago by drkp (Dan Ports)
| Cc: | petri@… added |
|---|
I fixed a similar issue with ntfs-3g in r81605. It looks like the other fuse filesystems work fine.
main.log