Closed esabol closed 3 years ago
I've got same exception on Ubuntu 18.04
Configuration summary for gearmand version 1.1.19
* Installation prefix: /usr/local
* System type: pc-linux-gnu
* Host CPU: x86_64
* C Compiler: cc
* C Flags: -g -O2 -fstack-check -Wpragmas -Wunknown-pragmas -Wall -Wextra -Wunsuffixed-float-constants -Wjump-misses-init -Wno-attributes -Waddress
-Wvarargs -Warray-bounds -Wbad-function-cast -Wchar-subscripts -Wcomment -Wfloat-equal -Wformat-security -Wformat=2 -Wformat-y2k -Wlogical-op -Wmaybe-uninitialized -Wm
issing-field-initializers -Wmissing-noreturn -Wmissing-prototypes -Wnested-externs -Wnormalized=id -Woverride-init -Wpointer-arith -Wpointer-sign -Wredundant-decls -Wsh
adow -Wsign-compare -Wstrict-overflow=1 -Wswitch-enum -Wtrampolines -Wundef -funsafe-loop-optimizations -Wclobbered -Wunused -Wunused-result -Wunused-variable -Wunused-
parameter -Wunused-local-typedefs -Wwrite-strings -fwrapv -pipe -fPIE -pie -Wsizeof-pointer-memaccess -Wpacked -Werror
* C++ Compiler: c++
* C++ Flags: -D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC -g -O2 -fstack-check -Wpragmas -Wunknown-pragmas -Wall -Wextra -Wno-attributes -Wvarargs -Wa
ddress -Warray-bounds -Wchar-subscripts -Wcomment -Wctor-dtor-privacy -Wfloat-equal -Wformat=2 -Wformat-y2k -Wmaybe-uninitialized -Wmissing-field-initializers -Wlogical
-op -Wnon-virtual-dtor -Wnormalized=id -Woverloaded-virtual -Wpointer-arith -Wredundant-decls -Wshadow -Wsign-compare -Wstrict-overflow=1 -Wswitch-enum -Wtrampolines -W
undef -funsafe-loop-optimizations -Wc++11-compat -Wclobbered -Wunused -Wunused-result -Wunused-variable -Wunused-parameter -Wunused-local-typedefs -Wwrite-strings -Wfor
mat-security -fwrapv -pipe -fPIE -pie -Wsizeof-pointer-memaccess -Wpacked -Werror -std=c++0x
* CPP Flags: -fvisibility=hidden
* LIBS:
* LDFLAGS Flags: -Werror -rdynamic
* Assertions enabled: yes
* Debug enabled: no
* Warnings as failure: yes
* Building with hiredis yes
* Building with libsqlite3 yes
* Building with libdrizzle yes
* Building with libmemcached yes
* Building with libpq no
* Building with tokyocabinet no
* Building with libmysql yes
* SSL enabled: no
* wolfssl found: no
* openssl found: yes
* make -j: 5
* VCS checkout: yes
I googled /usr/include/boost/program_options/detail/value_semantic.hpp:184: undefined reference to
boost::program_options::validate` and found this:
https://stackoverflow.com/questions/39591067/undefined-reference-to-boostprogram-options-in-xubuntu
And this:
https://lists.boost.org/boost-users/2017/10/87969.php
Sounds like it’s not really a problem?
One of the stackoverflow.com answers said to try adding -D_GLIBCXX_USE_CXX11_ABI=0
to CXXFLAGS
. That didn't work for me.
I also tried -Wp,-D_GLIBCXX_USE_CXX11_ABI=0
. Same result.
I don’t think this is an issue. I’m going to close it unless someone comments that it should stay open.
I did a gcc/g++ build on Fedora 31 (GCC 9.2.1 20190827 Red Hat 9.2.1-1) with
CXXFLAGS='-D_GLIBCXX_DEBUG -D_GLIBCXX_DEBUG_PEDANTIC'
and the following errors popped up:Dockerfile to reproduce: