public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: 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: Thu, 26 Oct 2023 14:58:40 +0300	[thread overview]
Message-ID: <838r7ph9xr.fsf@gnu.org> (raw)
In-Reply-To: <83cyxq29wf.fsf@gnu.org> (message from Eli Zaretskii on Sat, 07 Oct 2023 10:01:52 +0300)

> Date: Sat, 07 Oct 2023 10:01:52 +0300
> From: Eli Zaretskii <eliz@gnu.org>
> Cc: gdb-patches@sourceware.org, tom@tromey.com
> X-Spam-Status: No, score=0.6 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH,
>  DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, SPF_HELO_PASS, SPF_PASS,
>  TXREP autolearn=ham autolearn_force=no version=3.4.6
> 
> > From: Thiago Jung Bauermann <thiago.bauermann@linaro.org>
> > Cc: gdb-patches@sourceware.org, tom@tromey.com
> > Date: Thu, 05 Oct 2023 20:12:17 -0300
> > 
> > As a workaround, I was able to get away with some escaping:
> > 
> > $ ~/src/binutils-gdb/configure \
> >     --disable-{binutils,ld,gold,gas,sim,gprof,gprofng} \
> >     --with-auto-load-dir='foo\\\;bar\\\;baz' && make
> >     ⋮
> > checking for default auto-load directory... foo\\\;bar\\\;baz
> > checking for default auto-load safe-path... foo\\\;bar\\\;baz
> >     ⋮
> > $ grep AUTO_LOAD gdb/config.h
> > #define AUTO_LOAD_DIR "foo;bar;baz"
> > #define AUTO_LOAD_SAFE_PATH "foo;bar;baz"
> 
> Thanks, will use these in my next build, and see if it works for me as
> well.

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).

I've updated the Bugzilla bug with this information.

Thanks!

  reply	other threads:[~2023-10-26 11:58 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 [this message]
2023-10-26 23:48         ` Thiago Jung Bauermann
2023-10-27  5:59           ` Eli Zaretskii
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=838r7ph9xr.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).