From: Tom Tromey <tromey@adacore.com>
To: Tom Tromey <tromey@adacore.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] gnulib: import getline
Date: Tue, 04 May 2021 14:10:48 -0600 [thread overview]
Message-ID: <87a6pas1iv.fsf@tromey.com> (raw)
In-Reply-To: <YJGlQRWKMTZVMQUJ@vapier> (Mike Frysinger's message of "Tue, 4 May 2021 15:49:21 -0400")
Mike> this patch is required, but isn't sufficient, to fix this problem. i've been
Mike> hacking on it a bit. the sim hasn't used gnulib before, so still need to have
Mike> it integrate that dir.
Aha, right, thanks.
Mike> in the meantime, --disable-sim-hardware should fix the build by skipping the
Mike> new code that uses getline.
Thanks again. I understand this to mean that the getline use is in new
code and that if I use --disable-sim-hardware then I'm back to the
status quo ante, from before some of the recent changes? If so, that
should work for me.
Tom
next prev parent reply other threads:[~2021-05-04 20:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-01 22:09 Mike Frysinger via Gdb-patches
2021-05-02 0:39 ` Simon Marchi via Gdb-patches
2021-05-02 0:46 ` Mike Frysinger via Gdb-patches
2021-05-02 0:49 ` Simon Marchi via Gdb-patches
2021-05-02 4:50 ` Mike Frysinger via Gdb-patches
2021-05-04 15:03 ` Tom Tromey
2021-05-04 17:46 ` Mike Frysinger via Gdb-patches
2021-05-04 19:19 ` Tom Tromey
2021-05-04 19:49 ` Mike Frysinger via Gdb-patches
2021-05-04 20:10 ` Tom Tromey [this message]
2021-05-04 21:22 ` Mike Frysinger via Gdb-patches
2021-05-02 7:14 ` Eli Zaretskii via Gdb-patches
2021-05-02 14:14 ` Mike Frysinger via Gdb-patches
2021-05-02 14:48 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:12 ` Mike Frysinger via Gdb-patches
2021-05-02 15:24 ` Eli Zaretskii via Gdb-patches
2021-05-02 15:47 ` Mike Frysinger via Gdb-patches
2021-05-02 16:06 ` Eli Zaretskii via Gdb-patches
2021-05-02 16:12 ` Mike Frysinger via Gdb-patches
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=87a6pas1iv.fsf@tromey.com \
--to=tromey@adacore.com \
--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