On Sun, Feb 24, 2013 at 04:48:06AM +0100, Adam Borowski wrote: > > This bug is already fixed in the version in experimental. > > I'm afraid this is not true. Your changes fix unrelated problems (-flto > breakage on some architectures) but not the COMPILE_CHECK issue.
Oh, but upstream already changed the COMPILE_CHECK macros in 0.11. I tried them
out and they seemed to work without problems, but maybe I did something wrong?
> It's been long fixed in upstream trunk (commit 6c236b4), and I've just
> cherry-picked it into 0.11, but the last packaged point release (0.11.2)
> doesn't include the fix.
Ok then I did not correctly check whether this really fixed the issue. I guess
I didn't use gcc 4.8 after all.
> Since unstable still defaults to gcc-4.7, I don't think there's a reason
> to hurry, though. 0.12 will come in 1-2 months, and if per some chance
> wheezy gets released sooner, I can cut a 0.11.3.
>
> If you want to fix this now, please either take that commit, or enclose
> COMPILE_CHECK macros in tilepick.cc in a dummy function. Building with
> -std=c++11 would be another option (static_assert() goodness), but 0.11
> produces so many warnings about auto_ptr and %"PRId64 that let's not
> even bother.
Or just define _lint, so these COMPILE_CHECKS just go away?
--
Met vriendelijke groet / with kind regards,
Guus Sliepen <[email protected]>
signature.asc
Description: Digital signature
