All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Petr Červenka" <grugh@centrum.cz>
To: "Henning Schild" <henning.schild@siemens.com>,
	"Philippe Gerum" <rpm@xenomai.org>
Cc: Xenomai <xenomai@xenomai.org>
Subject: Re: [I-PIPE] ipipe-core-4.14.71-x86-1 released
Date: Fri, 02 Nov 2018 14:20:31 +0100	[thread overview]
Message-ID: <20181102142031.712D8BE3@centrum.cz> (raw)
In-Reply-To: 000000001f9d00090368043c91bd

You are right.
The errors were because of version 3.0.7. I didn't realize, that prepare-kernel.sh script doesn't only apply the patch. But it also copies part of the xenomai to the kernel.
 
Meanwhile I tried the latest git (probably master branch). I got another error (simple to fix) in one of the rtnet drivers:
drivers/xenomai/net/drivers/e1000e/netdev.c: In function ‘e1000e_set_interrupt_capability’:
drivers/xenomai/net/drivers/e1000e/netdev.c:1225:11: error: implicit declaration of function ‘pci_enable_msix’; did you mean ‘pci_enable_msi’? [-Werror=implicit-function-declaration]
     err = pci_enable_msix(adapter->pdev,
           ^~~~~~~~~~~~~~~
           pci_enable_msi
 
Petr Cervenka
 
______________________________________________________________
> Od: "Henning Schild" <henning.schild@siemens.com>
> Komu: "Philippe Gerum" <rpm@xenomai.org>
> Datum: 02.11.2018 11:07
> Předmět: Re: [I-PIPE] ipipe-core-4.14.71-x86-1 released
>
> CC: <xenomai@xenomai.org>
Am Thu, 1 Nov 2018 18:38:47 +0100
 schrieb Philippe Gerum <rpm@xenomai.org>:
 
 > On 11/1/18 5:59 PM, Petr Červenka wrote:
 > > Hello.
 > >  
 > > Is it really finished?
 > > I have problems to compile the patched kernel.
 > >  
 > > At first, when it compiles machine.c, there is such error:
 > >   CC      arch/x86/xenomai/machine.o
 > > In file included from ./include/asm-generic/xenomai/syscall.h:23:0,
 > >                  from
 > > arch/x86/xenomai/include/asm/xenomai/syscall.h:24, from
 > > arch/x86/xenomai/machine.c:22: ./arch/x86/include/asm/uaccess.h: In
 > > function ‘set_fs’: ./arch/x86/include/asm/uaccess.h:33:9: error:
 > > dereferencing pointer to incomplete type ‘struct task_struct’
 > > current->thread.addr_limit = fs; ^~
 > >  
 > > After an ad-hoc fix, there are some other errors for example during
 > > compiling of thread.c, mostly connected to fpu: fpu.fpregs_active,
 > > fpu.active_state, __fpregs_deactivate(), __fpregs_activate(),
 > > clts(), stts(), SLAB_NOTRACK, ... Am I doing something wrong?
 > >    
 > 
 > You are likely not using the proper Xenomai branch, you need -next.
 
 I would not suggest next, master and stable/v3.0.x should do. But
 v3.0.7 and older will not work.
 
 As far as i understood we will soon have a v3.1, for people that like
 their releases ;).
 
 Henning


  parent reply	other threads:[~2018-11-02 13:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-01 16:59 [I-PIPE] ipipe-core-4.14.71-x86-1 released Petr Červenka
2018-11-01 17:38 ` Philippe Gerum
2018-11-02 10:07   ` Henning Schild
2018-11-02 11:45     ` Jan Kiszka
2018-11-02 13:20   ` Petr Červenka [this message]
2018-11-02 14:49     ` Jan Kiszka
2019-02-18 13:31       ` [rtnet] e1000e/netdev.c deprecated pci_enable_msix alessio margan
  -- strict thread matches above, loose matches on Subject: below --
2018-10-31 16:27 [I-PIPE] ipipe-core-4.14.71-x86-1 released xenomai
2018-11-01  2:07 ` Alec Ari

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=20181102142031.712D8BE3@centrum.cz \
    --to=grugh@centrum.cz \
    --cc=henning.schild@siemens.com \
    --cc=rpm@xenomai.org \
    --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.