All of lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/linuxptp: fix build with new headers
Date: Tue, 26 Feb 2019 23:39:34 +0100	[thread overview]
Message-ID: <39be702c-6716-c855-ac9c-531278a7b713@gmail.com> (raw)
In-Reply-To: <87sgwad9z6.fsf@dell.be.48ers.dk>

Hello Peter,

Le 26/02/2019 ? 13:12, Peter Korsgaard a ?crit?:
>>>>>> "Romain" == Romain Naour <romain.naour@gmail.com> writes:
> 
>  > Hi Baruch, Artem, All,
>  > Le 25/02/2019 ? 06:58, Baruch Siach a ?crit?:
>  >> Hi Artem,
>  >> 
>  >> On Sun, Feb 24, 2019 at 11:49:31PM +0300, Artem Panfilov wrote:
>  >>> net_tstamp.h in recent kernel versions requires time.h for clockid_t.
>  >> 
>  >> This is a kernel bug. Kernel UAPI headers must not use the userspace clockid_t 
>  >> type. This bug has been fixed in kernel commit e2c4cf7f98a5 ("net: Use 
>  >> __kernel_clockid_t in uapi net_stamp.h") just before the v4.20 release. It 
>  >> looks like this Linaro toolchain took the headers of a kernel -rc release.
>  >> 
>  >> Maybe update the Linaro toolchain to 2019.02 in master?
>  >> Romain?
> 
>  > Actually it's not a Linaro toolchain anymore, it's an ARM toolchain.
> 
>  > Indeed, these toolchains use a 4.20 -rc kernel release.
>  > I noticed it while updating to the 2018.11 release that was released one month
>  > before the official kernel 4.20 release (respectively 23 Nov 2018 and 23 Dec
>  > 2018). I had to wait for BR2_TOOLCHAIN_HEADERS_AT_LEAST_4_20 symbol in Buildroot.
> 
>  > The latest ARM toolchain 2019.01 release use 5.0-rc1 kernel release.
>  > We can't include this version into Buildroot since the kernel 5.0 is not
>  > released yet.
> 
>  > Maybe we should report this issue to https://bugs.linaro.org ?
> 
> Yes, it would be nice if they could use released kernels for the
> headers.
> 

Done:
https://bugs.linaro.org/show_bug.cgi?id=4297

Best regards,
Romain

  reply	other threads:[~2019-02-26 22:39 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-24 20:49 [Buildroot] [PATCH 1/1] package/linuxptp: fix build with new headers Artem Panfilov
2019-02-25  5:58 ` Baruch Siach
2019-02-25  6:24   ` Artem Panfilov
2019-02-25 22:40   ` Romain Naour
2019-02-26 12:12     ` Peter Korsgaard
2019-02-26 22:39       ` Romain Naour [this message]
2019-02-27  8:53         ` Peter Korsgaard
2019-05-26 22:05 ` Arnout Vandecappelle

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=39be702c-6716-c855-ac9c-531278a7b713@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.