Boost Errors When I Try to Run make

[traverbrad]

I get the following errors when I try to run make:
/usr/include/boost/range/begin.hpp:49:24: error: ‘const struct boost::sub_match<__gnu_cxx::__normal_iterator<const char*, std::basic_string > >’ has no member named ‘begin’
/usr/include/boost/range/end.hpp:50:26: error: ‘const struct boost::sub_match<__gnu_cxx::__normal_iterator<const char*, std::basic_string > >’ has no member named ‘end’

The configure command I used is ./configure --with-boost-libdir=/usr/lib64

[cbaakman]

Hello! Could you tell me your boost version and xssp version?

[traverbrad]

I am trying to install XSSP 3.0.10. We have two Boost versions installed. 1.53 and 1.68.0.a. I've tried both of them and they both kick out the same error. This is on Red Hat 7.6

[cbaakman]

I tried with boost 1.68.0 and I was able to compile. So it's either one of these issues:

1. the compiler tries to combine the library files of one boost version with the headers of the other boost version. Try setting the configure script's --with-boost argument also, then run again from scratch.

OR

2. the boost you're building with is incorrectly built. Ask your administrator to remove both boost installation and install the latest version. Then run again from scrath.

[traverbrad]

When I add the --with-boost argument the configure script fails with the error: "configure: error: Could not find a version of the library!". Just before that it says "checking for boostlib >= 1.48... yes" and then "checking whether the Boost::Date_Time library is available... yes"

[cbaakman]

I meant that you should use the --with-boost argument like this:

./configure -- with-boost-libdir=PATH --with-boost=PATH

Did you provide a path with the argument?

[traverbrad]

I did. I've used both of those arguments and it still doesn't work. ./configure --with-boost=/cm/local/apps/boost/1.68.0.a --with-boost-libdir=/cm/local/apps/boost/1.68.0.a/lib64 CC=mpicc CXX=mpicxx
configure: error: Could not link against boost_filesystem !

[cbaakman]

Is the file "/cm/local/apps/boost/1.68.0.a/lib64/libboost_filesystem.so" present on your machine?
What about "/cm/local/apps/boost/1.68.0.a/lib64/libboost_filesystem.so.1.68.0.a" ?

Also, what is the message you get before "Could not link against ...". It should be something like: "checking whether the ... library is available"

[traverbrad]

It did find the filesystem library and it said it was available.

[cbaakman]

I think this is some kind of autoconf problem. I'll look into it when I have time. There must be some way to make this error go away. I'll let you know when I have a solution...

[cbaakman]

I've created a similar situation on my local machine

@traverbrad your two boost versions are conflicting and I think the second boost installation has partly overwritten the first one. Since you're not the administrator, the only solution is not to use either of the two boost installations. Instead, build your own boost in your home directory.

Download the latest boost source from: https://www.boost.org/users/download/ and extract the archive.
From the resulting directory, run ./bootstrap.sh, then ./b2, then ./b2 install --prefix=$HOME/boost
From the xssp directory, configure with ./configure --with-boost=$HOME/boost
This should dodge the conflicting boost installations.

If you still get linker errors, then use the '-L' flag on the compiler to specify the directory where you installed boost.

[mattiaperr]

hi cbaakman and travelbrad

I have the same error during the installation. How can I know how many version are there in my computer?

@cbaakman I tried with this procedure:

Download the latest boost source from: https://www.boost.org/users/download/ and extract the archive.
From the resulting directory, run ./bootstrap.sh, then ./b2, then ./b2 install --prefix=$HOME/boost
From the xssp directory, configure with ./configure --with-boost=$HOME/boost
This should dodge the conflicting boost installations.

but still returns error, where should i place the -L flag?

thank you

[cbaakman]

@garundula

In order to find out how many versions of boost are installed, you need to search your hard drive for boost library files with version numbers. Commands like 'locate' on linux can help.

If the makefile doesn't include the boost directory in your build path (with -L), then the easiest way is to edit your Makefile manually after running configure. Take care of the following things:

LDFLAGS should include all library directories:

LDFLAGS = $(BOOST_LDFLAGS) $(LIBBZ2_LDFLAGS) $(LIBZ_LDFLAGS)

CXXLINK and LINK should include LDFLAGS:

CXXLINK = ... $(LDFLAGS) ...
LINK = ... $(LDFLAGS) ...

Also, the build commands for mkhssp, mkdssp and hsspconv should include the $(CXXLINK)

I'll try to find a way to make autom4ke set this right automatically in the next version.