From: Peter Korsgaard <peter@korsgaard.com>
To: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Cc: Christian Stewart <christian@aperture.us>, buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/containerd: fix btrfs handling
Date: Sat, 23 Mar 2024 13:45:56 +0100 [thread overview]
Message-ID: <87wmptyv3v.fsf@48ers.dk> (raw)
In-Reply-To: <20240321211245.508853-1-fontaine.fabrice@gmail.com> (Fabrice Fontaine's message of "Thu, 21 Mar 2024 22:12:45 +0100")
>>>>> "Fabrice" == Fabrice Fontaine <fontaine.fabrice@gmail.com> writes:
> btrfs handling doesn't depend on btrfs-progs but on kernel >= 4.12 since
> bump to version 1.7.7 in commit 79e01ef9506a6cdc4836912607dc594ae7b1999d
> and
> https://github.com/containerd/containerd/commit/024a748c092cbddde0918f2e93a646ce50116e11
> resulting in the following build failure:
> In file included from vendor/github.com/containerd/btrfs/v2/btrfs.go:21:0:
> ./btrfs.h:19:2: error: #error "Headers from kernel >= 4.12 are required on compilation time (not on run time)"
> #error "Headers from kernel >= 4.12 are required on compilation time (not on run time)"
> ^~~~~
> In file included from vendor/github.com/containerd/btrfs/v2/btrfs.go:21:0:
> ./btrfs.h:22:10: fatal error: linux/btrfs_tree.h: No such file or directory
> #include <linux/btrfs_tree.h>
> ^~~~~~~~~~~~~~~~~~~~
> Fixes: 79e01ef9506a6cdc4836912607dc594ae7b1999d
> - http://autobuild.buildroot.org/results/d6afeef47daae1783dcce3e2b6a0a16e3e5d5fbd
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>
Committed, thanks.
--
Bye, Peter Korsgaard
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2024-03-23 12:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-21 21:12 [Buildroot] [PATCH 1/1] package/containerd: fix btrfs handling Fabrice Fontaine
2024-03-23 12:45 ` Peter Korsgaard [this message]
2024-03-25 7:29 ` Peter Korsgaard
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=87wmptyv3v.fsf@48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@buildroot.org \
--cc=christian@aperture.us \
--cc=fontaine.fabrice@gmail.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