configure: error: Linking to libboost_regex FAILED.
mgrep - A Multiline grep Implementation
Brought to you by:
lenardpi
I am running Arch Linux.
When configuring, I get the following error:
$ ./configure
checking for g++... g++
checking whether the C++ compiler works... yes
checking for C++ compiler default output file name... a.out
checking for suffix of executables...
checking whether we are cross compiling... no
checking for suffix of object files... o
checking whether we are using the GNU C++ compiler... yes
checking whether g++ accepts -g... yes
checking how to run the C++ preprocessor... g++ -E
checking for grep that handles long lines and -e... /usr/bin/grep
checking for egrep... /usr/bin/grep -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking iostream usability... yes
checking iostream presence... yes
checking for iostream... yes
checking boost/regex.hpp usability... no
checking boost/regex.hpp presence... no
checking for boost/regex.hpp... no
configure: Checking linking with libboost_regex...
configure: error: in `/home/maddin/user_programs/mgrep-1.1.2':
configure: error: Linking to libboost_regex FAILED.
See `config.log' for more details
config.log is attached.
The package boost-libs is installed on my system.
Anonymous
Diff:
Hi,
Based on the attached config.log, the header file regex.hpp was not found:
Could you please check if this file is present on your system? (For me, it resides at /usr/include/boost/regex.hpp.)
It can happen that the boost library was installed without regex support (ie. the regular expression handling part of boost library is missing). In this case Boost.Regex has to be installed as well.
Can you check the above?
Regards,
Istvan
Yes, that was the problem. The file is part of the boost-package in Arch. I could find that in this article. Thank you very much. It works now :)
Yep, this can be tricky sometimes. Great that it works, now. You're welcome, closing the ticket then.