Article 5KBVS Got stuck at verifying modules being built into the kernel for Hybris HAL

Got stuck at verifying modules being built into the kernel for Hybris HAL

by
Kristoffer G
from LinuxQuestions.org on (#5KBVS)
I'm working on porting Sailfish OS to my Samsung Galaxy S10 Plus (SM-G975F) using the HADK which stands for Hardware Adaptation Development Kit (I added the PDF for it as an attachment to this thread) and I use Lineage 17.1 as a base.

After coming to page 15 and running make hybris-hal droidmedia I use the mer-kernel-checker verify script to verify that the kernel that was built doesn't have any warnings or errors anymore and here's where I got stuck.

Here's the defconfig that builds the kernel for Lineage 17.1 that I'm trying to change to build the Sailfish OS kernel: https://github.com/whatawurst/androi...2lte_defconfig

I know for a fact that I have changed the defconfig to solve the warnings and errors that's displayed so hybris-hal should show no warnings or errors.

I compared with the .config in /obj/KERNEL_OBJ/ and they don't look the same and I have no clue as to why.

I have looked in the FAQ-HADK and the hot-hadk if the issue is reported (at the time of this writing), but I can't see that anyone else experiences this.

I'll also add the summary of the HADK to show you how far I've come and what steps I've finished.

Copy paste the content of fixup-mountpoints.txt to /hadk/hybris/hybris-boot/fixup-mountpoints before building anything.
Attached Files
pdf.gifHADK.pdf (273.1 KB)
log.gifRebuilding hybris-hal and getting the same WARNINGS.log (174.1 KB)
txt.giffixup-mountpoints.txt (2.3 KB)
log.gifThis is how far the HADK has taken me.log (3.2 KB)
latest?d=yIl2AUoC8zA latest?i=-Jk7hP75298:3L7x1seSkso:F7zBnMy latest?i=-Jk7hP75298:3L7x1seSkso:V_sGLiP latest?d=qj6IDK7rITs latest?i=-Jk7hP75298:3L7x1seSkso:gIN9vFw-Jk7hP75298
External Content
Source RSS or Atom Feed
Feed Location https://feeds.feedburner.com/linuxquestions/latest
Feed Title LinuxQuestions.org
Feed Link https://www.linuxquestions.org/questions/
Reply 0 comments