public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Tom Tromey <tom@tromey.com>
To: Tom de Vries <tdevries@suse.de>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] [gdb/build] Fix adding -DNDEBUG to python flags of release build
Date: Thu, 30 Nov 2023 12:26:11 -0700	[thread overview]
Message-ID: <874jh3cab0.fsf@tromey.com> (raw)
In-Reply-To: <20231130112128.9197-1-tdevries@suse.de> (Tom de Vries's message of "Thu, 30 Nov 2023 12:21:28 +0100")

>>>>> "Tom" == Tom de Vries <tdevries@suse.de> writes:

Tom> [ This was not obvious to me, but apparently evaluating an empty or undefined
Tom> variable in this context is similar to using ':' or 'true', so the line is
Tom> evaluated as:

TIL.

Tom> [ Unfortunately, the move might introduce issues similar to the one we're
Tom> fixing, and I'm not sure how to check for this.  Shellcheck doesn't detect
Tom> this type of problem.  FWIW, I did run shellcheck (using arguments -xa, in the
Tom> src/gdb directory to make sure ../bfd/development.sh is taken into account)
Tom> before and after and observed that the number of lines/words/chars in the
Tom> shellcheck output is identical. ]

I don't think there's a good way to figure this out.  It's one of the
problems with autoconf.

If we do discover an issue, we may have to split the macro in two; or
perhaps move more code into it.

Anyway I think this is ok.
Approved-By: Tom Tromey <tom@tromey.com>


Tom

  reply	other threads:[~2023-11-30 19:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-30 11:21 Tom de Vries
2023-11-30 19:26 ` Tom Tromey [this message]
2023-12-01  6:25   ` Tom de Vries
  -- strict thread matches above, loose matches on Subject: below --
2023-11-30 11:16 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=874jh3cab0.fsf@tromey.com \
    --to=tom@tromey.com \
    --cc=gdb-patches@sourceware.org \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).