summaryrefslogtreecommitdiffstats
path: root/meta-yocto/conf
diff options
context:
space:
mode:
authorAndré Draszik <git@andred.net>2016-08-18 08:56:24 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2016-09-09 11:53:36 +0100
commitfe90376acae1335c430ec400b8ada9ab3d536ee2 (patch)
tree313b5756215129a025e649652e2fc5f47288afb0 /meta-yocto/conf
parenta2966330bcd29e99c0403235edb29433b0c53d56 (diff)
downloadpoky-fe90376acae1335c430ec400b8ada9ab3d536ee2.tar.gz
module.bbclass: use Module.symvers for dependants
When compiling multiple external kernel modules, where one depends on the other, there are two problems at the moment: 1) we get compile time warnings from the kernel build system due to missing symbols (from modpost). 2) Any modules generated are missing dependency information (in the .modinfo elf section) for any dependencies outside the current source tree and outside the kernel itself. This is expected, but the kernel build system has a way to deal with this - the dependent module is expected to specify KBUILD_EXTRA_SYMBOLS (as a space-separated list) to point to any and all Module.symvers of kernel modules that are dependencies. While 1) by itself is not really a big issue, 2) prevents the packaging process from generating cross-source tree package dependencies. As a first step to solve the missing dependencies in packages created, we: 1) install Module.symvers of all external kernel module builds (into a location that is automatically packaged into the -dev package) 2) make use of KBUILD_EXTRA_SYMBOLS and pass the location of all Module.symvers of all kernel-module-* packages we depend on This solves both problems mentioned above. (From OE-Core rev: 88f1bc77c22091fccb00e80839adfdf34534187f) Signed-off-by: André Draszik <git@andred.net> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta-yocto/conf')
0 files changed, 0 insertions, 0 deletions