From: Eli Zaretskii <eliz@gnu.org>
To: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
Cc: gdb-patches@sourceware.org, tom@tromey.com
Subject: Re: [PATCH v2] gdb/configure.ac: Add option --with-additional-debug-dirs
Date: Fri, 27 Oct 2023 08:59:11 +0300 [thread overview]
Message-ID: <837cn8fvww.fsf@gnu.org> (raw)
In-Reply-To: <87sf5xrllh.fsf@linaro.org> (message from Thiago Jung Bauermann on Thu, 26 Oct 2023 20:48:58 -0300)
> From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> Cc: gdb-patches@sourceware.org, tom@tromey.com
> Date: Thu, 26 Oct 2023 20:48:58 -0300
>
> > FTR: just tried this with the gdb-14.0.91 pretest, and it works just
> > fine. Thank you very much for helping me avoid this annoying problem
> > (it previously required me to build GDB twice).
>
> Excellent! I poked at it some more today and I noticed two things:
>
> 1. We provide the definition of AC_DEFINE_DIR ourselves in
> gdb/acinclude.m4, so what I said earlier about the fix having to be
> in Autoconf was wrong. Too bad, it's always a relief when the blame
> lies somewhere else. :-)
>
> 2. We can do the escape trick above automatically in gdb/configure.ac.
>
> So I just sent a patch to do that:
>
> https://inbox.sourceware.org/gdb-patches/20231026234013.937210-1-thiago.bauermann@linaro.org/
Thanks, this is even better!
next prev parent reply other threads:[~2023-10-27 5:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-04 18:31 Thiago Jung Bauermann
2023-10-05 5:05 ` Eli Zaretskii
2023-10-05 23:12 ` Thiago Jung Bauermann
2023-10-07 7:01 ` Eli Zaretskii
2023-10-26 11:58 ` Eli Zaretskii
2023-10-26 23:48 ` Thiago Jung Bauermann
2023-10-27 5:59 ` Eli Zaretskii [this message]
2023-10-05 15:16 ` Tom Tromey
2023-10-06 2:03 ` Thiago Jung Bauermann
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=837cn8fvww.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=thiago.bauermann@linaro.org \
--cc=tom@tromey.com \
/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).