Date: Sat, 22 Jun 2013 03:30:16 -0400 From: Rob Clark <rpclark@tds.net> To: vd@FreeBSD.org Cc: freebsd-ports@freebsd.org Subject: hugin, libboost_thread.so not found Message-ID: <20130622033016.72bad862.rpclark@tds.net>
next in thread | raw e-mail | index | archive | help
Cannot get hugin to work, I get the following: $ hugin /libexec/ld-elf.so.1: Shared object "libboost_thread.so"not found, required by "hugin" $ The only reference I could find close to this libboost_thread.so issue is on Greg Lehey's diary website, http://www.lemis.com/grog/diary-jul2012.php?topics=c. Greg states, "There are 9 libraries in that directory, and (not surprisingly) hugin requires them all: ... ldd /dereel/usr/local/bin/hugin /dereel/usr/local/bin/hugin: libhuginbase.so.0.0 => not found (0) libboost_thread.so => not found (0) (etc) With some experimentation, discovered that ldconfig didn't like the names, in particular the .0.0 at the end. Change the name and it discovers them: === root@eureka (/dev/pts/13) /home/grog 11 -> ln /dereel/usr/local/lib/hugin//libhuginbase.so.0.0 /dereel/usr/local/lib/hugin/libhuginbase.so.0 === root@eureka (/dev/pts/13) /home/grog 12 -> ldconfig -32 -r /var/run/ld-elf32.so.hints: search directories: /dereel/usr/local/lib/hugin/ 0:-lhuginbase.0 => /dereel/usr/local/lib/hugin//libhuginbase.so.0 But that doesn't help, because the executable is still looking for the version with .0.0 at the end. Is this a bug or a feature? It's certainly a pain." I think Greg's objective was more pointed at 64 bit compatibility. Mine on the other hand is just getting hugin to work in my 32bit environment. My system: FreeBSD 8.3-STABLE #1: Wed May 30 20:15:48 EDT 2012, i386, with fluxbox window manager. It appears I have the same 9 files referenced by Greg for hugin. # cd /usr/local/lib/hugin/ # ls libceleste.so.0.0 libhuginvigraimpex.so.0.0 libflann_cpp.so libicpfindlib.so.0.0 libhuginbase.so.0.0 liblocalfeatures.so.0.0 libhuginbasewx.so.0.0 libmakefilelib.so.0.0 libhuginlines.so.0.0 Is hugin port broken, or is there possibly a fix for this that I have missed? Any help appreciated. Thank you, Rob -------------------------- Rob Clark <rpclark@tds.net>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20130622033016.72bad862.rpclark>