From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Subject: Re: gdb-cross-sdk hacking around gcc-4.3 warnings?
Date: Thu, 04 Dec 2008 21:33:51 +0100 [thread overview]
Message-ID: <gh9erh$10o$1@ger.gmane.org> (raw)
In-Reply-To: <20081204192759.GY16628@smtp.west.cox.net>
On 04-12-08 20:28, Tom Rini wrote:
> On Thu, Dec 04, 2008 at 06:06:03PM +0100, Koen Kooi wrote:
>> On 04-12-08 09:02, Tom Rini wrote:
>>> Hello, I see that in
>>> http://gitweb.openembedded.net/?p=openembedded.git;a=commit;h=6348b3baf7a61fc07626a3ecb29b539d438cfb4f
>>> we dropped -Werror from gdb-cross-sdk. Was this for gcc-4.3 support?
>>> If so, could we replace that by importing
>>> http://patches.ubuntu.com/g/gdb/extracted/gcc-4.3-build-error.patch
>>> instead? I'll do the work, just don't want to step on anyones toes if
>>> there was a different reason behind the change, thanks!
>> I'm not fond of enabling -Werror in crossbuilders, since simple,
>> harmless warnings will break your build.
>> If you are *completely* sure your patch removes *all* -Werror related
>> problems, then go ahead.
>
> Checked with an ARM and x86 build now, so yes, I'm pretty confident.
> Tangentally, what're a powerpc / avr32 target that should build (I'll fix
> db1200 / MIPS if that's broken, again) ?
Which arm? IIRC it broke on an armv7 build.
regards,
Koen
next prev parent reply other threads:[~2008-12-04 20:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-04 8:02 gdb-cross-sdk hacking around gcc-4.3 warnings? Tom Rini
2008-12-04 16:35 ` Khem Raj
2008-12-04 17:06 ` Koen Kooi
2008-12-04 19:28 ` Tom Rini
2008-12-04 19:45 ` Khem Raj
2008-12-04 20:33 ` Koen Kooi [this message]
2008-12-04 20:41 ` Tom Rini
2008-12-04 17:32 ` Koen Kooi
2008-12-04 19:25 ` Tom Rini
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='gh9erh$10o$1@ger.gmane.org' \
--to=k.kooi@student.utwente.nl \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.