From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: James Hilliard <james.hilliard1@gmail.com>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/1] package/ocf-linux: fix build with kernels up to version 4.14
Date: Tue, 1 Nov 2022 23:31:44 +0100 [thread overview]
Message-ID: <20221101233144.535079ab@windsurf> (raw)
In-Reply-To: <20221008134414.1305025-1-james.hilliard1@gmail.com>
Hello James,
On Sat, 8 Oct 2022 07:44:14 -0600
James Hilliard <james.hilliard1@gmail.com> wrote:
> Add patches fixing build on kernels up to version 4.14.
>
> Depend on !BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_15 as builds fail on 4.15
> and newer currently.
Thing is that !BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_15 does not guarantee
that the kernel is < 4.15. Indeed, the kernel version can be much more
recent than the kernel headers version. For example, you can be using
an external toolchain with headers 4.9... and be building a 6.0 Linux
kernel, against which the ocf-linux kernel modules will be built.. and
fail to build.
To be honest, the last release of ocf-linux was in 2017. It doesn't
build after 4.14, and even 4.14 requires patches. I would advocate for
dropping ocf-linux entirely. It was added by Gustavo back in the days,
and nobody ever cared about this package except you earlier this year
with the bump to 20171122. All other changes on ocf-linux have been
related to tree-wide cleanup/infrastructure changes.
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2022-11-01 22:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-08 13:44 [Buildroot] [PATCH 1/1] package/ocf-linux: fix build with kernels up to version 4.14 James Hilliard
2022-11-01 22:31 ` Thomas Petazzoni via buildroot [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=20221101233144.535079ab@windsurf \
--to=buildroot@buildroot.org \
--cc=james.hilliard1@gmail.com \
--cc=thomas.petazzoni@bootlin.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