<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 4, 2018 at 5:04 AM, Bas Mevissen <span dir="ltr"><<a href="mailto:abuse@basmevissen.nl" target="_blank">abuse@basmevissen.nl</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
<br>
Hi all,<br>
<br>
I ran into several issues with kernel-devsrc when building Poky Sumu with the meta-freescale layer for an Freescale i.mx6sx ARM board. In this mail(thread) I would like to collect them all and discuss the possible options to resolve them.<br>
<br>
* Install dependency issues (both during image creation and manual install on the board):<br>
<br>
The kernel-devsrc spec file defines a number of auto-generated run-time dependencies. These include<br>
(1) /bin/awk<br>
(2) /usr/bin/python<br>
<br>
(1) is due to scripts/ver_linux being an awk script using /bin/awk in its shebang in various (vendor) kernels, even recent ones. Instead of fixing all those kernel sources, I would suggest:<br>
1a) adding a link to /bin/awk in the awk or the kernel-devsrc package<br>
1b) automatically fix the kernel source included in the kernel-devsrc package<br>
1c) having a more helpful error message?<br>
<br>
(2) is normally fine, but on my build, there is only /usr/bin/python3. A manually created symlink fixed the issue. I'm wondering what a more permanent solution would be:<br>
2a) Fix all Python script in the installed kernel source like 1b)? (the python3-native package does create such a symlink, but not the target one!)<br>
2b) See whether there is a package that already creates that symlink and make kernel-devsrc depend on it?<br>
<br>
* External module build issue:<br>
<br>
When building an external module (rtl8812au driver) on the board using kernel-devsrc, I ran into the following issues:<br>
<br>
(3) No symlink from /lib/modules/`uname -r`/build to the kernel source. Solution:<br>
3a) Add this symlink (and optionally "source") to kernel-devsrc, comparable to Fedora kernel-headers package<br>
<br>
(4) The scripts where not build, resulting in build error. Solution:<br>
4b) Pre-build scripts ("make scripts") in kernel-devsrc. Should be ok, as the package is already arch dependent.<br>
<br>
(remarkably, there is mention of both in the <a href="http://kernel-devsrc.bb" rel="noreferrer" target="_blank">kernel-devsrc.bb</a> file, but I think the current solutions are wrong as the package is not ready-to-use currently)<br>
<br>
* Multiple kernel support:<br>
<br>
When developing, multiple kernel versions might be installed. Current version of the package installs in /usr/src/kernel without the kver in the patch.<br>
<br>
(5) So you can have only 1 set of kernel sources installed. Proposal:<br>
(5a) Install in /usr/src/kernels/`uname r` following the way Fedora does it.<br>
<br>
* Huge size of package<br>
<br>
(6) The package contains an awful lot of files and is huge. Not all of them are needed to compile external kernel modules<br>
6a) Remove the sources and only provide what is needed to build external kernel modules (like fedora)<br>
6b) Create the package suggested at 6a) (or add it to kernel-dev) and keep the devsrc as the full-source alternative.<br>
<br>
<br>
Your thoughts? I'm more than happy to fix the issues and provide patches. However, I need input on what direction to go on the issues I ran into until now.<br></blockquote><div><br></div><div>There's already a completely re-written kernel-devsrc that I posted in the last</div><div>dev cycle, which will be re-sent in the next few days. The only reason it didn't</div><div>merge was due to a multlib issue, which should be sorted out now.</div><div><br></div><div>So please, don't do any patches on top of the existing devsrc structure, since</div><div>it is essentially obsolete.</div><div><br></div><div>Cheers,</div><div><br></div><div>Bruce</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
<br>
Bas.<span class="HOEnZb"><font color="#888888"><br>
<br>
<br>
-- <br>
______________________________<wbr>_________________<br>
Openembedded-core mailing list<br>
<a href="mailto:Openembedded-core@lists.openembedded.org" target="_blank">Openembedded-core@lists.openem<wbr>bedded.org</a><br>
<a href="http://lists.openembedded.org/mailman/listinfo/openembedded-core" rel="noreferrer" target="_blank">http://lists.openembedded.org/<wbr>mailman/listinfo/openembedded-<wbr>core</a><br>
</font></span></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature">"Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end"</div>
</div></div>