[yocto] Fwd: preempt-rt for 4.14.71 fails to build

[Dimitris Tassopoulos]

I've already send this to that list a few days ago, but since I didn't got
any reply there I've also asked here in case that someone else shares the
same experience.

Dimitris

On Wed, 10 Oct 2018, 21:48 Bruce Ashfield, <bruce.ashfield at windriver.com>
wrote:

> On 2018-10-10 2:18 PM, Dimitris Tassopoulos wrote:
> > Hi all!
> >
> > I've tried to build the latest preempt-rt kernel from the
> > `v4.14/standard/preempt-rt/base`
> > and it fails to build. These are the hashes I've used:
> >
>
> This should go to the linux-yocto list, since that's where
> people interested in the linux-yocto kernel variants will
> notice it.
>
> In this case, there was a bad merge. If you check the
> preempt-rt branches of 4.14 there's a fix queued, but I
> haven't sent SRCREV updates yet.
>
> Bruce
>
> > ```
> > LINUX_VERSION = "4.14.71"
> > SRCREV_machine = "c37a14708f5b618602f84f83f902346e055824c3"
> > SRCREV_meta = "1fb0b0379fb5883ce5af7485374e3f78ee4272d3"
> > ```
> >
> > And the errors I get are:
> > ```
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:
>
> > In function '__rt_mutex_lock':
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:2044:48:
>
> > error: passing argument 3 of 'rt_mutex_fastlock' from incompatible
> > pointer type [-Werror=incompatible-pointer-types]
> >    rt_mutex_fastlock(lock, TASK_UNINTERRUPTIBLE, rt_mutex_slowlock);
> >                                                  ^~~~~~~~~~~~~~~~~
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:1935:1:
>
> > note: expected 'struct ww_acquire_ctx *' but argument is of type 'int
> > (*)(struct rt_mutex *, int,  struct hrtimer_sleeper *, enum
> > rtmutex_chainwalk,  struct ww_acquire_ctx *)'
> >   rt_mutex_fastlock(struct rt_mutex *lock, int state,
> >   ^~~~~~~~~~~~~~~~~
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:2044:2:
>
> > error: too few arguments to function 'rt_mutex_fastlock'
> >    rt_mutex_fastlock(lock, TASK_UNINTERRUPTIBLE, rt_mutex_slowlock);
> >    ^~~~~~~~~~~~~~~~~
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:1935:1:
>
> > note: declared here
> >   rt_mutex_fastlock(struct rt_mutex *lock, int state,
> >   ^~~~~~~~~~~~~~~~~
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:
>
> > In function 'rt_mutex_lock':
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:2069:2:
>
> > error: too many arguments to function 'rt_mutex_lock_state'
> >    rt_mutex_lock_state(lock, TASK_UNINTERRUPTIBLE, 0);
> >    ^~~~~~~~~~~~~~~~~~~
> >
> /rnd/yocto/nativeos/build/tmp/work-shared/congatec/kernel-source/kernel/locking/rtmutex.c:2028:20:
>
> > note: declared here
> >   static int __sched rt_mutex_lock_state(struct rt_mutex *lock, int
> state)
> > ```
> >
> > Is there any change that the latest rt44 patches are nor applied?
> >
> > Thanks!
> > Dimitris
> >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.yoctoproject.org/pipermail/yocto/attachments/20181010/f23a32ca/attachment.html>