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 16:34:52 -0700 [thread overview]
Message-ID: <506B7A1C.3000001@tlinx.org> (raw)
In-Reply-To: <20121002231359.GV23520@dastard>
Dave Chinner wrote:
> On Tue, Oct 02, 2012 at 03:52:08PM -0700, Linda Walsh wrote:
>> Dave Chinner wrote:
>>> Patches welcome.
>>>
>>> Cheers,
>>>
>>> Dave.
>> ---
>> Gee, that's a hard one... (build and tested that it was included)...
>
> Actually, it's a lot more than just changing the default. If the
> build system doesn't have libreadline/libedit/libtermcap installed,
> the build will fail.
>
> You need to add detection of the libraries' presence on the build
> system, and then the "--enable-*" options can go away entirely.
> See, for example, the way libuuid is detected in
> m4/package_uuiddev.m4...
----
Hmmm...Oh...I thought configure did that detection.. Now I see that
was never put it and it was basically a 'manual' on/off switch
that was available.
Urk.
On top of matters, my local distrib had readline installed in a way that
it wouldn't link had libreadline.so.x.y, libreadline.so.x => libreadline.so.x.y in
/usr/lib64 but libreadline.so=>libreadline.so.x was in
/usr/lib64/readline/libreadline.so.
???
Will have to figure out why that is and where it is supposed to be (I just
moved the soft-link from /usr/lib64/readline/libreadline.so to one dir up -- same
with libeditline...
>
> Also, libedit is only supposed to be used as a fallback option if
> libreadline is not available.
---
Oh... thought readline did the history part and edit did the edit part...
Oi vey...
Well.. hrumph...
Will have to look this over when i get some more time.
Have a system disk upgrade to do first...
Sigh. That I actually thought something might be simple... what an idiot!
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2012-10-02 23:33 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 ` Why xfs_<utils> not 'readline' w/line-edit & history enabled? (+attachment) Linda Walsh
2012-10-02 23:14 ` Dave Chinner
2012-10-02 23:34 ` Linda Walsh [this message]
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=506B7A1C.3000001@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox