From: Joel Brobecker <brobecker@adacore.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: palves@redhat.com, gdb-patches@sourceware.org
Subject: Re: [PATCHSET] [4/4] Fix various issue in TUI
Date: Mon, 19 Jan 2015 15:43:00 -0000 [thread overview]
Message-ID: <20150119154301.GF4041@adacore.com> (raw)
In-Reply-To: <83y4p1zq7k.fsf@gnu.org>
> I just realized that I cannot push this changeset because Autoconf I
> have installed isn't version 2.64, and so I cannot regenerate
> 'configure'. Could someone please do that for me? The patch is
> below.
>
> Or I could push the patch below, and then someone else could do the
> generated files as a separate commit.
>
> Thanks in advance.
>
> Don't use windows-termcap.c when linking against a curses library
>
> gdb/
> 2015-01-17 Eli Zaretskii <eliz@gnu.org>
>
> * configure.ac [*mingw32*]: Only add windows-termcap.o to
> CONFIG_OBS if not building with a curses library.
>
> * windows-termcap.c: Include defs.h. Make the whole body empty if
> either one of HAVE_CURSES_H or HAVE_NCURSES_H or
> HAVE_NCURSES_NCURSES_H is defined.
I pushed this patch after having regenerated the configure script.
I edited the ChangeLog entry to add a line for configure being
regenerated.
> --- a/libiberty/ChangeLog
> +++ b/libiberty/ChangeLog
> @@ -1,3 +1,8 @@
> +2015-01-17 Eli Zaretskii <eliz@gnu.org>
> +
> + * strerror.c <sys_nerr, sys_errlist>: Declare only if they aren't
> + macros.
I pushed this change separately (and first).
To answer your question, such changes should be pushed to both
the GCC repository (SVN), and the binutils-gdb repository (git).
The commits are now in master; I can't remember whether these were
approved for 7.9, but if they were, then you can cherry-pick them
from master.
--
Joel
next prev parent reply other threads:[~2015-01-19 15:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-31 17:56 Eli Zaretskii
2015-01-05 19:55 ` Pedro Alves
2015-01-05 20:06 ` Eli Zaretskii
2015-01-17 9:55 ` Eli Zaretskii
2015-01-19 14:50 ` Joel Brobecker
2015-01-19 16:26 ` Eli Zaretskii
2015-01-19 16:54 ` Joel Brobecker
2015-01-19 15:43 ` Joel Brobecker [this message]
2015-01-19 17:31 ` Eli Zaretskii
2015-01-19 17:54 ` Joel Brobecker
2015-01-22 12:07 ` Pedro Alves
2015-01-22 16:26 ` Eli Zaretskii
2015-01-22 17:15 ` Pedro Alves
2015-01-22 17:30 ` Eli Zaretskii
2015-01-22 18:36 ` Pedro Alves
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=20150119154301.GF4041@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.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