From: Tom Tromey <tom@tromey.com>
To: "Alexandra Hájková via Gdb-patches" <gdb-patches@sourceware.org>
Cc: "Alexandra Hájková" <alexandra.khirnova@gmail.com>
Subject: Re: [PATCH] configure.ac: Check for the readline.h explicitly
Date: Thu, 18 Nov 2021 08:36:30 -0700 [thread overview]
Message-ID: <87y25la329.fsf@tromey.com> (raw)
In-Reply-To: <20211118121440.558038-1-ahajkova@redhat.com> ("Alexandra =?utf-8?B?SMOhamtvdsOh?= via Gdb-patches"'s message of "Thu, 18 Nov 2021 13:14:40 +0100")
>>>>> ">" == Alexandra Hájková via Gdb-patches <gdb-patches@sourceware.org> writes:
>> From: Alexandra Hájková <ahajkova@redhat.com>
>> When readline development package is missing make fails with
>> "configure: error: system readline is not new enough" which
>> might be confusing. This patch checks for the readline.h explicitly
>> and makes make to warn about the missing package.
Hi. Thanks for the patch.
>> diff --git a/configure b/configure
>> index 787fcf89100..6a1da1665d8 100755
>> --- a/configure
>> +++ b/configure
>> @@ -755,6 +755,7 @@ infodir
>> docdir
>> oldincludedir
>> includedir
>> +runstatedir
>> localstatedir
>> sharedstatedir
>> sysconfdir
This hunk and some of the other ones may mean that you're regenerating
configure with a distro-modified autoconf rather than the pristine
upstream version. I'm not sure (maybe someone else did this and your
patch is correcting it, I never remember), but FAOD make sure you're
using the unmodified one.
>> if test "$with_system_readline" = yes; then
>> + AC_CHECK_HEADERS(readline/readline.h, [readline_h=yes], [readline_h=no])
>> + if test "$readline_h" = "no"; then
>> + AC_MSG_ERROR([readline development packages are probably missing])
>> + fi
This seems reasonable to me.
Tom
next prev parent reply other threads:[~2021-11-18 15:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-18 12:14 Alexandra Hájková via Gdb-patches
2021-11-18 15:36 ` Tom Tromey [this message]
2021-11-20 18:37 ` [PATCH v2] " Alexandra Hájková via Gdb-patches
2021-11-22 16:37 ` Kevin Buettner 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=87y25la329.fsf@tromey.com \
--to=tom@tromey.com \
--cc=alexandra.khirnova@gmail.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