From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH next 2/2] package/strace: reenable bpf for m68k
Date: Sun, 18 Aug 2019 00:04:30 +0300 [thread overview]
Message-ID: <87r25jec69.fsf@tarshish> (raw)
In-Reply-To: <20190817154243.16fa1e2e@windsurf.home>
Hi Thomas,
On Sat, Aug 17 2019, Thomas Petazzoni wrote:
> On Fri, 16 Aug 2019 06:54:38 +0300
> Baruch Siach <baruch@tkos.co.il> wrote:
>
>> Kernel commit 0472301a28f ("bpf: fix uapi bpf_prog_info fields
>> alignment") fixed the issue causing build failure in bpf support code.
>> The fix has been applied to all kernel versions that are affected and
>> supported (v4.19, v5.1, v5.2). Enable back bpf for m68k.
>>
>> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
>> ---
>> Note: the binary toolchain based on 2019.05.1 is still affected
>
> The kernel headers version used in 2019.05.1 are not recent enough ?
No.
For v5.1.x, 2019.05.1 has 5.1.16, but the fix is only in 5.1.20.
There is no fix for v5.0.x.
For v4.19.x, 2019.05.1 has 4.19.57, but the fix is only in 4.19.61.
baruch
--
http://baruch.siach.name/blog/ ~. .~ Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
- baruch at tkos.co.il - tel: +972.52.368.4656, http://www.tkos.co.il -
next prev parent reply other threads:[~2019-08-17 21:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-16 3:54 [Buildroot] [PATCH next 1/2] package/strace: bump to version 5.2 Baruch Siach
2019-08-16 3:54 ` [Buildroot] [PATCH next 2/2] package/strace: reenable bpf for m68k Baruch Siach
2019-08-17 13:42 ` Thomas Petazzoni
2019-08-17 21:04 ` Baruch Siach [this message]
2019-08-17 13:42 ` [Buildroot] [PATCH next 1/2] package/strace: bump to version 5.2 Thomas Petazzoni
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=87r25jec69.fsf@tarshish \
--to=baruch@tkos.co.il \
--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