Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] bootutils: fix build with glibc 2.28
Date: Sat, 29 Sep 2018 18:26:26 +0200	[thread overview]
Message-ID: <169683a6-c4e0-8f28-e14f-dd98a610b63d@gmail.com> (raw)
In-Reply-To: <20180929111537.22500-1-fontaine.fabrice@gmail.com>

Hi Fabrice,

Le 29/09/2018 ? 13:15, Fabrice Fontaine a ?crit?:
> Replace first patch which was adding sys/types.h to fix musl issue by a
> patch adding sys/sysmacros to fix build with glibc 2.28
> 
> Fixes:
>  - http://autobuild.buildroot.org/results/c26761663a764a2eb7af54316a6dc78bd01490fb
> 
> Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com>

Why we want to keep Bootutils in Buildroot?
Upstream is dead since 2009 and "BootUtils is a collection of utilities to
facilitate booting of modern Kernel 2.6 based systems"

Maybe it's time to remove this package?

Best regards,
Romain

  reply	other threads:[~2018-09-29 16:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-29 11:15 [Buildroot] [PATCH 1/1] bootutils: fix build with glibc 2.28 Fabrice Fontaine
2018-09-29 16:26 ` Romain Naour [this message]
2018-09-30  8:43   ` Peter Korsgaard
2018-09-30  8:41 ` 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=169683a6-c4e0-8f28-e14f-dd98a610b63d@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /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