I got this post by email today, 11 days after it looks like it was
sent. Don't you subscribe to ligsigc-list? If you don't, your posts
can be severely delayed.
Your configure script contains errors. Did you use autogen.sh to
generate it? The lines that end "command not found" contain m4 macro
names. Those macros come from configure.ac. They should have been
expanded when the configure file was generated. They are defined in
libsigc++2/build/cxx.m4 and libsigc++2/build/cxx_std.m4. Did those
.m4 files exist when you generated configure?
Kjell
2014-07-03 15:58, Jonas Platte skrev:
Hi,
when I tried to compile libsigc++ with emscripten today (which
basically is compiling to LLVM bitcode with clang in my scenario)
I got an error I first thought would be emscripten-specific but
then I tried to compile it normally. Here are the error messages I
get:
I also get an
error message when running configure, this might be related:
[...]
checking pkg-config is at least version 0.9.0... yes
checking for libstdc documentation...
/usr/share/mm-common/doctags/libstdc++.tag@http://gcc.gnu.org/onlinedocs/libstdc++/latest-doxygen
../configure: line 16133:
SIGC_CXX_GCC_TEMPLATE_SPECIALIZATION_OPERATOR_OVERLOAD:
command not found
../configure: line 16134:
SIGC_CXX_MSVC_TEMPLATE_SPECIALIZATION_OPERATOR_OVERLOAD:
command not found
../configure: line 16135:
SIGC_CXX_SELF_REFERENCE_IN_MEMBER_INITIALIZATION: command not
found
../configure: line 16136: SIGC_CXX_HAS_NAMESPACE_STD: command
not found
../configure: line 16137: SIGC_CXX_HAS_SUN_REVERSE_ITERATOR:
command not found
checking which C++ compiler warning flags to use... -Wall
checking that generated files are newer than configure... done
configure: creating ./config.status
[...]
|
