Open Source Telephony
 help / color / mirror / Atom feed
From: =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont <remi@remlab.net>
To: ofono@ofono.org
Subject: Re: ofono build error on ARM
Date: Sat, 01 Aug 2009 18:56:54 +0300	[thread overview]
Message-ID: <200908011856.54384.remi@remlab.net> (raw)
In-Reply-To: <1249139209.3491.1.camel@localhost.localdomain>

[-- Attachment #1: Type: text/plain, Size: 2075 bytes --]

Le samedi 1 août 2009 18:06:49 Marcel Holtmann, vous avez écrit :
> > > cc1: warnings being treated as errors
> > > netlink.c: In function ‘g_pn_nl_process’:
> > > netlink.c:75: error: cast increases required alignment of target type
> > > netlink.c:107: error: cast increases required alignment of target type
> > > netlink.c:109: error: cast increases required alignment of target type
> > > make[2]: *** [netlink.lo] Error 1
> >
> > I think there is no way to fix this. It comes from the Netlink packet
> > format and macros, which are confusing gcc. That's why I hate to enfore
> > -Werror.
>
> we only enforce -Werror for the developers and it is important to have
> gcc help us catch mistakes that might be easily overlooked.

If I recall correctly, `-Werror' is enforced when maintainer mode is enabled. 
Really, turning off maintainer mode is primilarly useful to binary package 
maintainers who *might* not want to trigger autotools updates. Then again, 
some might waht to have them anyway... I find the underlying assumption to be 
a bit restrictive if not flawed.

> I would have to look into these one and how we can fix them properly.

As far as I understand, those warnings come from casting receive buffers into 
structure with higher-order alignment requirement  - with some of your 
competitors' CPU architectures anyway ;) Arguably, those are caused by 
kernel/libc headers, not Ofono. I will check on Monday if we can fix them by 
promoting the receive buffers to larger integer types, but it might make the 
code worse.

But generally, there remain a problem that some warnings might simply be 
bogus, or not under our control. For instance -outside of Ofono- I'm yet to 
find a way around dummy variable "clobber warnings" when using POSIX thread 
cancellation cleanup handlers. Sure, I could make all variables volatile, but 
I refuse to damage optimizations for the sake of bogus warnings...

The real shame is that -Werror-* is dysfunctional in GCC :(

-- 
Rémi Denis-Courmont
http://www.remlab.net/


  reply	other threads:[~2009-08-01 15:56 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 15:13 ofono build error on ARM Andres Salomon
2009-07-31 15:30 ` Andres Salomon
2009-08-01  8:14 ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
2009-08-01 15:06   ` Marcel Holtmann
2009-08-01 15:56     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont [this message]
2009-08-03  7:48       ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200908011856.54384.remi@remlab.net \
    --to=remi@remlab.net \
    --cc=ofono@ofono.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox