Boost, libboost, g++

Issues related to applications and software problems
Post Reply
andt88
Posts: 6
Joined: 2016/11/28 14:24:35

Boost, libboost, g++

Post by andt88 » 2017/12/13 10:13:51

I am trying to install the program my_mead_2.3.4 on my CentOS system.
I run ./configure --prefix=`pwd` --boostdir=/usr

and then make where I get these errors:

g++: error: /usr/lib64/lib/libboost_regex.a: No such file or directory
g++: error: /usr/lib64/lib/libboost_filesystem.a: No such file or directory
g++: error: /usr/lib64/lib/libboost_system.a: No such file or directory
g++: error: /usr/lib64/lib/libboost_serialization.a: No such file or directory


I ran yum install boost-devel, but still these files are missing.

I am new to Linux and CentOS, could you please tell me what to do here? Let me know if I should provide any additional Info.

User avatar
TrevorH
Site Admin
Posts: 33202
Joined: 2009/09/24 10:40:56
Location: Brighton, UK

Re: Boost, libboost, g++

Post by TrevorH » 2017/12/13 11:29:48

yum provides '*/libboost_regex.a' shows the first of those files is part of boost-static though in a slightly different path.
The future appears to be RHEL or Debian. I think I'm going Debian.
Info for USB installs on http://wiki.centos.org/HowTos/InstallFromUSBkey
CentOS 5 and 6 are deadest, do not use them.
Use the FAQ Luke

andt88
Posts: 6
Joined: 2016/11/28 14:24:35

Re: Boost, libboost, g++

Post by andt88 » 2017/12/13 11:49:52

thanks! I found the files that are missing, they are all in /usr/lib64. How can I tell g++ to look for the files in this directory when running make?

pjsr2
Posts: 614
Joined: 2014/03/27 20:11:07

Re: Boost, libboost, g++

Post by pjsr2 » 2017/12/13 14:52:32

To add a directory to the list of directories to search for a library, you would add the option

Code: Select all

-L/usr/lib64
to the compiler/linker options. However, this directory is in the default list of directories to search, so there is something else wrong when g++ isn't finding it there. "/usr/lib64/lib" is a weird name. Having a subdirectory lib in /usr/lib64 is not normal. Why is the configure script producing this directory name?

Post Reply