From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Simon Marchi <simark@simark.ca>
Cc: GDB Patches <gdb-patches@sourceware.org>,
Jan Kratochvil <jan.kratochvil@redhat.com>
Subject: Re: [PATCH] Check for ncursesw first when searching for "tgetent"
Date: Wed, 14 Feb 2018 01:28:00 -0000 [thread overview]
Message-ID: <87o9ksfjgk.fsf@redhat.com> (raw)
In-Reply-To: <87d118hfs7.fsf@redhat.com> (Sergio Durigan Junior's message of "Tue, 13 Feb 2018 14:04:56 -0500")
On Tuesday, February 13 2018, I wrote:
> On Monday, February 12 2018, Simon Marchi wrote:
>
>> On 2018-01-31 04:04 PM, Sergio Durigan Junior wrote:
>>> Commit 5007d765ae09c10c7f3b18bb16841b9d2d59e181 ("Allow linking GDB
>>> with ncursesw") modified our configure.ac and included the check for
>>> "ncursesw" when searching for "waddstr". However, there's one more
>>> place where we should check for "ncursesw" first:
>>>
>>> AC_SEARCH_LIBS(tgetent, [termcap tinfo curses ncursesw ncurses])
>>>
>>> This patch changes the order of the libraries to be searched when
>>> looking for "tgetent", and puts "ncursesw" before "curses ...".
>>>
>>> This is another patch we carry on Fedora GDB.
>>
>> I think it makes sense, but can you expand on why this is needed?
>
> The rationale for this patch was:
>
> https://bugzilla.redhat.com/show_bug.cgi?id=1270534
>
> This is a bug that happened on Fedora GDB when linking against ncurses,
> but not ncursesw. The bug has been fixed upstream by commit
> 5007d765ae09c10c7f3b18bb16841b9d2d59e181, but the AC_SEARCH_LIBS line
> for tgetent has not been modified, so, for the sake of completeness, I
> think it makes sense to leave configure.ac in a consistent state (i.e.,
> requiring ncursesw over ncurses whenever applicable).
>
> I guess that's the gist of it. There's not much that can be said, the
> patch is really simple and its intention is to make things more uniform.
>
> I can include the link to the Red Hat bug in the commit message, if you
> want.
After talking to Pedro in private, I was convinced that this is not the
right explanation for the patch, either. Therefore, I will write a
better commit message and submit a v2, hopefully addressing your
concerns.
Thanks,
--
Sergio
GPG key ID: 237A 54B1 0287 28BF 00EF 31F4 D0EB 7628 65FC 5E36
Please send encrypted e-mail if possible
http://sergiodj.net/
prev parent reply other threads:[~2018-02-14 1:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-31 21:04 Sergio Durigan Junior
2018-02-10 1:43 ` Sergio Durigan Junior
2018-02-13 4:58 ` Simon Marchi
[not found] ` <87d118hfs7.fsf@redhat.com>
2018-02-14 1:28 ` Sergio Durigan Junior [this message]
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=87o9ksfjgk.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=simark@simark.ca \
/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