From: Mike Frysinger <vapier@gentoo.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 0/3] vboot-utils fixes
Date: Sat, 2 Jan 2016 01:17:40 -0500 [thread overview]
Message-ID: <20160102061740.GQ25803@vapier.lan> (raw)
In-Reply-To: <cover.1451483256.git.alex.suykov@gmail.com>
On 30 Dec 2015 16:05, Alex Suykov wrote:
> vboot-utils depend on relatively recent host kernel headers,
> and fail to build on some of the autobuilders.
>
> MTD_CHAR_MAJOR definition appears in linux-3.13, and ssize_t related
> failures probably happen with glibc from the same timeframe.
>
> Sadly I cannot check it properly, I can only tell it does not break
> builds on newer systems. If possible, please try them on some older
> systems before applying.
>
> If everything works well, I'd try to send 0002 upstream, but probably not 0001.
> It's an ugly fix and I don't think upstream cares much about older kernels.
please send all of them to us via gerrit
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20160102/80135f9b/attachment.asc>
prev parent reply other threads:[~2016-01-02 6:17 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 14:05 [Buildroot] [PATCH 0/3] vboot-utils fixes Alex Suykov
2015-12-30 14:05 ` [Buildroot] [PATCH 1/3] vboot-utils: MTD_CHAR_MAJOR definition Alex Suykov
2015-12-30 14:58 ` Thomas Petazzoni
2015-12-30 14:05 ` [Buildroot] [PATCH 2/3] vboot-utils: ssize_t needs unistd.h Alex Suykov
2015-12-30 14:58 ` Thomas Petazzoni
2015-12-30 14:06 ` [Buildroot] [PATCH 3/3] vboot-utils: remove hash file Alex Suykov
2015-12-30 15:00 ` Thomas Petazzoni
2015-12-30 21:41 ` Arnout Vandecappelle
2015-12-30 21:53 ` Thomas Petazzoni
2015-12-30 22:10 ` Arnout Vandecappelle
2015-12-30 22:53 ` Thomas Petazzoni
2016-01-01 14:52 ` Alex Suykov
2016-01-01 21:52 ` Yann E. MORIN
2016-01-01 19:45 ` Peter Korsgaard
2016-01-02 6:17 ` Mike Frysinger [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=20160102061740.GQ25803@vapier.lan \
--to=vapier@gentoo.org \
--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