From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "minwoo.im.dev@gmail.com" <minwoo.im.dev@gmail.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>
Subject: Re: ndctl-v77: LIBCXL_5 not found
Date: Tue, 9 May 2023 19:23:46 +0000 [thread overview]
Message-ID: <0009d65b83ba5bfdfc022aee5fc900b14657f816.camel@intel.com> (raw)
In-Reply-To: <ZFpnIICkh3Wpqmn/@minwoo-desktop>
On Wed, 2023-05-10 at 00:30 +0900, Minwoo Im wrote:
> Hello ndctl,
>
> With the recent tag (v77), after building it with the following
> commands, `cxl` command is not albe to find `LIBCXL_5` version from the
> /lib/libcxl.so.1 installed.
>
> meson build
> ninja -C build
> meson install -C build
>
> root@vm:~/work/ndctl.git# cxl
> cxl: /lib/libcxl.so.1: version `LIBCXL_5' not found (required by cxl)
> root@vm:~/work/ndctl.git# ls -l /lib/libcxl.so.1
> lrwxrwxrwx 1 root root 15 May 9 15:28 /lib/libcxl.so.1 -> libcxl.so.1.1.3
>
> I'm not pretty certain how to go through with this, but I'm using v77
> with the following patch which might not be a good one to solve it.
>
>
> ---
> diff --git a/meson.build b/meson.build
> index 50e83cf770a2..665b8e958178 100644
> --- a/meson.build
> +++ b/meson.build
> @@ -307,7 +307,7 @@ LIBDAXCTL_AGE=5
>
> LIBCXL_CURRENT=5
> LIBCXL_REVISION=0
> -LIBCXL_AGE=4
> +LIBCXL_AGE=5
>
> root_inc = include_directories(['.', 'ndctl', ])
No, this patch would violate libtool versioning rules[1].
LIBCXL_5 should be available if the library has been rebuilt, it seems
like your cxl tool is picking up an older version of the library, maybe
installed via the package manager or something?
Can you try a full clean rebuild?
[1]: https://www.gnu.org/software/libtool/manual/html_node/Updating-version-info.html
>
>
>
> It would be great if any folks here can provide advices on this.
>
> Thanks,
prev parent reply other threads:[~2023-05-09 19:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-09 15:30 ndctl-v77: LIBCXL_5 not found Minwoo Im
2023-05-09 19:23 ` Verma, Vishal L [this message]
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=0009d65b83ba5bfdfc022aee5fc900b14657f816.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=linux-cxl@vger.kernel.org \
--cc=minwoo.im.dev@gmail.com \
--cc=nvdimm@lists.linux.dev \
/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