From: Ned Bass <bass6@llnl.gov>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Lustre and libreadline
Date: Wed, 3 Jun 2015 11:57:16 -0700 [thread overview]
Message-ID: <20150603185716.GA10033@llnl.gov> (raw)
In-Reply-To: <556F4825.1050408@cray.com>
Hi Patrick,
LLNL builds a stand-alone liblustreapi library for our BG/Q compute
nodes, and readline isn't available there. Now, since we just install
the library and not the utils we don't actually need readline. Perhaps
rather than making the readline configurue check stricly mandatory, we
could add a --disable-utils option which, if specified, would make
readline optional.
Thanks,
Ned
On Wed, Jun 03, 2015 at 01:32:05PM -0500, Patrick Farrell wrote:
> Good afternoon,
>
> Cray has recently discovered that 'lfs getstripe' crashes with a
> null pointer if it is not built with libreadline (Found in
> 'readline-devel').
>
> When built without libreadline, Lustre uses its own implementation
> of the readline components it needs. (Look for "HAVE_LIBREADLINE"
> in libcfs/libcfs/util/parser.c) This is the source of the null
> pointer.
>
> I think libreadline should be available on every platform we wish to
> build Lustre on, so I'd rather not fix the broken internal version
> of it. Given that, is there any objection to adding an explicit
> BuildRequires to the spec, making it mandatory in the config
> process, and removing all traces of Lustre's internal readline
> implementation? If not, I'll open a Jira ticket to do this.
>
> - Patrick
> _______________________________________________
> lustre-devel mailing list
> lustre-devel at lists.lustre.org
> http://lists.lustre.org/listinfo.cgi/lustre-devel-lustre.org
next prev parent reply other threads:[~2015-06-03 18:57 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-03 18:32 [lustre-devel] Lustre and libreadline Patrick Farrell
2015-06-03 18:57 ` Ned Bass [this message]
2015-06-03 20:27 ` Patrick Farrell
2015-06-03 20:57 ` Ned Bass
2015-06-03 21:07 ` Simmons, James A.
2015-06-03 22:49 ` Ned Bass
2015-06-04 11:21 ` Dilger, Andreas
2015-06-04 17:37 ` Ned Bass
2015-06-04 17:47 ` Ned Bass
2015-06-05 17:15 ` Dilger, Andreas
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=20150603185716.GA10033@llnl.gov \
--to=bass6@llnl.gov \
--cc=lustre-devel@lists.lustre.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 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.