encfs not building

[js-macports@…]

There are 3 issues with encfs:

1.) If boost ist not built with +complete, the configure script won't even run (fails with the message that a packet whose name is an empty string was not found)

2.) If that is solved, it fails to build with this:

/opt/local/include/boost/serialization/serialization.hpp:140:   instantiated from 'void boost::serialization::serialize_adl(Archive&, T&, unsigned int) [with Archive = boost::archive::xml_iarchive, T = EncFSConfig]'
/opt/local/include/boost/archive/detail/iserializer.hpp:160:   instantiated from 'void boost::archive::detail::iserializer<Archive, T>::load_object_data(boost::archive::detail::basic_iarchive&, void*, unsigned int) const [with Archive = boost::archive::xml_iarchive, T = EncFSConfig]'
FileUtils.cpp:1521:   instantiated from here
FileUtils.cpp:163: error: 'make_binary_object' was not declared in this scope
make[2]: *** [FileUtils.lo] Error 1
make[1]: *** [all-recursive] Error 1
make: *** [all] Error 2

Easy to fix: Just add #include <boost/serialization/binary_object.hpp> to that file, it will build then.

3.) When it was built with these two workarounds, it fails when trying to start it due to missing symbols:

avalon:~$ encfs
dyld: lazy symbol binding failed: Symbol not found: __ZN5boost6system19get_system_categoryEv
  Referenced from: /opt/local/lib/libencfs.4.dylib
  Expected in: flat namespace

dyld: Symbol not found: __ZN5boost6system19get_system_categoryEv
  Referenced from: /opt/local/lib/libencfs.4.dylib
  Expected in: flat namespace

zsh: trace trap  encfs

Found no solution for the 3rd issue yet. Guess I'll have to look at the linking stage, something goes wrong there, I assume (missing library?)

[blb@…]

Assigning to maintainer.

The +complete issue appears to be mentioned as well in #15714.

[jlucg@…]

I have attached a new version of the Portfile with a few added patches that allow me to build and run encfs on my machine.

I have included in a new configuration option that allows to manually disable extended attribute support. You may want to feed this upstream to the encfs developer. I decided to compile without xattr support

(instead of fixing the header mismatch) after reading this post from

Amit Singh: ​http://www.mail-archive.com/macfuse-devel@googlegroups.com/msg01050.html

All seems to work OK for me. Please note that encfs 1.5.0 appears to have addressed the xattr issue: ​http://www.arg0.net/encfs

1.5.0 (September 7, 2008) Change Log [..,]

Bug fixes:

fixes for xattr calls on MacOS (issue 4 & 7)

[jlucg@…]

Updated Portfile and new patches

[jlucg@…]

Cc Me!

[web@…]

Cc Me!

[macsforever2000@…]

Are you still seeing this problem with the latest version of the port? It works fine for me now.

[macsforever2000@…]

Closing due to lack of response.

[anonymous]

Milestone Port Bugs deleted