Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte via buildroot" <buildroot@buildroot.org>
Cc: "Sen Hastings" <sen@hastings.org>,
	"Norbert Lange" <nolange79@gmail.com>,
	"Raphaël Mélotte" <raphael.melotte@mind.be>,
	"Yann E. MORIN" <yann.morin.1998@free.fr>
Subject: Re: [Buildroot] [PATCH 1/1] package/systemd: fix compiling with headers < 4.14
Date: Thu, 11 Jul 2024 22:00:40 +0200	[thread overview]
Message-ID: <20240711220040.22319e31@windsurf> (raw)
In-Reply-To: <20240617080310.2433521-1-raphael.melotte@mind.be>

On Mon, 17 Jun 2024 10:03:09 +0200
Raphaël Mélotte via buildroot <buildroot@buildroot.org> wrote:

> In commit 360a7cd738a85067ba60b029ca88eb7c874bfe4f ("package/systemd:
> bump linux-headers dependency to 4.14"), the headers requirements were
> bumped to 4.14 because of new build failures due to
> LOOP_SET_BLOCK_SIZE.
> 
> Even though systemd does not recommend using it with headers <
> 4.15 (see [1]), it is still possible to build it and use some of its
> features (after fixing the build failure).
> 
> Note that this was build-tested with 4.4 headers only, and not all the
> way back to 3.15 (which is the version requirement that was used
> before 360a7cd738a85067ba60b029ca88eb7c874bfe4f).
> 
> [1]: https://github.com/systemd/systemd/blob/main/README
> 
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
> ---
>  ...g_loop.h-fix-missing-LOOP_SET_BLOCK_.patch | 40 +++++++++++++++++++
>  package/systemd/Config.in                     |  7 ++--
>  system/Config.in                              |  6 +--
>  3 files changed, 47 insertions(+), 6 deletions(-)
>  create mode 100644 package/systemd/0001-src-basic-missing_loop.h-fix-missing-LOOP_SET_BLOCK_.patch

Applied to master, after refreshing the patch so that it applies on the
current version of systemd we have packaged, and updating the Upstream:
tag of the patch to point to the upstream commit, now that your pull
request has been accepted upstream.

Thanks a lot!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

      reply	other threads:[~2024-07-11 20:00 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-17  8:03 [Buildroot] [PATCH 1/1] package/systemd: fix compiling with headers < 4.14 Raphaël Mélotte via buildroot
2024-07-11 20:00 ` 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=20240711220040.22319e31@windsurf \
    --to=buildroot@buildroot.org \
    --cc=nolange79@gmail.com \
    --cc=raphael.melotte@mind.be \
    --cc=sen@hastings.org \
    --cc=thomas.petazzoni@bootlin.com \
    --cc=yann.morin.1998@free.fr \
    /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