Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Simon Marchi via Gdb-patches <gdb-patches@sourceware.org>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Subject: Re: [pushed] gdb: fix typos in configure
Date: Sat, 27 Nov 2021 19:35:30 -0500	[thread overview]
Message-ID: <606909fd-f3fe-4f42-790e-d36a0ec3124f@polymtl.ca> (raw)
In-Reply-To: <a1a4e653-8279-b088-2c05-432b1600dfd3@suse.de>

On 2021-11-27 15:35, Tom de Vries wrote:
> On 11/27/21 8:34 PM, Simon Marchi via Gdb-patches wrote:
>> The variable names used to restore CFLAGS and LDFLAGS here don't quite
>> match the names used above, resulting in losing the original CFLAGS and
>> LDFLAGS.  Fix that.
>>
> 
> Hi Simon,
> 
> thanks for fixing this mistake in my patch.
> 
> Trying to understand what I could have done to catch his, I tried
> shellcheck:
> ...
> $ shellcheck src/gdb/configure 2>&1 | grep -i save
>       save_CFLAGS=$CFLAGS
>       ^---------^ SC2034: save_CFLAGS appears unused. Verify use (or
> export if used externally).
>       save_LDFLAGS=$LDFLAGS
>       ^----------^ SC2034: save_LDFLAGS appears unused. Verify use (or
> export if used externally).
>       CFLAGS="$SAVE_CFLAGS"
>               ^----------^ SC2153: Possible misspelling: SAVE_CFLAGS may
> not be assigned, but save_CFLAGS is.
> ...
> and indeed the problem was found.
> 
> I'll try to use that next time I'll do a configure update.
> 
> Thanks,
> - Tom

I think shellcheck is great, but it's not so easy to use it on a
generated file that produces a ton of warnings already.

Simon

  reply	other threads:[~2021-11-28  0:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-11-27 19:34 Simon Marchi via Gdb-patches
2021-11-27 20:35 ` Tom de Vries via Gdb-patches
2021-11-28  0:35   ` Simon Marchi via Gdb-patches [this message]
2021-11-27 23:03 ` Andreas Schwab

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=606909fd-f3fe-4f42-790e-d36a0ec3124f@polymtl.ca \
    --to=gdb-patches@sourceware.org \
    --cc=simon.marchi@polymtl.ca \
    --cc=tdevries@suse.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