配置错误：无法链接到 boost_system

Question

我正在尝试在 Debian 上安装一个软件包（足球模拟器 2d）。 当我转到目录并运行./configure ，我得到以下信息：

reza@debian:~/soccer/rcssserver-15.0.1$ ./configure
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 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 for style of include used by make... GNU
checking dependency style of g++... gcc3
checking for gawk... (cached) mawk
checking for gcc... gcc
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 how to run the C preprocessor... gcc -E
checking whether ln -s works... yes
checking whether make sets $(MAKE)... (cached) yes
checking for cos in -lm... yes
checking for deflate in -lz... no
checking whether the compiler implements namespaces... yes
checking whether the compiler has stringstream... yes
checking for grep that handles long lines and -e... /bin/grep
checking for egrep... /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 for working alloca.h... yes
checking for alloca... yes
checking for ANSI C header files... (cached) yes
checking arpa/inet.h usability... yes
checking arpa/inet.h presence... yes
checking for arpa/inet.h... yes
checking fcntl.h usability... yes
checking fcntl.h presence... yes
checking for fcntl.h... yes
checking for inttypes.h... (cached) yes
checking libintl.h usability... yes
checking libintl.h presence... yes
checking for libintl.h... yes
checking for libintl.h... (cached) yes
checking malloc.h usability... yes
checking malloc.h presence... yes
checking for malloc.h... yes
checking netdb.h usability... yes
checking netdb.h presence... yes
checking for netdb.h... yes
checking netinet/in.h usability... yes
checking netinet/in.h presence... yes
checking for netinet/in.h... yes
checking poll.h usability... yes
checking poll.h presence... yes
checking for poll.h... yes
checking pwd.h usability... yes
checking pwd.h presence... yes
checking for pwd.h... yes
checking stddef.h usability... yes
checking stddef.h presence... yes
checking for stddef.h... yes
checking for stdlib.h... (cached) yes
checking sys/param.h usability... yes
checking sys/param.h presence... yes
checking for sys/param.h... yes
checking sys/socket.h usability... yes
checking sys/socket.h presence... yes
checking for sys/socket.h... yes
checking sys/time.h usability... yes
checking sys/time.h presence... yes
checking for sys/time.h... yes
checking for sys/types.h... (cached) yes
checking for unistd.h... (cached) yes
checking for stdbool.h that conforms to C99... yes
checking for _Bool... yes
checking for an ANSI C-conforming const... yes
checking for inline... inline
checking for int16_t... yes
checking for int32_t... yes
checking for int8_t... yes
checking for size_t... yes
checking whether time.h and sys/time.h may both be included... yes
checking whether struct tm is in sys/time.h or time.h... time.h
checking for uint16_t... yes
checking for uint32_t... yes
checking for uint8_t... yes
checking for socklen_t... yes
checking for size_t... (cached) yes
checking for pid_t... yes
checking vfork.h usability... no
checking vfork.h presence... no
checking for vfork.h... no
checking for fork... yes
checking for vfork... yes
checking for working fork... yes
checking for working vfork... (cached) yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible malloc... yes
checking for stdlib.h... (cached) yes
checking for GNU libc compatible realloc... yes
checking return type of signal handlers... void
checking for strftime... yes
checking for memset... yes
checking for floor... yes
checking for gethostbyname... yes
checking for gettimeofday... yes
checking for inet_ntoa... yes
checking for memset... (cached) yes
checking for mkdir... yes
checking for pow... yes
checking for rint... yes
checking for socket... yes
checking for sqrt... yes
checking for strdup... yes
checking for strerror... yes
checking for flex... flex
checking lex output file root... lex.yy
checking lex library... -lfl
checking whether yytext is a pointer... yes
checking for a sed that does not truncate output... /bin/sed
checking if flex is the lexer generator... yes
checking for bison... bison -y
checking if bison is the parser generator... yes
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for a sed that does not truncate output... (cached) /bin/sed
checking for fgrep... /bin/grep -F
checking for ld used by gcc... /usr/bin/ld
checking if the linker (/usr/bin/ld) is GNU ld... yes
checking for BSD- or MS-compatible name lister (nm)... /usr/bin/nm -B
checking the name lister (/usr/bin/nm -B) interface... BSD nm
checking the maximum length of command line arguments... 1572864
checking whether the shell understands some XSI constructs... yes
checking whether the shell understands "+="... yes
checking for /usr/bin/ld option to reload object files... -r
checking for objdump... objdump
checking how to recognize dependent libraries... pass_all
checking for ar... ar
checking for strip... strip
checking for ranlib... ranlib
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for dlfcn.h... yes
checking whether we are using the GNU C++ compiler... (cached) yes
checking whether g++ accepts -g... (cached) yes
checking dependency style of g++... (cached) gcc3
checking how to run the C++ preprocessor... g++ -E
checking for objdir... .libs
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC -DPIC
checking if gcc PIC flag -fPIC -DPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking if gcc supports -c -o file.o... (cached) yes
checking whether the gcc linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... no
checking for ld used by g++... /usr/bin/ld -m elf_x86_64
checking if the linker (/usr/bin/ld -m elf_x86_64) is GNU ld... yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking for g++ option to produce PIC... -fPIC -DPIC
checking if g++ PIC flag -fPIC -DPIC works... yes
checking if g++ static flag -static works... yes
checking if g++ supports -c -o file.o... yes
checking if g++ supports -c -o file.o... (cached) yes
checking whether the g++ linker (/usr/bin/ld -m elf_x86_64) supports shared libraries... yes
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking for boostlib >= 1.32.0... yes
checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... no
configure: error: Could not link against boost_system 

我已经安装了boost库，所以我不知道是什么问题。

Answer 1

在基于 Debian 的64 位机器上，以下命令为我修复了这个错误：

  ./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu

Answer 2

我以为我已经安装了但是

$ sudo apt-get install libboost1.48-*

通过安装缺少的 boost 包为我解决了这个问题。

Answer 3

就我而言，我缺少一些必要的 boost 部分。 尝试在 Ubuntu/Debian 上执行：

sudo apt-get install libboost-system-dev libboost-filesystem-dev libboost-chrono-dev libboost-program-options-dev libboost-test-dev libboost-thread-dev libboost-iostreams-dev

Answer 4

在基于 Debian 的 32 位机器上，以下命令为我修复了这个错误：

./configure --with-boost-libdir=/usr/lib/i386-linux-gnu

在基于 Debian 的 64 位机器上，尝试以下命令：

./configure --with-boost-libdir=/usr/lib/x86_64-linux-gnu

更多信息可以在这里找到。

Answer 5

检查这个帖子。 我有同样的问题。 我在 64 位机器上。 您必须指定 64 位库的路径。 我发现这篇文章解决了这个问题。

Answer 6

我刚刚遇到了这个问题，为了其他人的利益，请确保您非常仔细地查看configure输出！ 检查中存在错误，因此如果缺少 Boost 库 B，您将看到：

checking whether the A library is available... yes
checking for exit in -lA... yes
checking whether the B library is available... no
configure: error: Could not link against A

请注意，虽然错误消息抱怨A ，但缺少的库实际上是B ！ 如果您安装库B则检查将成功。

Answer 7

只是为了让潜在的观众知道，在 armhf 设备上使用./configure --with-boost-libdir=/usr/lib/arm-linux-gnueabihf 。 感谢@Hadi 的启发。

Answer 8

安装

• libboost-system-dev
• libboost 文件系统开发
• libboost-chrono-dev
• libboost-program-options-dev
• libboost-test-dev
• libboost 线程开发
• libboost-iostreams-dev

修复了问题。 ./configure 的报告是：

checking whether the Boost::System library is available... yes
checking for exit in -lboost_system... yes
checking whether the Boost::Filesystem library is available... yes
checking for exit in -lboost_filesystem... yes
checking whether the Boost::IOStreams library is available... yes
checking for exit in -lboost_iostreams... yes
checking whether the Boost::Program_Options library is available... yes
checking for exit in -lboost_program_options... yes
checking whether the Boost::Regex library is available... yes
checking for exit in -lboost_regex... yes
checking whether the Boost::Thread library is available... yes
checking for exit in -lboost_thread... yes
checking whether the Boost::Unit_Test_Framework library is available... yes

Answer 9

install libboost-all-dev 

为我解决了这个问题。

Answer 10

这里没有专家，但我的 $.02：

首先，补偿仅大多仅头库。 对于某些库，您必须构建并添加到您的库路径中； boost_system 是这些库之一。

其次，很容易忽略这样一个事实，即您可以将 Boost 库构建为静态库或共享库，如果您已经构建了一个库并试图链接到另一个库，那么这可能会导致您的问题。

./b2 runtime-link=shared 将创建共享； ./b2 runtime-link=static 将构建静态库。

希望这可以帮助 ：）

Answer 11

我遇到了同样的问题，添加 --with-boost-libdir=XXX 不起作用，但是当我切换到 gcc v9.3 时，所有东西都被编译并链接了 boost 库。

检查您的 boost 库是用什么版本编译的并匹配编译器版本.. 可能会有所帮助。