[MacPorts] #44658: Encfs fails to mount after the recent upgrade
#44658: Encfs fails to mount after the recent upgrade -------------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.1 Keywords: encfs,boost | Port: encfs -------------------------+-------------------------------- OS X 10.9.4 Mavericks $ encfs /path /Volumes/path The directory "/Volumes/path" does not exist. Should it be created? (y,n) y dyld: lazy symbol binding failed: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib dyld: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib Trace/BPT trap: 5 $ -- Ticket URL: <https://trac.macports.org/ticket/44658> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: encfs,boost Port: encfs | -----------------------+-------------------------------- Comment (by kacnow@…): Replying to [ticket:44658 kacnow@…]: Rebuilding the package fixed it.
OS X 10.9.4 Mavericks
$ encfs /path /Volumes/path The directory "/Volumes/path" does not exist. Should it be created? (y,n) y dyld: lazy symbol binding failed: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib
dyld: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib
Trace/BPT trap: 5 $
-- Ticket URL: <https://trac.macports.org/ticket/44658#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: High | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: encfs,boost Port: encfs | -----------------------+-------------------------------- Comment (by ionic@…): He rebuilt `encfs`, after which it worked. `encfs` is missing a revbump due to the latest `boost` upgrade. Interestingly, `rev-upgrade` didn't catch that for some reason. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Changes (by ryandesign@…): * priority: High => Normal * keywords: encfs,boost => Old description:
OS X 10.9.4 Mavericks
$ encfs /path /Volumes/path The directory "/Volumes/path" does not exist. Should it be created? (y,n) y dyld: lazy symbol binding failed: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib
dyld: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib
Trace/BPT trap: 5 $
New description: OS X 10.9.4 Mavericks {{{ $ encfs /path /Volumes/path The directory "/Volumes/path" does not exist. Should it be created? (y,n) y dyld: lazy symbol binding failed: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib dyld: Symbol not found: __ZN5boost7archive6detail17shared_ptr_helperC2Ev Referenced from: /opt/local/lib/libencfs.6.dylib Expected in: /opt/local/lib/libboost_serialization-mt.dylib Trace/BPT trap: 5 $ }}} -- Comment: Hmm, did this just start after upgrading to boost 1.56.0? I wonder if ports using boost need to be rebuilt. You could try downgrading boost to 1.55.0, or rebuilding encfs (i.e. `sudo port -ns upgrade --force encfs`). -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by ryandesign@…): Oh, sorry, overlooked ionic's previous comment. rev-upgrade only catches library version changes. If the boost developers didn't change the library version (but should have), then it wouldn't catch that. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by urilabob@…): I'm not sure why, but rebuilding encfs didn't work for me (compilation errors) - see attached log. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by cal@…): That looks like you have fuse headers in `/usr/local`. Try this: {{{ sudo port clean encfs sudo port -nsft upgrade encfs }}} Note that you should not use `/usr/local` while using MacPorts because of problems like these. See wiki:FAQ#usrlocal. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by urilabob@…): Thank you, Cal, for your advice. As you say, I have osxfuse headers in both /usr and /opt. Unfortunately that doesn't seem to be the whole story. I tried {{{ sudo port clean encfs sudo port -nsftv install encfs }}} but got essentially the same errors (will attach the log file). I know it must be something to do with my configuration, as I upgraded my wife's machine to mavericks yesterday (same as mine) and installed Xcode (5.1.1, same as mine) and mavericks macports yesterday. On my wife's machine, encfs installed perfectly OK. But on mine, I continue to get these osxfuse-related errors. If you have any further ideas on what I could be doing wrong, I would really appreciate it. In particular, I'm wondering whether there could be some problem related to FUSE_USE_VERSION? -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by cal@…): Wait, do you actually have osxfuse headers in `/usr/include`? That would explain why trace mode doesn't fix the problem for you. If they are in `/usr/local/include`, the bad headers should have been hidden by trace mode (`-t`). Have you tried moving `/usr/local` aside for while? Also, if you have the headers in `/usr/include`, please revert that. `/usr/include` is Apple- land and you shouldn't have modified it. This isn't a source problem with encfs (as it was with the xtreemfs ticket you linked). The encfs code is compatible with this OS X-specific extension to fuse. encfs tries to assign a structure with 6 members (the last one OS X-specific) to a structure defined (by a bad and/or outdated header not installed by MacPorts) with 5 members, which causes the problem. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:9> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by urilabob@…): Thanks again Cal, the problem is solved for me - encfs compiled and is now running. I don't have osxfuse headers in /usr/include, but there are headers in /usr/local/include. Moving /usr/local aside temporarily allowed encfs to build properly (yay!!). However this means that trace mode didn't work properly, right? The usrlocal FAQ seems to suggest I should file a separate bug report, I presume against encfs, correct? -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:10> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by cal@…): Replying to [comment:10 urilabob@…]:
However this means that trace mode didn't work properly, right?
Yes. There are a number of reasons why trace mode might have failed in this case, such as symlinks from outside `/usr/local` into `/usr/local`. I'd have to see the log of a failed build with trace mode debugging enabled – however that requires manually recompiling the trace library, so I'm not sure it's worth the effort. Let me know if you want to attempt that and I'll give you instructions on how to do that. -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:11> MacPorts <http://www.macports.org/> Ports system for OS X
#44658: Encfs fails to mount after the recent upgrade -----------------------+-------------------------------- Reporter: kacnow@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.3.1 Resolution: | Keywords: Port: encfs | -----------------------+-------------------------------- Comment (by urilabob@…): Thank you again Cal. It sounds like the reason for trace not working is likely to be something specific to my system, and therefore not of wider value. This is a quite old system, originally installed under OSX 10.1, and then migrated a number of times over versions of OSX, over versions of XCode/Developer, and over hardware. For quite a while it had fink installed, before I decided to switch to macports. So there are many reasons why it might be slightly nonstandard, have leftover symlinks etc. I now know that if trace mode fails, I should move /usr/local out of the way temporarily - and anyone googling this discussion knows it too. So overall, I agree it's probably not worth the effort to debug. Thanks and Best Wishes Bob -- Ticket URL: <https://trac.macports.org/ticket/44658#comment:12> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts