Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!

Bug 366325

Summary: sys-fs/encfs is not compatible with dev-libs/boost-1.46.1
Product: Gentoo Linux Reporter: Albert W. Hopkins <marduk>
Component: New packagesAssignee: Gentoo Linux bug wranglers <bug-wranglers>
Status: RESOLVED INVALID    
Severity: normal    
Priority: Normal    
Version: unspecified   
Hardware: All   
OS: Linux   
Whiteboard:
Package list:
Runtime testing required: ---
Attachments: emerge --info

Description Albert W. Hopkins 2011-05-07 10:37:10 UTC
Created attachment 272363 [details]
emerge --info

Time to do the encfs/boost dance again:

configure:16691: x86_64-pc-linux-gnu-g++ -c -O2 -pipe -march=native -msse4.1  -I/usr/include/boost-1_46/include conftest.cpp >&5                                
conftest.cpp:28:30: fatal error: boost/version.hpp: No such file or directory  

This problem can be worked around with a symlink:

ln -s . /usr/include/boost-1_46

However, after this:

libtool: link: x86_64-pc-linux-gnu-g++ -shared -nostdlib /usr/lib/gcc/x86_64-pc-
linux-gnu/4.5.2/../../../../lib64/crti.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/
crtbeginS.o  .libs/readpassphrase.o .libs/base64.o .libs/ConfigReader.o .libs/Co
nfigVar.o .libs/Context.o .libs/Cipher.o .libs/CipherKey.o .libs/FileIO.o .libs/
RawFileIO.o .libs/BlockFileIO.o .libs/CipherFileIO.o .libs/MACFileIO.o .libs/Nam
eIO.o .libs/StreamNameIO.o .libs/BlockNameIO.o .libs/NullNameIO.o .libs/Interfac
e.o .libs/MemoryPool.o .libs/NullCipher.o .libs/DirNode.o .libs/FileNode.o .libs
/FileUtils.o .libs/openssl.o .libs/autosprintf.o .libs/SSL_Cipher.o   /usr/lib64
/librlog.so -lssl -lcrypto -ldl -lz -lboost_serialization-mt -lboost_filesystem-
mt -lboost_system-mt -L/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2 -L/usr/lib/gcc/x86
_64-pc-linux-gnu/4.5.2/../../../../lib64 -L/lib/../lib64 -L/usr/lib/../lib64 -L/
usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../../../x86_64-pc-linux-gnu/lib -L/usr
/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../.. -lstdc++ -lm -lc -lgcc_s /usr/lib/gc
c/x86_64-pc-linux-gnu/4.5.2/crtendS.o /usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../
../../../lib64/crtn.o  -march=native -msse4.1 -pthread -Wl,-O1 -Wl,--as-needed  
 -pthread -Wl,-soname -Wl,libencfs.so.6 -o .libs/libencfs.so.6.0.0
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../../../x86_64-pc-linux-gnu/bin/ld: c
annot find -lboost_serialization-mt
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_filesystem-mt
/usr/lib/gcc/x86_64-pc-linux-gnu/4.5.2/../../../../x86_64-pc-linux-gnu/bin/ld: cannot find -lboost_system-mt
collect2: ld returned 1 exit status

This can be fixed with a symlink too, however my fear is there is going to be a chain of these (fix one and another pops up).
Comment 1 Albert W. Hopkins 2011-05-07 10:53:02 UTC
And encfs requires >boost-1.34. And the 1.45* ebuilds were removed entirely.  Which basically means encfs is broken and people can't mount directories.
Comment 2 Albert W. Hopkins 2011-05-07 11:12:29 UTC
(In reply to comment #1)
> And encfs requires >boost-1.34. And the 1.45* ebuilds were removed entirely. 
> Which basically means encfs is broken and people can't mount directories.

Oops, take that back.  I tried to downgrade the 1.46 and it went to a much lower version, but i see that 1.42 is slotted and still available.

It looks like encfs will work with 1.42 slotted, but as it doesn't explicitly depend on the 1.42 slot "--depclean" will take it away, then revdep-rebuild will try to rebuild encfs but it fails to build with boost 1.46 (and 1.45 as well)

So the work-around is to keep boost 1.42 and not allow "--depclean" to take it away
Comment 3 Jeroen Roovers (RETIRED) gentoo-dev 2011-05-10 21:42:15 UTC
What does `eselect boost list' say?
Comment 4 Albert W. Hopkins 2011-05-10 22:44:09 UTC
This is completely my fault.  Either I had didn't know there was a boost module for eselect or I'd simply forgotten about it.  Nevertheless, yes I eselected 1.46 and then encfs built without any issues.

I regret turning bugzilla for what turned to be a support issue.  Thanks for the tip.