Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: gdb-patches@sourceware.org
Subject: [patch] Fix --with-system-readline vs. readline-6.0+
Date: Fri, 31 Jul 2009 14:36:00 -0000	[thread overview]
Message-ID: <20090731085253.GA5744@host0.dyn.jankratochvil.net> (raw)

Hi,

configure --with-system-readline with system readline-6.0 do cause:
.../gdb/tui/tui-io.c:567: undefined reference to `readline_echoing_p'
.../gdb/tui/tui-io.c:525: undefined reference to `readline_echoing_p'
.../gdb/tui/tui-io.c:530: undefined reference to `readline_echoing_p'
	http://koji.fedoraproject.org/koji/getfile?taskID=1515524&name=build.log

There are now various vendor patches out there
	http://www.mail-archive.com/pld-cvs-commit@lists.pld-linux.org/msg174978.html
	http://lists.opensuse.org/opensuse-commit/2009-03/msg00362.html
	http://osdir.com/ml/fedora-extras-commits/2009-07/msg05039.html

After bundled readline gets upgraded to 6.0 this AC_DEFINE should be reversed
and tui/tui-io.c to be updated to use _rl_echoing_p of the bundled version.


Thanks,
Jan


gdb/
2009-07-31  Jan Kratochvil  <jan.kratochvil@redhat.com>

	Fix compatibility of --with-system-readline and readline-6.0+.
	* configure.ac <--with-system-readline> (for readline_echoing_p): New
	test.
	* config.in: Regenerate.
	* configure: Regenerate.

--- a/gdb/configure.ac
+++ b/gdb/configure.ac
@@ -536,6 +536,21 @@ if test "$with_system_readline" = yes; then
   READLINE=-lreadline
   READLINE_DEPS=
   READLINE_CFLAGS=
+
+  # readline-6.0 started to use the name `_rl_echoing_p'.
+  # `$(READLINE_DIR)/' of bundled readline would not resolve in configure.
+
+  AC_MSG_CHECKING([for readline_echoing_p])
+  save_LIBS=$LIBS
+  LIBS="$LIBS $READLINE"
+  AC_LINK_IFELSE(AC_LANG_PROGRAM(,[[extern int readline_echoing_p;
+				    return readline_echoing_p;]]),
+		 [READLINE_ECHOING_P=yes],
+		 [READLINE_ECHOING_P=no
+		  AC_DEFINE([readline_echoing_p], [_rl_echoing_p],
+			    [readline-6.0 started to use different name.])])
+  LIBS="$save_LIBS"
+  AC_MSG_RESULT([$READLINE_ECHOING_P])
 else
   READLINE='$(READLINE_DIR)/libreadline.a'
   READLINE_DEPS='$(READLINE)'


             reply	other threads:[~2009-07-31  8:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 14:36 Jan Kratochvil [this message]
2009-07-31 14:37 ` Andreas Schwab
2009-08-04 17:42   ` Tom Tromey
2009-08-05  8:03     ` Andreas Schwab

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=20090731085253.GA5744@host0.dyn.jankratochvil.net \
    --to=jan.kratochvil@redhat.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