From: Gao Xiang <xiang@kernel.org>
To: Igor Eisberg <igoreisberg@gmail.com>
Cc: linux-erofs@lists.ozlabs.org
Subject: Re: An issue with erofsfuse
Date: Fri, 20 Aug 2021 21:42:53 +0800 [thread overview]
Message-ID: <20210820134248.GB25885@hsiangkao-HP-ZHAN-66-Pro-G1> (raw)
In-Reply-To: <CABjEcnFcM+Yib-SzNHBegabTjhoNvv7vH6WAkdZO1Vx13s-9xw@mail.gmail.com>
On Fri, Aug 20, 2021 at 04:35:52PM +0300, Igor Eisberg wrote:
> You're right, this is definitely what's missing:
>
> > linux-vdso.so.1 (0x00007ffeb2163000)
> > libfuse.so.2 => /lib/x86_64-linux-gnu/libfuse.so.2
> > (0x00007ffb2d6b7000)
> > libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
> > (0x00007ffb2d694000)
> > libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007ffb2d4a3000)
> > libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007ffb2d49d000)
> > /lib64/ld-linux-x86-64.so.2 (0x00007ffb2d728000)
> >
>
> And actually when running configure, I notice this:
>
> > checking lz4.h usability... no
> > checking lz4.h presence... no
> > checking for lz4.h... no
> >
>
> Not sure what I'm missing here though...
Maybe "sudo apt install liblz4-dev" for debian.
(Anyway, I may need to add another erofsfuse package for Debian sid,
I may seek some time to do this.)
Thanks,
Gao Xiang
>
> $ apt list --installed | grep lz4
> > liblz4-1/now 1.9.3-2 amd64 [installed,local]
> > lz4/now 1.9.3-2 amd64 [installed,local]
> >
>
next prev parent reply other threads:[~2021-08-20 13:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-20 12:34 An issue with erofsfuse Igor Eisberg
2021-08-20 12:48 ` Gao Xiang
2021-08-20 13:16 ` Igor Eisberg
2021-08-20 13:26 ` Huang Jianan
2021-08-20 13:26 ` Gao Xiang
2021-08-20 13:35 ` Igor Eisberg
2021-08-20 13:42 ` Gao Xiang [this message]
2021-08-20 13:58 ` Igor Eisberg
2021-08-20 14:05 ` Gao Xiang
2021-08-20 14:14 ` Igor Eisberg
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=20210820134248.GB25885@hsiangkao-HP-ZHAN-66-Pro-G1 \
--to=xiang@kernel.org \
--cc=igoreisberg@gmail.com \
--cc=linux-erofs@lists.ozlabs.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).