Summary: | [asyncns] Gabble fails to build with pedantic gcc | ||
---|---|---|---|
Product: | Telepathy | Reporter: | Pierre-Luc Beaudoin <pierre-luc> |
Component: | gabble | Assignee: | Guillaume Desmottes <guillaume.desmottes> |
Status: | RESOLVED FIXED | QA Contact: | Telepathy bugs list <telepathy-bugs> |
Severity: | major | ||
Priority: | high | CC: | 84yelo3, biru.ionut, lennart |
Version: | unspecified | Keywords: | patch |
Hardware: | Other | ||
OS: | All | ||
URL: | http://git.collabora.co.uk/?p=user/cassidy/telepathy-gabble;a=shortlog;h=refs/heads/build | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Pierre-Luc Beaudoin
2009-09-03 06:26:09 UTC
You shouldn't use -Werror when building this. The code in asyncns.c breaks C99 strict aliasing ruless. (BTW, glib now has an async dns module that embedds libasyncns. Might be a good idea to port your code over to that instead of using libasyncns directly) http://git.collabora.co.uk/?p=user/cassidy/telepathy-gabble;a=shortlog;h=refs/heads/gibber-error removes ERROR_CFLAGS when building Gibber. I opened bug #23920 about the GResolver switch. I'd prefer to quickly fix this issue without having to block on it as I currently can't build Gabble. (In reply to comment #1) > You shouldn't use -Werror when building this. The code in asyncns.c breaks C99 > strict aliasing rules. Shouldn't it either not do that, or be documented as "must be compiled with -fno-strict-aliasing", given that AIUI the gcc warnings basically mean "I think I'm applying unsafe optimizations to your code"? (In reply to comment #4) > (In reply to comment #1) > > You shouldn't use -Werror when building this. The code in asyncns.c breaks C99 > > strict aliasing rules. > > Shouldn't it either not do that, or be documented as "must be compiled with > -fno-strict-aliasing", given that AIUI the gcc warnings basically mean "I think > I'm applying unsafe optimizations to your code"? Yes, of course, I should fix this. It is on my todo list already, just haven't found the time yet. I think the meaning of the warning is actually "I am not applying optimizations here because your code stinks", though... ;-) But tbh I neer really verified my interpretation of this. *** Bug 23567 has been marked as a duplicate of this bug. *** *** Bug 22413 has been marked as a duplicate of this bug. *** Guillaume, could you fix this, either by improving asyncns.c or by compiling it with -fno-strict-aliasing? Fixed in master. Will be in 0.9.0. Fixed in the 0.8 branch as well A small followup: Upstream libasyncns in git now compiles cleanly with -Wstrict-aliasing. Will release that as 0.8 shortly. |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.