erreur de configuration: impossible d'établir un lien avec boost_system

Question

J'essaie d'installer un paquet (simulateur de football 2d) sur Debian. Lorsque je vais dans le répertoire et lance ./configure, j'obtiens les informations suivantes:

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

J'ai installé la bibliothèque boost, donc je ne sais pas quel est le problème.

Hadi Nahavandi · Accepted Answer

Sur une machine 64-bit basée sur Debian, la commande suivante a corrigé cette erreur pour moi:

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

oozie · Answer

Je pensais je l'avais installé mais

$ Sudo apt-get install libboost1.48-*

résolu le problème pour moi en installant les paquets boost manquants.

Luke · Answer

Sur un ordinateur 32 bits basé sur Debian, la commande suivante a corrigé cette erreur pour moi:

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

Sur un ordinateur 64 bits basé sur Debian, essayez la commande suivante:

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

Plus d'informations peuvent être trouvé ici.

danger89 · Answer

Dans mon cas, il me manquait quelques éléments de boost nécessaires. Essayez de vous exécuter sur 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

ALvin Das · Answer

Vérifiez ce post . J'ai eu le même problème. Je suis sur la machine 64 bits. Vous devez spécifier le chemin d'accès aux bibliothèques 64 bits. J'ai trouvé ce post qui résout le problème.

Malvineous · Answer

Je viens d'avoir ce problème et pour le bénéfice de quiconque, assurez-vous de regarder de près la sortie configure! Il y a un bogue dans les vérifications, donc si la bibliothèque Boost B est manquante, vous verrez ceci:

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

Notez que bien que le message d’erreur se plaint de A, la bibliothèque manquante est en fait B! Si vous installez la bibliothèque B, la vérification aboutira.

Nonny Moose · Answer

Pour que les téléspectateurs potentiels sachent, utilisez ./configure --with-boost-libdir=/usr/lib/arm-linux-gnueabihf sur les appareils armhf. Merci à @Hadi pour l'inspiration.

Ben Brammer · Answer

Aucun expert ici, mais mon $ 0,02:

Premièrement, Boost n’est que principalement une bibliothèque contenant uniquement des en-têtes. Pour certaines bibliothèques, vous devez créer et ajouter à votre chemin de bibliothèque; boost_system est l'une de ces bibliothèques.

Deuxièmement, il est facile de négliger le fait que vous pouvez créer les bibliothèques Boost en tant que bibliothèques statiques ou partagées. Si vous en avez construit une et essayez de la lier à une autre, cela pourrait expliquer votre problème.

./b2 runtime-link = shared créera partagé; ./b2 runtime-link = static construira des bibliothèques statiques.

J'espère que cela t'aides :)

user241199 · Answer

L'installation

libboost-system-dev
libboost-filesystem-dev
libboost-chrono-dev
libboost-programme-options-dev
libboost-test-dev
libboost-thread-dev
libboost-iostreams-dev

Correction du problème. Le rapport de ./configure est:

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