mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Subject: Re: [ptxdist] problem compiling gdbserver and gdb with -Wcast-align
Date: Mon, 9 Sep 2013 11:38:49 +0200	[thread overview]
Message-ID: <20130909093849.GE31967@pengutronix.de> (raw)
In-Reply-To: <3c1ab5a6ffb2ef241d9666c0d473afcf@idefix.lespocky.dyndns.org>

On Wed, Sep 04, 2013 at 04:19:08PM +0200, Alexander Dahl wrote:
> at the moment we are using ptxdist 2013.07.1 with OSELAS toolchain
> 2012.12.1 for arm-v5te. We usually have set -Wcast-align in the extra
> toolchain options (TARGET_EXTRA_CFLAGS and the two for C++) to spot
> alignment problems in our code. Most software packages throw alignment
> warnings. Ignoring what this actually means, this is no problem as long
> as the package does not set -Werror. gdb sets -Werror. We tried most
> currently available versions of gdb and the build fails, e.g. like this:
> 
> /home/adahl/Work/bsp/XXX/platform-XXX/build-target/gdbserver-7.5/gdb/gdbserver/../common/agent.c:
> In function 'agent_look_up_symbols':
> /home/adahl/Work/bsp/XXX/platform-XXX/build-target/gdbserver-7.5/gdb/gdbserver/../common/agent.c:95:2:
> error: cast increases required alignment of target type
> [-Werror=cast-align]
> cc1: all warnings being treated as errors
> make[1]: *** [agent.o] Error 1
> 
> I guess one could dig into gdb sources, find and hopefully fix the
> problem, make a patch, send it to upstream and to ptxdist, wait, do all
> the usual things.
> 
> One could also drop the additional flag globally.
> 
> My question: is it possible to override the TARGET_EXTRA_CFLAGS per
> package? Maybe in rules/gdbserver.make? Or would this be a bad idea?
> 
> I'd like a quick solution where I don't have to dig into gdb source code
> and can keep the global target warnings. O:-)

An interesting problem. I think what you need is a -Wno-error=cast-align or
just -Wno-error. The problem is, that right now TARGET_EXTRA_CFLAGS are
added at the beginning of the command-line, so the -Werror from gdb will
overwrite it.
Maybe we can move the TARGET_EXTRA_CFLAGS to the end. I'm not sure if there
are any compiler flags, that must be specified at the beginning like some
of the linker flags?

Also, I think an (optional?) -Wno-error at the end would make sense.

Michael

-- 
Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

-- 
ptxdist mailing list
ptxdist@pengutronix.de

      parent reply	other threads:[~2013-09-09  9:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-09-04 14:19 Alexander Dahl
2013-09-04 18:38 ` Uwe Kleine-König
2013-09-05  7:19   ` Alexander Dahl
2013-09-09  9:38 ` Michael Olbrich [this message]

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=20130909093849.GE31967@pengutronix.de \
    --to=m.olbrich@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /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