Develop Bugs

[DEV] Building for 3.0 Kernel based ROMs [04-17]

After seeing how popular the HW codecs are in the 3.0 kernel test build, I realize that testers may consider building their own test ROMs and we're probably far enough along that the projects needed to be updated out at:
https://github.com/KFire-Android
So here's a quick explanation of how to sync down your own source for the android build (for right now it's CM9 and AOKP specific):
To start you will need to determine which code base you want to build for: CM9 or AOKP.
And then find that branch in the following project:
https://github.com/KFire-Android/android_local_manifest
The default branch is "ics" and this should work for building both AOSP and CM9 (AOSP untested as of yet). If you want to build AOKP change the branch to "ics-aokp".
The README.mkdn contains the setup instructions for how to get started.
Once you've followed those instructions you can execute the following from the command line:
. build/envsetup.sh
brunch otter
At the end of the long compile you can find your flashable ROM in the out/target/product/otter directory.
AS ALWAYS THE NEW KERNEL IS IN DEVELOPMENT. PLEASE WATCH YOUR BATTERY AND POWER OFF THE DEVICE WHEN NOT IN USE.

I'm looking up to the heaven's
wondering which cloud is yours
thank you
Sent from my Amazon Kindle Fire using xda premium

U r our hero hashcode
Sent from my LG-P500 using Tapatalk 2

Grrrr I can not for the life of me get ics to build. I need a new machine. If anyone gets an aokp build with 3.0 kernel would you mind sharing? Thanks
Sent from my Kindle Fire using Tapatalk 2 Beta-5

Will be doing this tonight!! Thanks!
CM9 Infuse - XDA Premium

pbailey212 said:
Grrrr I can not for the life of me get ics to build. I need a new machine. If anyone gets an aokp build with 3.0 kernel would you mind sharing? Thanks
Sent from my Kindle Fire using Tapatalk 2 Beta-5
Click to expand...
Click to collapse
The new AOKP build is totally untested btw. I can debug it later.
EDIT: And I fixed at least 1 issue where the existing amazon/otter projects need to be removed from AOKP (they're the old gingerbread kernel based build).
Re-grab the local_manifest.xml file here:
https://raw.github.com/KFire-Android/android_local_manifest/ics-aokp/local_manifest.xml

Hashcode said:
The new AOKP build is totally untested btw. I can debug it later.
EDIT: And I fixed at least 1 issue where the existing amazon/otter projects need to be removed from AOKP (they're the old gingerbread kernel based build).
Re-grab the local_manifest.xml file here:
https://raw.github.com/KFire-Android/android_local_manifest/ics-aokp/local_manifest.xml
Click to expand...
Click to collapse
I'm gonna try and build an AOKP rom from this, gonna start the repo sync soon just waiting on my VM to finish cloning.

So the build went fine, and I'm currently using the AOKP
Rom. The system UI keeps force closing but so far everything else seems to be working OK so far.
Sent from my Amazon Kindle Fire using xda premium

johnwayne007 said:
So the build went fine, and I'm currently using the AOKP
Rom. The system UI keeps force closing but so far everything else seems to be working OK so far.
Sent from my Amazon Kindle Fire using xda premium
Click to expand...
Click to collapse
Yep. As the kernel dev ramps down, I'll dig into that.
Sent from my XT894 using XDA

Hashcode said:
Yep. As the kernel dev ramps down, I'll dig into that.
Sent from my XT894 using XDA
Click to expand...
Click to collapse
Also the soft buttons do something kinda weird, it could just be a scaling/DPI problem at the moment Screenshot below. I also uploaded it if anyone else was interested in testing it out, its a pure AOKP rom with hashcodes 3.0 kernel, i didnt change anything.
Uploading a New build with Kernel 4 included, will post link to dropbox as soon as its done.
Special thanks to Hashcode for his awesome work, as well as the AOKP Team for their awesome ROM.

johnwayne007 said:
Also the soft buttons do something kinda weird, it could just be a scaling/DPI problem at the moment Screenshot below. I also uploaded it if anyone else was interested in testing it out, its a pure AOKP rom with hashcodes 3.0 kernel, i didnt change anything.
AOKP Otter Build 32 with Hashcode 3.0 Kernel
Special thanks to Hashcode for his awesome work, as well as the AOKP Team for their awesome ROM.
Click to expand...
Click to collapse
Where's the OP of that rom??
Sent from my LG-P500 using Tapatalk 2

http://forum.aokp.co/page/releases/_/build-32-r16
I'm assuming that you mean this link?
Sent from my Amazon Kindle Fire using xda premium

Hey hash, if i wanted to use this as a base and start modding the rom. Changing Icons etc, is their some guides out there as to how to do that? I am relatively new to modding a rom, i can follow the instructions to build one, but now i think i'd like to try and make my own.
Nevermind i found what i'm looking for.

johnwayne007 said:
Hey hash, if i wanted to use this as a base and start modding the rom. Changing Icons etc, is their some guides out there as to how to do that? I am relatively new to modding a rom, i can follow the instructions to build one, but now i think i'd like to try and make my own.
Nevermind i found what i'm looking for.
Click to expand...
Click to collapse
Could you post the link(s)/docs you found. I'm always looking for some good docu regarding CM and modding.
I don't have issues setting up my build environment, that's no problem. In fact I just built CM9 from the latest sources including Hashcodes kernel#4 from this evening and it's running like a charm on my KF. Thanks Hash!

So far i've found theme guides so far, now i'm looking for how to add in apps change build.prop before building.
http://forum.xda-developers.com/showthread.php?t=1377128
http://forum.xda-developers.com/showthread.php?t=916814

Is anyone else coming across these errors? Pastebin

loki154 said:
Is anyone else coming across these errors? Pastebin
Click to expand...
Click to collapse
Looks like a permissions or space / mounting issue on your ccache area.

Thanks Hash that worked!
Could we use your kernel and vendor and device files to pure AOSP?

Help? I just setup a vittualbox running ubuntu so I could make my own builds. On 5/9 I had a successful compile lots of warnings but it compiled all the way thru. Today I did:
. build/envsetup.sh
repo sync
brunch otter
Now it errors out:
GEN /root/android/system/out/target/product/otter/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c:206:24: fatal error: zconf.hash.c: No such file or directory
compilation terminated.
make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
make[2]: *** [otter_android_defconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/root/android/system/kernel/amazon/otter'
make: *** [/root/android/system/out/target/product/otter/obj/KERNEL_OBJ/.config] Error 2
What am I doing wrong?
oh yeah what is the difference between the ota.zip and the update.zip that comes out.
Thanks

mlpmail said:
GEN /root/android/system/out/target/product/otter/obj/KERNEL_OBJ/Makefile
HOSTCC scripts/kconfig/zconf.tab.o
scripts/kconfig/zconf.tab.c:206:24: fatal error: zconf.hash.c: No such file or directory
compilation terminated.
make[3]: *** [scripts/kconfig/zconf.tab.o] Error 1
make[2]: *** [otter_android_defconfig] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/root/android/system/kernel/amazon/otter'
make: *** [/root/android/system/out/target/product/otter/obj/KERNEL_OBJ/.config] Error 2
What am I doing wrong?
oh yeah what is the difference between the ota.zip and the update.zip that comes out.
Thanks
Click to expand...
Click to collapse
I also got an error yesterday:
Code:
make[6]: *** [/u02/dev/android/otter/cm9/out/target/product/otter/target/kbuild/services4/srvkm/env/linux/module.o] Error 1
make[5]: *** [_module_/u02/dev/android/otter/cm9/out/target/product/otter/target/kbuild] Error 2
make[4]: *** [sub-make] Error 2
make[3]: *** [all] Error 2
make[2]: *** [kbuild] Error 2
make[1]: *** [build] Error 2
make[1]: Leaving directory `/u02/dev/android/otter/cm9/kernel/amazon/otter/external/sgx/src/eurasia_km/eurasiacon/build/linux2/omap4430_android'
target Symbolic: libOMX.TI.DUCATI1.VIDEO.MPEG4E (out/target/product/otter/symbols/system/lib/libOMX.TI.DUCATI1.VIDEO.MPEG4E.so)
make: *** [KERNEL_EXTERNAL_MODULES] Error 2
When checking the build log a little further up I noticed a few errors like this:
/bin/sh: dos2unix: not found
These log messages did not appear in previous builds. So I went ahead and installed the tofrodos package:
apt-get install tofrodos
cd /usr/bin
ln -s fromdos dos2unix
ln -s todos unix2dos
Then the build went fine.
However, I then removed the dos2unix link in /usr/bin to see if the build will fail again - but it didn't - go figure.
In other words I'm not sure what really caused the error - all I know it works again in my environment...

[Dev Tutorial] Building CM9 from source PrimoC/U

Hello guys. I'm bringing another tutorial to the One V
So have you wanted to build CM9 for whatever reason? Maybe you have some code you want to submit to cyanogenmod and want to test on your one v? Well then this thread is for you!
First set up your build environment with this post by Google -> here
Now, run these commands
Code:
sudo curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > /usr/bin/repo
sudo chmod a+x /usr/bin/repo
cd ~/
mkdir cm9
cd cm9
repo init -u git://github.com/CyanogenMod/android.git -b ics
repo sync -j8
You just got repo, put it in /usr/bin/ made it executable, and got the source all at the same. Now you need to get the device folders for the CDMA One V. Thats easy, thanks to local_manifest.xml
run these commands bellow
Code:
cd ~/cm9/.repo/
nano local_manifest.xml
Now you have opened nano, a text editor. You will need to copy this code into nano, so you will get the proper device files.
Code:
This file is really just the location of all of these projects so repo can pull them all for you and keep them up to date
Now you will run this code
Code:
cd ~/cm9/
cd vendor/cm
./get-prebuilts
This code grabs the prebuilts that CyanogenMod uses in every build
Now you will be ready to build the this code is always the same
Code:
cd ~/cm9
. build/envsetup.sh
Now for device specific
Primoc:
Code:
brunch primoc
Primou:
Code:
brunch primou
Congratulations, the rom will be in the out/ dir inside the source. Grab the one that follows the right name scheme! And as always, enjoy!

Mods/admins recently had a discussion on where guides/tutorials should go and it was decided that the General section is the place for them. Moved there.

haha lol
i see why u did that
RD!
Sent from my One V

paarthdesai said:
haha lol
i see why u did that
RD!
Sent from my One V
Click to expand...
Click to collapse
Please keep ALL discussion pertinent to the thread and tutorial
Sent from my One V using Tapatalk 2

Was the OP intentionally changed to remove the location of the primo repositories ? This tutorial is kind of worthless now.
Anyone know where/how to change this so it works ?

No. I just lost my op privilege here. No mod ever got around to fixing it
Sent from my One V using Tapatalk 2

Can you post on how to do it? I'd like to try and fix the Bluetooth, and this seems the easiest way.

So I figured I'd give this a try, but no matter what I do I can't get it to find the primoc device in cyanogenmods local_manifest? I'm pretty new to this and this is the first thing I've tried to build, so maybe I should start somewhere else? please help

[Q] Device name question.

Hi everyone. I am attempting to buld my first ROM and am following a guide to build beanstalk. I am at a point that confuses me. The comand is "breakfast (Device name)". Is this just looking for "n7100" or is there a speacial name I have to put there? Thanks!!
PS: Before anyone say this is not the place for this, Id like to say sorry first. IF i can get this to work and I get permision from scott this will turn into a new Beanstalk build thread.

It depends on the Beanstalk build environment setup. Your best bet is to PM someone that has already built for a device and ask them.
Just something to try, you could try the breakfast command without typing anything after it and see if your device name shows up then.
When I started building from source, I have never used the breakfast command, only lunch and make.

Thanks for the reply. I am running into another problem thats a step before that. I am trying to get the curl command to work. It creates a file called repo but when I try to do the next command repo init "blahblah" I get an error code saying syntay error Doctype HTML. The only thing I can think of is that the repo file should be a python script but is getting saved as html. I dont know how to fix this. Can someone post there repo file. This is the code to I am using to create the repo file.
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Bert.C said:
It depends on the Beanstalk build environment setup. Your best bet is to PM someone that has already built for a device and ask them.
Just something to try, you could try the breakfast command without typing anything after it and see if your device name shows up then.
When I started building from source, I have never used the breakfast command, only lunch and make.
Click to expand...
Click to collapse

Goneeuro said:
Thanks for the reply. I am running into another problem thats a step before that. I am trying to get the curl command to work. It creates a file called repo but when I try to do the next command repo init "blahblah" I get an error code saying syntay error Doctype HTML. The only thing I can think of is that the repo file should be a python script but is getting saved as html. I dont know how to fix this. Can someone post there repo file. This is the code to I am using to create the repo file.
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
Click to expand...
Click to collapse
Have you got that big list of dependencies installed? If you dont know what I mean, search for aosp amd setting up build environment and theres a list of packages that need imstalling, python beimg one of them.
Actually looking at that link I dont think thats where my repo come from. If you can wait until tomorrow when Im back at my pc Ill sort out a step by step guide if you want? As in noob starting from scratch guide that I followed to get set up.
Sent from my GT-N7100 using Tapatalk

Bert.C said:
Have you got that big list of dependencies installed? If you dont know what I mean, search for aosp amd setting up build environment and theres a list of packages that need imstalling, python beimg one of them.
Actually looking at that link I dont think thats where my repo come from. If you can wait until tomorrow when Im back at my pc Ill sort out a step by step guide if you want? As in noob starting from scratch guide that I followed to get set up.
Sent from my GT-N7100 using Tapatalk
Click to expand...
Click to collapse
Yeah. I had a wrong link in the curl command. It was an old link. I googled it and replaced it, now everything seems to be working. Lets see though. Any help you can give though I would apreciate it.

Goneeuro said:
Yeah. I had a wrong link in the curl command. It was an old link. I googled it and replaced it, now everything seems to be working. Lets see though. Any help you can give though I would apreciate it.
Click to expand...
Click to collapse
What steps have you already taken mate? Start from the very beginning if you can and we shall get you up and running in no time at all (unless you already are?)

Hi. I got it syncing now. Thanks. The next command I'm not to sure of is the breakfast command.
Sent from my GT-N7100 using xda app-developers app

Goneeuro said:
Hi. I got it syncing now. Thanks. The next command I'm not to sure of is the breakfast command.
Sent from my GT-N7100 using xda app-developers app
Click to expand...
Click to collapse
Did you add your N7100 repo's to the local manifest?

Bert.C said:
Did you add your N7100 repo's to the local manifest?
Click to expand...
Click to collapse
Can I message you on hangouts?

Bert.C said:
Did you add your N7100 repo's to the local manifest?
Click to expand...
Click to collapse
Sent PM. :good:

Ok. Next question. Where or how do I get the device specific files for the note 2 so I can try to build the newest beanstalk. I thought they would automatically come from CM but the device isnt supported. Not sure if I mentioned this or not before but I have never done this before so it is a learning experience for me.

Kernel creation

I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)

ThePiGuy said:
I am trying to compile LOS 15.1 for my H815 using @kessaras's G4 files from AOSCP, and it broke during the kernel creation.
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit), and surprisingly it has carried on building. Are there any chances that this could break my phone permanently when I flash it (assuming the build completes)
Click to expand...
Click to collapse
Which branch of titan are you using?
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Which branch of titan are you using?
Click to expand...
Click to collapse
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
steadfasterX said:
If something goes wrong it just soft bricks so you will still have TWRP and download mode.
Click to expand...
Click to collapse
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device

ThePiGuy said:
To be honest, I have no idea. I just took the AOSCP device_lge_g4-common, device_lge_h815 and kernel_lge_msm8992 repos and modified them to point to the correct lineage directories instead of AOSCP
Thanks for confirming this. Its what I thought, and then I came across a forum saying the wrong kernel can hard brick your device
Click to expand...
Click to collapse
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Click to expand...
Click to collapse
I got them from github.com/cypheros/[reponame] and I obtained them by adding them to the local_manifest (with oreo-mr1-release as the revision) and repo syncing

steadfasterX said:
Yea ppl often don't know much about the correct brick terms..
So where do you take the repos from? From our suicide org?
Ensure you checkout the oreo branch! For all repos!
git checkout
Sent from my LG-H815 using XDA Labs
Click to expand...
Click to collapse
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)

@steadfasterX, have I done something obviously wrong?

ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Sent from my LG-H815 using XDA Labs

steadfasterX said:
Don't know about the txt failures. The image.gz-dtb is your zImage. It's the zImage with appended dtb
So does it boot or not?
Click to expand...
Click to collapse
This kept causing the android build to fail. I'll see if I can build android using that zimage as a prebuilt kernel

FYI moving this to the Help & Troubleshooting section

ThePiGuy said:
I have now tried building the kernel separately from the main android build process (both with suicide squirrel and official AOSCP sources), and It has finished by dumping the files "Image", "Image.gz" and "Image.gz-dtb" in the arch/arm/arm64/boot folder. Are these the files we are supposed to get (I thought we were supposed to get a zImage file)?
Also, it ended with the errors
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/thepiguy/kernel/kernel/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
CAT arch/arm64/boot/Image.gz-dtb
I have copied the full terminal output on hastebin if it helps (https://hastebin.com/regeqaqiva.rb)
Click to expand...
Click to collapse
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.

sdembiske said:
I have endeavoured to build the H812 UsU LineageOS 15.1 (for general interest and to gain a better understanding of what the build process entails) and have encountered the same text errors as you ran into:
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/L0L55P1_1_11.img' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_curved.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_flat.txt' given more than once in the same rule
/home/s/Desktop/LineageOS/kernel/lge/msm8992/scripts/Makefile.fwinst:45: target '/lib/firmware/sic/p1/p1_limit_mfts_folder.txt' given more than once in the same rule
make: Leaving directory '/home/s/Desktop/LineageOS/kernel/lge/msm8992'
ninja: build stopped: subcommand failed.
16:10:27 ninja failed with: exit status 1
You obviously overcame this but I'm wondering how you solved it ultimately? Was it just as you stated in the OP?
I looked at the error, and just commented out the line causing it (inside the g4-common/sepolicy/sysinit.te, it was saying unknown type sysinit)
Did you get to the bottom of the issue finally?
Appreciate any direction/solutions you can provide here.
Thanks,
S.
Click to expand...
Click to collapse
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)

ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
Just doing another build - if the error still appears, I'll post the full log. If it doesn't I'll indicate what I tried.
Thank you, appreciate it.
S.

ThePiGuy said:
So...the conclusion I came to was that those are warnings but not errors.
If you have a full ROM build where it works, if you look closely those still appear and then the build continues as normal
If you post the full build log I can see if I can find the problem (I would imagine the error is above those)
Click to expand...
Click to collapse
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.

sdembiske said:
The build failed with the same errors - I pulled off all I could off the terminal. If you have a specific log(s) in mind, please let me know.
Link: https://pastebin.com/3T1GTFQG
I'm really not sure where the build error is arising. I am running a full build make for the H812 UsU using
brunch lineage_h812_usu-userdebug
Thanks again,
S.
Click to expand...
Click to collapse
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well

ThePiGuy said:
Ok so unfortunately I don't think that log goes up high enough (it is the log I am looking for though)
See if you can increase the terminal scroll back size and/or use a method like piping to "tee" to save the output to a file as well
Click to expand...
Click to collapse
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)

sdembiske said:
OK - here you go:
Link: https://pastebin.com/QGWqLAJg
Didn't realize there was a setting in the terminal preferences to increase scroll back length to infinite.
I haven't spotted as yet anything that stands out in the log, so would appreciate you going through it.
Thanks again,
S.
Addendum: Found it, I believe @ThePiGuy
FAILED: /home/s/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp
/bin/bash -c "prebuilts/misc/linux-x86/flex/flex-2.5.39 -o/home/steve/Desktop/LineageOS/out/target/product/h812_usu/obj/STATIC_LIBRARIES/libedify_intermediates/lexer.cpp bootable/recovery/edify/lexer.ll"
flex-2.5.39: loadlocale.c:130: _nl_intern_locale_data: Assertion `cnt < (sizeof (_nl_value_type_LC_TIME) / sizeof (_nl_value_type_LC_TIME[0]))' failed.
Aborted (core dumped)
Click to expand...
Click to collapse
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it

ThePiGuy said:
Yep that's exactly what I found
I encountered this error when I began building - it's because Oreo requires an older version of this flex library (or something along those lines)
Run "export LC_ALL=C" before building - that should fix it
Click to expand...
Click to collapse
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.

sdembiske said:
Yes, just was about to do that as that seemed to be the recommended solution when I searched the error. Seems it cropped up in newer version of ubuntu-based linux versions.
Sorry I troubled you with this - if I had managed to scroll back far enough in the first place, I might have found it ...
Cheers & Thanks again.
S.
Click to expand...
Click to collapse
No worries
I think I asked enough of these questions when I was learning (including this exact one) so I absolutely don't mind answering them too

Kernel android-msm-marlin-3.18-pie-qpr2 build failed

Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.

me too

Adlismon said:
Hi all,
I am new to study the android. Right now, I faced a problem that the build would be failed at:
Running extra build command(s):
+ eval python build/buildinfo/buildinfo.py
++ python build/buildinfo/buildinfo.py
python: can't open file 'build/buildinfo/buildinfo.py': [Errno 2] No such file or directory
I noticed that there is a command line in the build.config: "EXTRA_CMDS='python build/buildinfo/buildinfo.py'". How the buildinfo folder be created? How can I solve this problem, thanks.
Click to expand...
Click to collapse
ucantseeme said:
me too
Click to expand...
Click to collapse
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.

Adlismon said:
Hi Sudoxd,
Thanks for your feedback. I am the creator of this topic and I don't know the "ucantseeme". Currently, I don't solve this compile error issue, but I do successfully to get the kernel image(Image.lz4) where is located at out/android-msm-xxx-xx.xx/private/msm-google/arch/arm64/boot/. I guess the function of buildinfo.py should be only to move the files to the target folder.
Click to expand...
Click to collapse
The files are all outputted where they are meant to be (/out/android.../dist) already, and the image.lz4 is the normal output. If yours outputs elsewhere I would sync, delete the buildinfo line and rebuild in a new directory and see what happens.

sudoxd said:
i can not tell if you 2 are the same person, trying to make this issue look popular or something. ucantseeme was made today and has 1 post, OP has 1 post but account was made a few months ago.
Either way, just now i synced the repo, and built the kernel after removing the "EXTRA_CMDS='python build/buildinfo/buildinfo.py'" line from build.config and it works just fine, booted to it while i am writing this.
Click to expand...
Click to collapse
thank you, thank you
I solved it