linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Uli Heller <uli.heller@daemons-point.com>
To: Nick Terrell <terrelln@fb.com>
Cc: "linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: Btrfs progs pre-release 4.14-rc1
Date: Sat, 18 Nov 2017 10:03:58 +0100	[thread overview]
Message-ID: <90348c33-efe7-a6b7-ea6b-13082fbe2ffd@daemons-point.com> (raw)
In-Reply-To: <520341F4-58FE-4A62-BC46-78FA1709A323@fb.com>

Am 17.11.2017 um 21:08 schrieb Nick Terrell:
>> On Nov 17, 2017, at 8:48 AM, Uli Heller <uli.heller@daemons-point.com> wrote:
>>
>> I tried to compile these on ubuntu-14.04 running 4.4.0-98-generic
>> - I had to install libzstd-dev
>> - I had to disable the zstd tests
>>
>> Do you think this ends up in a working binary? Or am I doing something strange?
> You'll need to install libzstd-dev to compile with zstd enabled, since you
> need the libraries and headers. What version of libzstd do you have? You'll
> need a version >= 0.8.1 in order to read the compressed data.

I compiled and installed version 1.3.2. I didn't verify if this version 
is actually working OK.
The tests run during the build for quite some time and I didn't observe 
an error, so I assumed
it ought to be fine.

> On the zstd side, we're working on getting the version of zstd in Ubuntu
> 16.04 upgraded from 0.5.1 to a version >= 1.0.0 [1]. zstd-0.5.1 was
> released before the format stabilized, and can't read data produced by zstd
>> = 0.6.
> I would expect the zstd tests to fail if the zstd version is < 0.8.1.
> Otherwise, could you tell me which version of zstd you have, and I'll
> attempt to reproduce the issue.

OK, so the success of the zstd tests depend on the version of the 
library, not the version
of the kernel, right?

I can offer to send some output of the failing tests if it helps.

Thanks a lot + best regards, Uli

      reply	other threads:[~2017-11-18  9:03 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-14 15:33 Btrfs progs pre-release 4.14-rc1 David Sterba
2017-11-17 16:48 ` Uli Heller
2017-11-17 20:08   ` Nick Terrell
2017-11-18  9:03     ` Uli Heller [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=90348c33-efe7-a6b7-ea6b-13082fbe2ffd@daemons-point.com \
    --to=uli.heller@daemons-point.com \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=terrelln@fb.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 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).