From: Yann E. MORIN <yann.morin.1998@free.fr>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4 1/1] Added linux drivers backports project
Date: Sun, 19 Apr 2015 15:15:30 +0200 [thread overview]
Message-ID: <20150419131529.GH4313@free.fr> (raw)
In-Reply-To: <20150419110326.31c34542@free-electrons.com>
Thomas, Petr, All,
On 2015-04-19 11:03 +0200, Thomas Petazzoni spake thusly:
--SNIP--]
> I wanted to apply your patch, and did a couple of updates to it (see
> below). However, there's a more fundamental problem to this package: it
> expects the linux package to be extracted/configured *before* the
> configuration of linux-backports. Unfortunately, this is not the case:
> 'linux' is only in LINUX_BACKPORTS_DEPENDENCIES, so it's only
> guaranteed to be here when linux-backports gets configured, not before.
[--SNIP--]
> I'm not sure yet of the possible solutions to this: add 'linux' to
> LINUX_BACKPORT_PATCH_DEPENDENCIES ? Use the linux extension mechanism
> as suggested by Arnout ?
Adding 'linux' to _PATCH_DEPENDENCIES will not be enough, because all
_PATCH_DEPENDENCIES guarantees is that such dependencies are extracted
and patched, not that they are configured/built or whatever.
So, the only option left would be to treat them as a linux extension,
and drop the build+install commands from linux-backports, and use the
integration strategy (instead of the packaging strategy), see:
https://backports.wiki.kernel.org/index.php/Documentation/integration
However, it seems to be quite involved...
Regards,
Yann E. MORIN.
--
.-----------------.--------------------.------------------.--------------------.
| Yann E. MORIN | Real-Time Embedded | /"\ ASCII RIBBON | Erics' conspiracy: |
| +33 662 376 056 | Software Designer | \ / CAMPAIGN | ___ |
| +33 223 225 172 `------------.-------: X AGAINST | \e/ There is no |
| http://ymorin.is-a-geek.org/ | _/*\_ | / \ HTML MAIL | v conspiracy. |
'------------------------------^-------^------------------^--------------------'
next prev parent reply other threads:[~2015-04-19 13:15 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 23:01 [Buildroot] [PATCH v4 1/1] Added linux drivers backports project Petr Vorel
2015-04-19 9:03 ` Thomas Petazzoni
2015-04-19 13:15 ` Yann E. MORIN [this message]
2015-04-19 16:20 ` Arnout Vandecappelle
2015-04-19 16:28 ` Yann E. MORIN
2015-04-19 17:03 ` Thomas Petazzoni
2015-04-19 21:19 ` Petr Vorel
2015-04-19 21:28 ` Yann E. MORIN
2015-04-20 20:42 ` Arnout Vandecappelle
2015-04-20 20:56 ` Thomas Petazzoni
2015-04-20 21:08 ` Arnout Vandecappelle
2015-04-20 21:00 ` Yann E. MORIN
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=20150419131529.GH4313@free.fr \
--to=yann.morin.1998@free.fr \
--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 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.