From: L A Walsh <lkml@tlinx.org>
To: util-linux@vger.kernel.org
Subject: why do I get this:/bin/findmnt.suse: /lib64/libsmartcols.so.1: version `SMARTCOLS_2.25' not found (required by /bin/findmnt.suse)
Date: Sun, 26 Aug 2018 22:27:10 -0700 [thread overview]
Message-ID: <5B838BAE.1010706@tlinx.org> (raw)
when smartcols.sym has a whole section with 2.25 syms in it.
What is the point of embedding mixing symbols with versions if they
don't work?
I.e. the 2.25 version of the symbols is in the lib, but findmnt linked
against 2.25 doesn't work cuz it can't access that specific label.
(sources from
2.32.1).
I don't understand why the symbols are versioned in a library that
doesn't appear to have anything other than a normal symbol table.
So why are these symbols versioned if they don't work? They seem to
prevent earlier versions of programs from working with later libs even
though they are compatible.
next reply other threads:[~2018-08-27 9:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-27 5:27 L A Walsh [this message]
2018-08-30 9:20 ` why do I get this:/bin/findmnt.suse: /lib64/libsmartcols.so.1: version `SMARTCOLS_2.25' not found (required by /bin/findmnt.suse) Karel Zak
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=5B838BAE.1010706@tlinx.org \
--to=lkml@tlinx.org \
--cc=util-linux@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;
as well as URLs for NNTP newsgroup(s).