From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: Jan Kiszka <jan.kiszka@siemens.com>
Cc: xenomai@xenomai.org
Subject: Re: ipipe 5.4.107 / 5.4.93 build issues on arm32
Date: Wed, 14 Apr 2021 20:35:17 +0200 [thread overview]
Message-ID: <20210414203517.772ea33c@windsurf.home> (raw)
In-Reply-To: <b72c8212-1638-891e-7a45-ffb9a5558400@siemens.com>
Hello,
On Wed, 14 Apr 2021 15:49:45 +0200
Jan Kiszka <jan.kiszka@siemens.com> wrote:
> Does
> https://source.denx.de/Xenomai/xenomai/-/commit/18ab00b7b0c2c2d0ed1f560cf4fb4161f6e9bde6
> help? Or did you build a tree that included this?
This helps, but the build fails a bit later with:
In file included from kernel/cpu.c:23:0:
./include/linux/stop_machine.h: In function ‘stop_machine_cpuslocked’:
./include/linux/stop_machine.h:150:2: error: implicit declaration of function ‘hard_irq_enable’; did you mean ‘hard_irq_disable’? [-Werror=implicit-function-declaration]
hard_irq_enable();
^~~~~~~~~~~~~~~
hard_irq_disable
But this makes me realize something: I am using Xenomai 3.1, together
with the ipipe patch
https://xenomai.org/downloads/ipipe/v5.x/arm/ipipe-core-5.4.107-arm-1.patch.
Maybe this doesn't make any sense, and this very recent ipipe patch is
only compatible with a more recent version of Xenomai ?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2021-04-14 18:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-14 12:42 ipipe 5.4.107 / 5.4.93 build issues on arm32 Thomas Petazzoni
2021-04-14 13:47 ` Greg Gallagher
2021-04-14 13:49 ` Jan Kiszka
2021-04-14 18:35 ` Thomas Petazzoni [this message]
2021-04-14 18:41 ` Greg Gallagher
2021-04-14 20:52 ` Thomas Petazzoni
2021-04-14 21:50 ` Greg Gallagher
2021-04-14 23:43 ` steve freyder
2021-04-15 5:35 ` Greg Gallagher
2021-04-15 6:52 ` Jan Kiszka
2021-04-15 12:09 ` Greg Gallagher
2021-04-15 12:41 ` Jan Kiszka
2021-04-15 12:48 ` Greg Gallagher
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=20210414203517.772ea33c@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=jan.kiszka@siemens.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.