Maybe useful:
Latest config & build logs (r13185) uploaded here: https://www.dropbox.com/sh/l25szbsju8ef4wu/9UFTW8z74y
gcc build fails (build log based on 'make -k') clang ok
On 2014-03-22 14:16 +0100, su_v wrote:
-Wno-error=self-assign
more errors:
../../src/libuemf/uwmf_endian.c:285:10: error: explicitly assigning a variable of type 'int' to itself [-Werror,-Wself-assign] ../../src/libuemf/uwmf_endian.c:310:10: error: explicitly assigning a variable of type 'int' to itself [-Werror,-Wself-assign] ../../src/libuemf/uwmf_endian.c:703:10: error: explicitly assigning a variable of type 'int' to itself [-Werror,-Wself-assign]
On 2014-03-22 13:25 +0100, Johan Engelen wrote:
With clang, can you try again without (after bzr up) -Wno-error=return-type -Wno-error=self-assign -Wno-error=parentheses-equality
Thanks, Johan
On 22-3-2014 12:42, su_v wrote:
On 2014-03-21 19:39 +0100, Johan Engelen wrote:
Hi all, I'd like people to check what compiler errors are reported for trunk on their system (Windows I can do myself), with these flags:
-Wall -Wformat -Werror=format-security -W -Wpointer-arith -Wcast-align -Wsign-compare -Woverloaded-virtual -Werror=switch -Werror=return-type -Werror -Wno-error=pointer-sign -Wno-error=unused-parameter -Wno-error=unused-but-set-variable -Wno-error=strict-overflow -Wno-error=write-strings -Wno-error=format -Wno-error=format-extra-args
Please no comments about whether you like these flags or not, just what build *errors* you get. (don't send me the warnings please!)
Attached are two diffs which allowed to compile successfully with:
- clang 3.1 (based on LLVM 3.1svn)
- GCC 4.2.1 (llvm-gcc-4.2)
(don't use both at the same time)
Notes:
clang diff was tested with dbus enabled, llvm-gcc-4.2 without.
cast-align warnings from boost headers are suppressed with #pragma
I failed to disable Werror for the warnings from lcms1 with
llvm-gcc-4.2, so the build was allowed to use lcms2 instead.
No tests have been run with experimental GTK3.
The warnings which had to be turned off have comments referring to the
files where the error occurred. If you need more detailed error logs, let me now.
- Ideally, the section in configure.ac would be converted into a loop so
that each flag gets tested individually whether the compiler supports it or not. I didn't spend time trying to figure out how to do that. For testing, those that fail can be individually commented out.