From: Linda Walsh <xfs@tlinx.org>
To: Dave Chinner <david@fromorbit.com>
Cc: xfs-oss <xfs@oss.sgi.com>
Subject: Re: Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment)
Date: Tue, 02 Oct 2012 15:52:08 -0700 [thread overview]
Message-ID: <506B7018.7040000@tlinx.org> (raw)
In-Reply-To: <20121002215253.GT23520@dastard>
[-- Attachment #1: Type: text/plain, Size: 136 bytes --]
Dave Chinner wrote:
> Patches welcome.
>
> Cheers,
>
> Dave.
---
Gee, that's a hard one... (build and tested that it was included)...
[-- Attachment #2: config.diff --]
[-- Type: text/plain, Size: 2671 bytes --]
--- configure.in 2011-08-04 07:04:44.000000000 -0700
+++ configure.in 2012-10-02 15:28:23.342090038 -0700
@@ -18,21 +18,21 @@
AC_SUBST(enable_gettext)
AC_ARG_ENABLE(readline,
-[ --enable-readline=[yes/no] Enable readline command editing [default=no]],
+[ --enable-readline=[yes/no] Enable readline command editing [default=yes]],
test $enable_readline = yes && libreadline="-lreadline",
enable_readline=no)
AC_SUBST(libreadline)
AC_SUBST(enable_readline)
AC_ARG_ENABLE(editline,
-[ --enable-editline=[yes/no] Enable editline command editing [default=no]],
+[ --enable-editline=[yes/no] Enable editline command editing [default=yes]],
test $enable_editline = yes && libeditline="-ledit",
enable_editline=no)
AC_SUBST(libeditline)
AC_SUBST(enable_editline)
AC_ARG_ENABLE(termcap,
-[ --enable-termcap=[yes/no] Enable terminal capabilities library [default=no]],
+[ --enable-termcap=[yes/no] Enable terminal capabilities library [default=yes]],
test $enable_termcap = yes && libtermcap="-ltermcap",)
AC_SUBST(libtermcap)
--- configure 2011-09-27 08:36:10.000000000 -0700
+++ configure 2012-10-02 15:45:07.911807028 -0700
@@ -1532,9 +1532,9 @@
--disable-libtool-lock avoid locking (might break parallel builds)
--enable-shared=yes/no Enable use of shared libraries default=yes
--enable-gettext=yes/no Enable alternate language support default=yes
- --enable-readline=yes/no Enable readline command editing default=no
- --enable-editline=yes/no Enable editline command editing default=no
- --enable-termcap=yes/no Enable terminal capabilities library default=no
+ --enable-readline=yes/no Enable readline command editing default=yes
+ --enable-editline=yes/no Enable editline command editing default=yes
+ --enable-termcap=yes/no Enable terminal capabilities library default=yes
--enable-blkid=yes/no Enable block device id library default=yes
--enable-lib64=yes/no Enable lib64 support default=yes
@@ -9971,7 +9971,8 @@
if test "${enable_readline+set}" = set; then :
enableval=$enable_readline; test $enable_readline = yes && libreadline="-lreadline"
else
- enable_readline=no
+ enable_readline=yes
+ libreadline="-lreadline"
fi
@@ -9981,7 +9982,8 @@
if test "${enable_editline+set}" = set; then :
enableval=$enable_editline; test $enable_editline = yes && libeditline="-ledit"
else
- enable_editline=no
+ enable_editline=yes
+ libeditline="-ledit"
fi
@@ -9990,6 +9992,9 @@
# Check whether --enable-termcap was given.
if test "${enable_termcap+set}" = set; then :
enableval=$enable_termcap; test $enable_termcap = yes && libtermcap="-ltermcap"
+else
+ enable_termcap=yes
+ libtermcap="-ltermcap"
fi
[-- Attachment #3: Type: text/plain, Size: 121 bytes --]
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-02 22:50 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-02 16:44 Why xfs_<utils> not 'readline' w/line-edit & history enabled? Linda Walsh
2012-10-02 18:41 ` Kinzel, David
2012-10-02 20:17 ` Dave Chinner
2012-10-02 21:29 ` Linda Walsh
2012-10-03 2:06 ` Eric Sandeen
2012-10-03 2:16 ` Nathan Scott
2012-10-03 3:51 ` Linda Walsh
2012-10-03 3:58 ` Nathan Scott
2012-10-03 4:21 ` Linda Walsh
2012-10-04 12:12 ` David Disseldorp
2012-10-02 21:30 ` Linda Walsh
2012-10-02 21:34 ` Linda Walsh
2012-10-02 21:52 ` Dave Chinner
2012-10-02 22:52 ` Linda Walsh [this message]
2012-10-02 23:14 ` Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment) Dave Chinner
2012-10-02 23:34 ` Linda Walsh
2012-10-02 23:50 ` Dave Chinner
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=506B7018.7040000@tlinx.org \
--to=xfs@tlinx.org \
--cc=david@fromorbit.com \
--cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.