Open Source Telephony
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: ofono@ofono.org
Subject: Re: ofono build error on ARM
Date: Sat, 01 Aug 2009 08:06:49 -0700	[thread overview]
Message-ID: <1249139209.3491.1.camel@localhost.localdomain> (raw)
In-Reply-To: <200908011114.15076.remi@remlab.net>

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

Hi Remi,

> > I'm seeing the following build error when building ofono on an HTC G1
> > phone:
> >
> > gcc -DHAVE_CONFIG_H -I. -I.. -I/usr/include/glib-2.0
> > -I/usr/lib/glib-2.0/include -g -O2 -g -Werror -Wextra
> > -Wno-unused-parameter -Wno-missing-field-initializers
> > -Wdeclaration-after-statement -Wmissing-declarations -Wredundant-decls
> > -Wcast-align -MT netlink.lo -MD -MP -MF .deps/netlink.Tpo -c netlink.c
> > -fPIC -DPIC -o .libs/netlink.o
> >
> > 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. I would have
to look into these one and how we can fix them properly.

Regards

Marcel



  reply	other threads:[~2009-08-01 15:06 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 [this message]
2009-08-01 15:56     ` =?unknown-8bit?q?R=C3=A9mi?= Denis-Courmont
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=1249139209.3491.1.camel@localhost.localdomain \
    --to=marcel@holtmann.org \
    --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