All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Berger <xenomai.list@gmail.com>
To: Greg Gallagher <greg@embeddedgreg.com>
Cc: "Xenomai@xenomai.org" <xenomai@xenomai.org>
Subject: Re: xenomai 3.1/ipipe-core-4.19.128-cip28-arm-10.patch
Date: Wed, 8 Jul 2020 00:12:39 +0300	[thread overview]
Message-ID: <de705804-291c-55de-66bd-0f3ee3a40138@gmail.com> (raw)
In-Reply-To: <CALLqZ8REwJXSjZ4m3D3_VGdfgf66ZcG0_oWq0MajEn3jMCXQWw@mail.gmail.com>

Hi,

My comments are in-line

On 07/07/2020 20:48, Greg Gallagher wrote:
> Yocto seems to be expecting that the
> kernel you are using is going to be 5.4 and is generating headers
> based on that.  So apps think that 407 is a valid system call but our
> 4.19 kernel doesn't know what system call that is.  I don't have a lot
> of yocto experience but you could try moving to an older yocto branch
> that supports 4.19 kernels and see what happens.

Well ;)

Every OE/YP release comes with some default kernel version and one would 
think the kernel headers of this kernel version are used to build the 
glibc, which kind of is the case, but it's 2 different recipes.

So although I use kernel version 4.19.x to apply the xenomai patch it 
still uses 5.4 kernel headers by default. I knew that and added my own 
4.19 kernel-headers recipe. But it looks like it was not used to build 
glibc, since I see some auto generated file with the 407 syscall.

I am still fighting trying to build a glibc with 4.19 kernel headers 
(which I think I managed).

I'll keep you updated.

> 
> -Greg

Thanks,

Robert

> 
>>
>> Will try something more drastic to see what happens.
>>
>> Regards,
>>
>> Robert



  reply	other threads:[~2020-07-07 21:12 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-06 23:28 xenomai 3.1/ipipe-core-4.19.128-cip28-arm-10.patch Robert Berger
2020-07-06 23:49 ` Greg Gallagher
2020-07-07 10:06   ` Robert Berger
2020-07-07 16:30   ` Robert Berger
2020-07-07 17:48     ` Greg Gallagher
2020-07-07 21:12       ` Robert Berger [this message]
2020-07-07 22:57       ` Robert Berger
2020-07-07 23:04       ` Robert Berger
2020-07-08 12:41         ` Greg Gallagher
2020-07-08 21:19           ` Robert Berger
2020-07-09  3:55             ` Greg Gallagher
2020-07-13 17:08         ` Jan Kiszka
2020-07-13 22:00           ` Robert Berger
  -- strict thread matches above, loose matches on Subject: below --
2020-07-04 18:59 Robert Berger
2020-07-04 19:03 ` Robert Berger

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=de705804-291c-55de-66bd-0f3ee3a40138@gmail.com \
    --to=xenomai.list@gmail.com \
    --cc=greg@embeddedgreg.com \
    --cc=xenomai@xenomai.org \
    /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.