From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [RFC PATCH] linux: let to work with xenomai in override mode
Date: Wed, 12 Sep 2018 22:08:22 +0200 [thread overview]
Message-ID: <20180912220822.7c6beee4@windsurf> (raw)
In-Reply-To: <1536782312-12240-1-git-send-email-michael@amarulasolutions.com>
Hello,
On Wed, 12 Sep 2018 21:58:32 +0200, Michael Trimarchi wrote:
> We would like to patch xenomai in override mode. Xenomai create
> symlink in order to build the kernel and those links are absolute
> one. The adeos patch is not applied if it is found so we
> can change the connect hook from PRE_PATCH to PRE_CONFIGURE.
> The xenomi dependence should be explicit set
>
> Change-Id: Idc5189047451bb9ac3019d3f35674d5332159918
> Signed-off-by: Michael Trimarchi <michael@amarulasolutions.com>
As I explained in our previous e-mail discussion, when you use
<pkg>_OVERRIDE_SRCDIR, you should handle any needed patching yourself.
Doing what you suggest here means that all patches from Linux kernel
extensions will be applied in the configure step, which is:
(1) Contrary to common sense: why should patching happen outside of
the patching step ?
(2) Completely inconsistent with what happens in all other packages
that use <pkg>_OVERRIDE_SRCDIR.
(3) Inconsistent with the initial principle of <pkg>_OVERRIDE_SRCDIR,
which is that the user *controls* the source code, and Buildroot
will not touch it all.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2018-09-12 20:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-12 19:58 [Buildroot] [RFC PATCH] linux: let to work with xenomai in override mode Michael Trimarchi
2018-09-12 20:08 ` Thomas Petazzoni [this message]
2018-09-12 20:15 ` Michael Nazzareno Trimarchi
2018-10-21 16:26 ` Arnout Vandecappelle
2018-10-28 10:25 ` Michael Nazzareno Trimarchi
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=20180912220822.7c6beee4@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox