From: Tom de Vries <tdevries@suse.de>
To: "gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: gdb build broken in sim with -Wall -Werror
Date: Mon, 17 May 2021 17:39:13 +0200 [thread overview]
Message-ID: <a5864fd6-3d1c-aa4d-313c-ab1e2c1fa643@suse.de> (raw)
In-Reply-To: <YKKFjmDMsrUg3Swf@vapier>
On 5/17/21 5:02 PM, Mike Frysinger wrote:
> On 17 May 2021 09:02, Tom de Vries wrote:
>> this morning I tried to rebuild gdb from trunk @ f4fdd84587e (with
>> --enable-werror and CFLAGS="-O0 -g -Wall", as usual)
>
> the build will add appropriate warning flags for you. you shouldn't be
> forcing your own set into the mix.
>
True. This configuration did build before though, so it actually seems
to work quite well.
>> and ran into build errors in sim.
>>
>> Specifically:
>
> these snippets are much too truncated to be actionable.
I'll send you the build log off-list.
Thanks,
- Tom
next prev parent reply other threads:[~2021-05-17 15:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-17 7:02 Tom de Vries
2021-05-17 15:02 ` Mike Frysinger via Gdb-patches
2021-05-17 15:39 ` Tom de Vries [this message]
2021-05-17 15:39 ` Tom de Vries
2021-05-18 15:12 ` Mike Frysinger via Gdb-patches
2021-05-18 15:26 ` Tom de Vries
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=a5864fd6-3d1c-aa4d-313c-ab1e2c1fa643@suse.de \
--to=tdevries@suse.de \
--cc=gdb-patches@sourceware.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