About the build directory: I don't know if 'build' is the best possible
name for that directory. Other packages, e.g. glibmm and gtkmm, also
have build directories with m4 files. I don't think it's meant for
out-of-tree-builds.
About the compilation errors: The results of some configure checks are
strange.
checking if C++ compiler supports the use of a particular specialization when
calling operator() template methods.... no
checking if C++ compiler supports the use of a particular specialization when
calling operator() template methods omitting the template keyword.... no
checking if C++ compiler allows usage of member function in initialization of
static member field.... yes
checking whether C++ library symbols are declared in namespace std... no
checking for non-standard Sun libCstd reverse_iterator... no
The first two 'no' here results in SIGC_WORKAROUND_OPERATOR_PARENTHESES
being defined as sun_forte_workaround, which is probably wrong.
The 'no' in the fourth line, testing whether C++ library symbols are
declared in namespace std, is not reasonable. That's an obsolete test,
which has long been unnecessary. Even half-modern C++ standard libraries
have their symbols declared in namespace std. Something is wrong here,
but I don't know exactly what's wrong. Reasonable results are 'yes' on
at least one of the first two tests, and on the fourth test.
Kjell
2014-07-14 14:55, Jonas Platte skrev:
About the email being sent late: I am subscribed but it seems it had
to be accepted by the moderator because it was a bit big because of
the terminal output I pasted.
About the m4 files: I started the build in an empty build directory
because that's what I did with emscripten too (only there I had a
different directory and here I just emptied build). It seems this
really was the problem because when copying the two .m4 files from the
build directory of the tarball the native build works. But shouldn't
m4 macros be in a seperate directory that is used no matter which
directory you use for an out-of-tree-build / if you don't do an
out-of-tree-build at all?
Also, when I copy those two files to the emscripten build directory
and rerun configure, that works. But make still fails after that. Here
is the output, this time not in the mail itself...
http://pastie.org/private/sanrhzyff9u6dxpfinpwg
_______________________________________________
libsigc-list mailing list
libsigc-list@gnome.org
https://mail.gnome.org/mailman/listinfo/libsigc-list
