From: Joel Brobecker <brobecker@adacore.com>
To: Mike Frysinger <vapier@gentoo.org>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] sim: erc32: fix linking against local readline on modern (ncurses) systems
Date: Sat, 31 Dec 2011 03:39:00 -0000 [thread overview]
Message-ID: <20111231033651.GB13974@adacore.com> (raw)
In-Reply-To: <CAJaTeTqguQX877CVXz3D=0=10CF2t8OODTEYMt1awCSC09RJXQ@mail.gmail.com>
> i hadn't noticed GDB had a test for it. i'm fine with keeping the two
> in sync.
If that works for your case, let's go with that as a first step
(because we can fix it now - see below).
> maybe extract the termcap m4 code out of gdb and put into a new m4
> file in the top level config/ dir ? that way we'd know the two trees
> would stay in sync.
Sounds like a fine idea to me. The extra complication is that I think
the config/ directory is "owned" by gcc. It should not be a problem,
but you'll have to go through them first.
Thanks,
--
Joel
next prev parent reply other threads:[~2011-12-31 3:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 10:19 Mike Frysinger
2011-12-30 10:39 ` Joel Brobecker
2011-12-31 2:57 ` Mike Frysinger
2011-12-31 3:39 ` Joel Brobecker [this message]
2011-12-31 7:27 ` Mike Frysinger
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=20111231033651.GB13974@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=vapier@gentoo.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