All of lore.kernel.org
 help / color / mirror / Atom feed
From: piaojun <piaojun@huawei.com>
To: <miklos@szeredi.hu>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>,
	"wangyan (AF)" <wangyan122@huawei.com>
Subject: Re: [QUESTION] `FUSE_3.1' not found error when calling fuse_new()
Date: Wed, 4 Sep 2019 08:45:05 +0800	[thread overview]
Message-ID: <5D6F0911.4000002@huawei.com> (raw)
In-Reply-To: <5D6F030B.7060901@huawei.com>

I clean up the /usr/local/lib/libfuse3.so.3 and reinstall fuse again,
the problem is gone. The new location of libfuse is
/usr/lib64/libfuse3.so.3. Probably the old libfuse is installed by my
manual 'make install'.

On 2019/9/4 8:19, piaojun wrote:
> Hi Miklos,
> 
> I encounter an error when calling fuse_new() from libfuse3.so.3, and I
> wonder if I missed some macro like 'FUSE_3.1' or fuse_new() could not
> be called like this?
> 
> Hope for your help.
> 
> ---
> # ./main
> ./main: /usr/local/lib/libfuse3.so.3: version `FUSE_3.1' not found (required by ./main)
> 
> main.c:
> #define FUSE_USE_VERSION 30
> #include <fuse3/fuse.h>
> #include <fuse3/fuse_lowlevel.h>
> 
> static struct fuse_operations hello_oper;
> 
> int main(int argc, char *argv[])
> {
>         struct fuse_args args = FUSE_ARGS_INIT(argc, argv);
>         struct fuse *fs;
> 
>         fs = fuse_new(&args, &hello_oper, sizeof(hello_oper), NULL);
> 
>         return 0;
> }
> 
> ---
> The fuse3-libs and devel rpm is from the following website:
> 
> https://centos.pkgs.org/7/epel-x86_64/fuse3-devel-3.6.1-2.el7.x86_64.rpm.html
> https://centos.pkgs.org/7/epel-x86_64/fuse3-libs-3.6.1-2.el7.x86_64.rpm.html
> 
> Thanks,
> Jun
> 

      reply	other threads:[~2019-09-04  0:45 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-04  0:19 [QUESTION] `FUSE_3.1' not found error when calling fuse_new() piaojun
2019-09-04  0:45 ` piaojun [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=5D6F0911.4000002@huawei.com \
    --to=piaojun@huawei.com \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=miklos@szeredi.hu \
    --cc=wangyan122@huawei.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 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.