Note that there are some explanatory texts on larger screens.

plurals
  1. POWhy autoconf isn't detecting boost properly?
    primarykey
    data
    text
    <p>I am using autoconf to detect boost libraries, with the support of the <a href="http://www.gnu.org/software/autoconf-archive/ax_boost_base.html" rel="noreferrer">autoconf-archive macros</a> and they work fine with system-wide boost libraries, but fail if I manually compile boost in my home directory:</p> <pre><code>sb@stephane:~/devel/spectra2$ ./configure --with-boost=/home/sb/local/ checking for a BSD-compatible install... /usr/bin/install -c checking whether build environment is sane... yes checking for a thread-safe mkdir -p... /bin/mkdir -p checking for gawk... no checking for mawk... mawk checking whether make sets $(MAKE)... yes checking build system type... i686-pc-linux-gnu checking host system type... i686-pc-linux-gnu checking for style of include used by make... GNU checking for gcc... gcc checking for C compiler default output file name... a.out checking whether the C compiler works... yes checking whether we are cross compiling... no checking for suffix of executables... checking for suffix of object files... o checking whether we are using the GNU C compiler... yes checking whether gcc accepts -g... yes checking for gcc option to accept ISO C89... none needed checking dependency style of gcc... gcc3 checking for library containing strerror... none required checking for g++... g++ checking whether we are using the GNU C++ compiler... yes checking whether g++ accepts -g... yes checking dependency style of g++... gcc3 checking for boostlib &gt;= 1.31.0... yes checking whether the Boost::Program_Options library is available... yes checking for exit in -lboost_program_options... yes checking whether the Boost::Filesystem library is available... yes checking for exit in -lboost_filesystem... no checking for exit in -lboost_filesystem... (cached) no checking for exit in -lboost_filesystem... (cached) no configure: error: Could not link against boost_filesystem ! </code></pre> <p>As you can see, it detects some libraries fine, but it fails with boost-filesystem. These are the contents of ~/local/lib:</p> <pre><code>sb@stephane:~$ ls -1 /home/sb/local/lib/ libboost_filesystem.a libboost_filesystem.so libboost_filesystem.so.1.42.0 libboost_program_options.a libboost_program_options.so libboost_program_options.so.1.42.0 libboost_system.a libboost_system.so libboost_system.so.1.42.0 libboost_thread.a libboost_thread.so libboost_thread.so.1.42.0 </code></pre> <p>So the library is there. I tried with both boost-1.39 and boost-1.42 with no different result, any idea why is this happening? Did I forget about something?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload