All of lore.kernel.org
 help / color / mirror / Atom feed
* PREEMPT-RT patch: wrong header
@ 2015-12-07 13:03 mike9874 channel
  2015-12-07 16:19 ` mar.krzeminski
  2015-12-07 19:53 ` Bruce Ashfield
  0 siblings, 2 replies; 3+ messages in thread
From: mike9874 channel @ 2015-12-07 13:03 UTC (permalink / raw)
  To: yocto

[-- Attachment #1: Type: text/plain, Size: 613 bytes --]

Hello,
i am building an image for qeumux86 with the PREEMT-RT patch. Therefore I
use the following in my image.conf file:
PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
PREFERRED_VERSION_linux-yocto-rt ?= "4%"

I get an image with the 4.1.8-rt8-yocto-preempt-rt kernel. I have an
Application which is also build into the image where I try to use
SCHED_DEADLINE with sched_setattr() and struct sched_attr from <sched.h>.
My bitbake compiler throws following error: storage size of
'scheduling_attribut' isn't known.
Where do I get the correct Headers to compile my application?

Regards,
Mike

[-- Attachment #2: Type: text/html, Size: 744 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: PREEMPT-RT patch: wrong header
  2015-12-07 13:03 PREEMPT-RT patch: wrong header mike9874 channel
@ 2015-12-07 16:19 ` mar.krzeminski
  2015-12-07 19:53 ` Bruce Ashfield
  1 sibling, 0 replies; 3+ messages in thread
From: mar.krzeminski @ 2015-12-07 16:19 UTC (permalink / raw)
  To: mike9874 channel, yocto

[-- Attachment #1: Type: text/plain, Size: 851 bytes --]

Hello,

I think you need to set PREFERRED_VERSION_linux-headers, but I have no 
idea what you should set for yocto-rt.

Regards,
Marcin

W dniu 07.12.2015 o 14:03, mike9874 channel pisze:
> Hello,
> i am building an image for qeumux86 with the PREEMT-RT patch. 
> Therefore I use the following in my image.conf file:
> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
> PREFERRED_VERSION_linux-yocto-rt ?= "4%"
>
> I get an image with the 4.1.8-rt8-yocto-preempt-rt kernel. I have an 
> Application which is also build into the image where I try to use 
> SCHED_DEADLINE with sched_setattr() and struct sched_attr from 
> <sched.h>. My bitbake compiler throws following error: storage size of 
> 'scheduling_attribut' isn't known.
> Where do I get the correct Headers to compile my application?
>
> Regards,
> Mike
>
>


[-- Attachment #2: Type: text/html, Size: 1844 bytes --]

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: PREEMPT-RT patch: wrong header
  2015-12-07 13:03 PREEMPT-RT patch: wrong header mike9874 channel
  2015-12-07 16:19 ` mar.krzeminski
@ 2015-12-07 19:53 ` Bruce Ashfield
  1 sibling, 0 replies; 3+ messages in thread
From: Bruce Ashfield @ 2015-12-07 19:53 UTC (permalink / raw)
  To: mike9874 channel, yocto

On 12/07/2015 08:03 AM, mike9874 channel wrote:
> Hello,
> i am building an image for qeumux86 with the PREEMT-RT patch. Therefore
> I use the following in my image.conf file:
> PREFERRED_PROVIDER_virtual/kernel = "linux-yocto-rt"
> PREFERRED_VERSION_linux-yocto-rt ?= "4%"
>
> I get an image with the 4.1.8-rt8-yocto-preempt-rt kernel. I have an
> Application which is also build into the image where I try to use
> SCHED_DEADLINE with sched_setattr() and struct sched_attr from
> <sched.h>. My bitbake compiler throws following error: storage size of
> 'scheduling_attribut' isn't known.
> Where do I get the correct Headers to compile my application?

You need to look at the kernel sources themselves:

STAGING_KERNEL_DIR = "${TMPDIR}/work-shared/${MACHINE}/kernel-source"

The preempt-rt kernel isn't messing with the libc-headers, so if you
are missing a struct that it is modifying, it'll be in the kernel
source itself.

Bruce

>
> Regards,
> Mike
>
>



^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2015-12-07 19:53 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-12-07 13:03 PREEMPT-RT patch: wrong header mike9874 channel
2015-12-07 16:19 ` mar.krzeminski
2015-12-07 19:53 ` Bruce Ashfield

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.