public inbox for linux-ext4@vger.kernel.org
 help / color / mirror / Atom feed
From: "Theodore Ts'o" <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] libss: add newer libreadline.so.8 to dlopen path
Date: Fri, 20 Aug 2021 17:07:39 -0400	[thread overview]
Message-ID: <YSAZm8XAkXmW2VMC@mit.edu> (raw)
In-Reply-To: <20210820161502.8497-1-jack@suse.cz>

On Fri, Aug 20, 2021 at 06:15:02PM +0200, Jan Kara wrote:
> OpenSUSE Tumbleweed now has libreadline.so.8. Add it to the list of libs
> to look for.
> 
> Signed-off-by: Jan Kara <jack@suse.cz>
> ---
>  lib/ss/get_readline.c | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> Hum, why don't we look for libreadline.so BTW? That way we could save adding
> now so version whenever one appears?

We do actually look for libreadline.so; it's right after
libreadline.so.4:

> -#define DEFAULT_LIBPATH "libreadline.so.7:libreadline.so.6:libreadline.so.5:libreadline.so.4:libreadline.so:libedit.so.2:libedit.so:libeditline.so.0:libeditline.so"

However, we still need the libreadline.so.N in the path because at
least for some distributions, they only install libreadline.so if you
install the -dev package.  For example, in Debian, libreadline.so.8 is
installed from the libreadline8 package, while libreadline.so is
installed from the libreadline-dev package (and it's not guaranteed to
be installed).

Fortunately for Debian users, openssh-client depends on libedit2,
which means that even if they don't have libreadline-dev installed, we
fall back to using libedit.so.2, which does work.  So apparently no
one noticed that a problem with debugfs on Debian Bullseye (which
ships libreadline.so.8).

But I agree that we should add libreadline.so.8 to the search path.

Thanks, applied.

      	    	    	       			- Ted

  reply	other threads:[~2021-08-20 21:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-20 16:15 [PATCH] libss: add newer libreadline.so.8 to dlopen path Jan Kara
2021-08-20 21:07 ` Theodore Ts'o [this message]
2021-08-23  9:31   ` Jan Kara

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=YSAZm8XAkXmW2VMC@mit.edu \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.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