Active Topics

 


Reply
Thread Tools
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#681
No, do not abort. You need the complete Cyanogenmod source not only the Nexus specific device bits.
 

The Following User Says Thank You to mautz For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#682
My 100GB /home ran out of space again.
I deleted everything from $ANDROID_ROOT, updated my local manifest to point to John's repos and re-run the repo init and the sync. The sync is running but I am going to get some sleep. Hopefully by the morning I will have everything is downloaded again and at the night I can try to compile the kernel again. (Unless I fall asleep. )
 

The Following User Says Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#683
Originally Posted by mautz View Post
No, do not abort. You need the complete Cyanogenmod source not only the Nexus specific device bits.
I wanted to let it run but finally I had no other choice. Very sorry about wasting your time, I really do! But a fresh start will be better.
(I am not sure why the disk has filled up though. Maybe when I changed the local manifest and re-run the sync it kept all the previous stuff.) I am just watching the console where the syn is running and seemingly it is downloading stuff for cm-11.0 and sony and other devices. Hmm. I think this happened when I used the cm-12.1 branch from the CM too. I will check in the morning.

I use this in my local manifest now:
Code:
<project path="device/lge/hammerhead" name="RealJohnGalt/android_device_lge_hammerhead" revision="cm-12.1" />
<project path="kernel/lge/hammerhead" name="RealJohnGalt/android_kernel_lge_hammerhead" revision="cm-12.1" />
Edit: Everything is nicely downloaded:
Code:
Checking out files: 100% (195/195), done.
Syncing work tree: 100% (172/172), done.
And only 29GB used. So far so good.

Edit2: The kernel compilation also is nicely done:
Code:
#### make completed successfully (03:10 (mm:ss)) ####

Now, I can step forward to try building the HAL!

Last edited by edp17; 2019-11-13 at 11:25. Reason: Added extra info
 

The Following 2 Users Say Thank You to edp17 For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#684
That's what i call good news

But with this hammerhead.xml file, you downloaded the normal cm12.1 base and not the modified version from John

Last edited by mautz; 2019-11-13 at 08:27.
 

The Following 2 Users Say Thank You to mautz For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#685
Originally Posted by mautz View Post
That's what i call good news

But with this hammerhead.xml file, you downloaded the normal cm12.1 base and not the modified version from John
Oops! Which one was his version? The hybris-12.1 or staging/cm-12.1 or one of the stable ones?
I have a feeling that I have to iterate this step a few times.

Before I started the compilation double checked the CONFIG_SECURITY_SELINUX_BOOTPARAM was unset and commented out and the CONFIG_AUDIT was not in there at all in the 'cyanogenmod_hammerhead_defconfig'.
I also added the selinux=0 at the end of BOARD_KERNEL_CMDLINE in 'BoardConfig.mk'.
 

The Following User Says Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#686
Originally Posted by mautz View Post
That's what i call good news

But with this hammerhead.xml file, you downloaded the normal cm12.1 base and not the modified version from John
Without you it probably would take much looooooooonger and harder. Thank you!

Although I think dealing with the HAL also will be a bumpy ride.
 

The Following 2 Users Say Thank You to edp17 For This Useful Post:
Posts: 635 | Thanked: 1,535 times | Joined on Feb 2014 @ Germany
#687
Did your kernel pass the mer-kernel-check?

Since cm12.1 is a relatively old base, i'll cross my fingers that ou'll don't run into heavy problems with the droid hal part!
 

The Following 2 Users Say Thank You to mautz For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#688
Originally Posted by mautz View Post
Did your kernel pass the mer-kernel-check?

Since cm12.1 is a relatively old base, i'll cross my fingers that ou'll don't run into heavy problems with the droid hal part!
Unfortunately don't know whether it passes. I couldn't run that command because in the morning I had to stolen that time from my family to be able to compile the kernel and write the post here.
Hopefully I can continue this night.

Yes, this is an old base so in theory the one I downloaded should also work. I am also not at all sure about the differences between the original cm-12.1 and John's version. Plus I don't know the benefits/disadvantages of using this or that.

My current SFOS 2.0.4.13 installation is using cm-12.1-20160704-UNOFFICIAL-hammerhead-nocheck.zip base but honestly I don't have a clue whose fork is this. Plus what differences are (if there are any) between this base and the one I am about to build.

By the way, I am also not sure whether I can use the cm-12.1-20160704-UNOFFICIAL-hammerhead-nocheck.zip base with my Sailfish.zip once that is done.

So, I am totally about these.
 

The Following 2 Users Say Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#689
Originally Posted by mautz View Post
Did your kernel pass the mer-kernel-check?

Since cm12.1 is a relatively old base, i'll cross my fingers that ou'll don't run into heavy problems with the droid hal part!
Yes, the kernel passes the mer-kernel-check. (hybris/mer-kernel-check/mer_verify_kernel_config ./out/target/product/$DEVICE/obj/KERNEL_OBJ/.config)
Well, there are a lots of warning but no error.
 

The Following 2 Users Say Thank You to edp17 For This Useful Post:
edp17's Avatar
Posts: 592 | Thanked: 706 times | Joined on Jul 2019 @ UK
#690
I have done steps
  • 6. SETTING UP SCRATCHBOX2 TARGET
  • 7.1 Creating Repositories for a New Device
and now I am at '7.2.1 Building the droid-hal-device packages'.
When I ran 'rpm/dhd/helpers/build_packages.sh' got an error:
Code:
Error building the cache:
[adaptation0|plugin:/ssu?repo=adaptation0] Valid metadata not found at specified URL
Some of the repositories have not been refreshed because of an error.
* Building rpm/droid-hal-hammerhead.spec 
WARNING: CONFIG_BLK_CGROUP is invalid
It is unset
Allowed values : y, !
Comment says: systemd (optional): http://0pointer.de/blog/projects/cgroups-vs-cgroups.html

WARNING: CONFIG_ECRYPT_FS is invalid
It is unset
Allowed values : y, m, !
Comment says: optional extra filesystem (ecryptfs)

WARNING: CONFIG_SUNRPC is invalid
It is unset
Allowed values : y, m, !
Comment says: optional, for NFS support

error: Bad exit status from /var/tmp/rpm-tmp.McCUtC (%build)


RPM build errors:
    Bad exit status from /var/tmp/rpm-tmp.McCUtC (%build)
* Check /home/edp17/mer/android/droid/droid-hal-hammerhead.log for full log. 
!! building of package failed
To fix these, I guess, need to go back and change those values in the cyanogenmod_hammerhead_defconfig.
 

The Following User Says Thank You to edp17 For This Useful Post:
Reply

Tags
hammerhead, nexus5, sailfishos, sfdroid


 
Forum Jump


All times are GMT. The time now is 18:02.