From: Martin Jansa <martin.jansa@gmail.com>
To: Pascal Bach <pascal.bach@siemens.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: rebuilding external kernel modules when kernel changed
Date: Tue, 21 Jun 2016 16:40:29 +0200 [thread overview]
Message-ID: <20160621144029.GA14456@jama> (raw)
In-Reply-To: <fdf902fc-2f74-e750-7215-bd939cac4518@siemens.com>
[-- Attachment #1: Type: text/plain, Size: 1338 bytes --]
On Tue, Jun 21, 2016 at 04:36:32PM +0200, Pascal Bach wrote:
> Hello
>
> I ran into an issue when working with kernel modules that are not part of the kernel source tree.
>
> The issue manifests itself as follows:
>
> 1. Build an image containing virtual/kernel and kernel-module-a
>
> 2. Do a `bitbake virtual/kernel -c clean`
>
> 3. Rebuild the above image again. This causes the kernel do rebuild and it seems that the do_compile task of kernel-module-a is also re-exectued.
> But this causes an error as there is some configuration missing in the kernel source directory that is created by module.bbclass:do_make_scripts.
> I think that the issue is that the do_make_scripts task is not re-executed prior to the modules do_compile task.
>
>
> I tried to teach bitbake to execute do_make_scripts too once the kernel was rebuilt, but I didn't find a way.
>
> Any hints how this can be done?
What version are you using?
Are you using rm_work?
Check https://bugzilla.yoctoproject.org/show_bug.cgi?id=9352
>
> Regards
> Pascal
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-06-21 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-21 14:36 rebuilding external kernel modules when kernel changed Pascal Bach
2016-06-21 14:40 ` Martin Jansa [this message]
2016-06-21 15:21 ` Pascal Bach
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=20160621144029.GA14456@jama \
--to=martin.jansa@gmail.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=pascal.bach@siemens.com \
/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.