Go Dirty, Never Clean and make your brain burn
Does anybody have tried or have any experience compiling this rom for our device?
I have spend few hours today figuring out how to do that, found some problems the fixinf them and the another problem and cant move forward.
Got his error:
Code:
make: *** No rule to make target '/home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes', needed by '/home/pajdek/DU/out/target/product/w7/obj/SHARED_LIBRARIES/libart-compiler_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Dont know what to do now any thoughts?
ppajdek said:
Go Dirty, Never Clean and make your brain burn
Does anybody have tried or have any experience compiling this rom for our device?
I have spend few hours today figuring out how to do that, found some problems the fixinf them and the another problem and cant move forward.
Got his error:
Code:
make: *** No rule to make target '/home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes', needed by '/home/pajdek/DU/out/target/product/w7/obj/SHARED_LIBRARIES/libart-compiler_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Dont know what to do now any thoughts?
Click to expand...
Click to collapse
Hi,
I compile several roms for the Galaxy S4, but I have seen this there before. A quick and dirty fix is to do this:
Code:
$ mkdir /home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/
$ touch /home/pajdek/DU/out/target/product/w7/obj/STATIC_LIBRARIES/libqc-art-compiler_intermediates/export_includes
Then you have to build dirty, e.g., don't "make clean" before your build.
Another option is to build CM for your phone, then steal the file from the out folder of CM's build and put it in the out folder of your build.
Here is a write up I did on that, if you want to read up on it a bit:
https://thealaskalinuxuser.wordpress.com/2016/06/10/error-no-rule-to-make-target-export_includes/
Hope that helps! Good luck!
Thanks for your reply, i will try that.
Uncle google told me that there were a commit for CM that should fix this.
Two solutions to try
Related
I had a working build environment for CM10, but then accidentally deleted the wrong VM. I started over and thought I'd done everything the same as before, but now I keep getting this when I try to build:
Code:
Export includes file: frameworks/av/media/libstagefright/yuv/Android.mk -- /home/darrian/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/libstagefright_yuv_intermediates/export_includes
make: *** No rule to make target `/home/darrian/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/libchromium_net_intermediates/export_includes', needed by `/home/darrian/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/libstagefright_intermediates/import_includes'. Stop.
make: *** Waiting for unfinished jobs....
Export includes file: external/tremolo/Android.mk -- /home/darrian/android/system/out/target/product/encore/obj/SHARED_LIBRARIES/libvorbisidec_intermediates/export_includes
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Note: Some input files use or override a deprecated API.
Note: Recompile with -Xlint:deprecation for details.
Note: Some input files use unchecked or unsafe operations.
Note: Recompile with -Xlint:unchecked for details.
Any ideas where my problem lies?
Ok, I solved it myself. Basically I wiped the virtual HDD and started over again. This time, when installing all the dependencies that I may or may not need, I did it completely using the software center and not at all using the terminal. This resulted in not installing some things I had installed before, because the software center could not find them, so I was probably forcing the install of packages that were conflicting or somehow otherwise mucking up the environment. I don't know enough about linux to really have any clue what happened, but it works now, so I'm happy.
Hey there all
I'm trying to compile a kernel for the GT-I9070P from the default Sammy source (opensource.samsung.com) and I've encountered an error and I hope you guys can help me with this:
Code:
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c: In function 'cm_DSP_AcknowledgeDspIrq':
drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.c:315:5: error: variable 'dummy' set but not used [-Werror=unused-but-set-variable]
cc1: all warnings being treated as errors
make[3]: *** [drivers/staging/nmf-cm/cm/engine/dsp/src/dsp.o] Error 1
make[2]: *** [drivers/staging/nmf-cm] Error 2
make[1]: *** [drivers/staging] Error 2
make[1]: *** Waiting for unfinished jobs....
I wonder if any of you guys have encountered these errors.....
Hi.
Dont use GCC 4.5+ to build kernel.
If you still wanna use GCC 4.5+, here is a method:
In your /drivers/staging/nmf-cm/makefile, just delete "Werror".
And build it again.
Recommend using Linaro GCC 4.4.5 or GCC 4.4.3 .
EDIT:
Although you can have a booting kernel, but the phone will reboot immediately when you dial out.
I replacd dsp.c from other source code, and it built with no errors.
The phone still will reboot when dial out.
Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.
CallMeVentus said:
Hmm....so that means the phone will reboot upon attempting to call someone ?
I give up writing anymore signatures.
Click to expand...
Click to collapse
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.
cocafe said:
Yep, when some calls come it will reboot, too.
It has no reboot issue with gcc 4.4
BTW,sorry, just now i replied a wrong thread.
Click to expand...
Click to collapse
Nah it's fine , I believe you just saved my ass
I give up writing anymore signatures.
Thread moved to General section.
Hello all, I was trying to cook up this AOKP based rom last night, and I let it build overnight as I usually do.
This morning, I woke up to:
Code:
make[6]: *** [drivers/net/wireless/bcmdhd/dhd_linux.o] Error 1
make[5]: *** [drivers/net/wireless/bcmdhd] Error 2
make[4]: *** [drivers/net/wireless] Error 2
make[3]: *** [drivers/net] Error 2
make[2]: *** [drivers] Error 2
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory `/home/nathan/AICP/kernel/htc/m7'
make: *** [TARGET_KERNEL_BINARIES] Error 2
I was going to use a prebuilt, but when I go to my m7spr directory (straight from AOKP source) I didn't see a kernel folder.
I know that I need to edit TARGET_KERNEL_BINARIES in BoardConfig.mk for m7-common, but I edited it to "aokp_m7_defconfig" and nothing changed. Please help and thank you in advance!!
That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE
thicklizard said:
That really doesn't show what the error is, just that there is an error.
Sent from my HTCONE
Click to expand...
Click to collapse
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.
nathantaylor said:
I was hoping that someone might recognize this or something but I run into almost every time.
Installed a package that someone said would fix the problem, and I'm anxious to see if it works, but it will have to be until tonight.
Also, I discovered that java 7 doesn't play well with kitkat. For some reason, you can use 7 to build jb, but if you use it with kitkat you will have issues. I installed 7 to use netflix on ubuntu, but I reverted to 6. The combination of those two things will hopefully fix it, if not I'll be back
Thank you for your help.
Click to expand...
Click to collapse
I would have to see the exact error in that .c file
Sent from my HTCONE
thicklizard said:
I would have to see the exact error in that .c file
Sent from my HTCONE
Click to expand...
Click to collapse
Yeah, I'm long past that terminal window now but if it ever comes up again I'll try and DM you or something.... Thank you
Sent from my Nexus 7 using Tapatalk 4
You can and will have many unidentifiable errors based on Java 7. In my experience, even having 6 installed won't help forever because somehow 7 will inadvertently be tripped; no idea why. This is what I did:
http://forum.xda-developers.com/showpost.php?p=47782603&postcount=4978
Hope it helps....
Hi, I recently try compiling AOSPA rom, I tried following the instructions given by others but when I use
Code:
./rom-build.sh ghost
It firstly runs a lot of lines of commands but finally return
Code:
make: *** No rule to make target `bacon'. Stop.
I tried to use otatools and envsetup and lunch, but they seem don't work on me, can somebody help me? Thank you
Hey guys,
I'm having an issue when building cyanogenmod 13.0. It gets to about 20 min into the build, then fails with this error:
Code:
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:57: HSIC cannot be resolved to a type
make: *** [/home/edwin/phonelab/cm-shamu/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
if anyone can point me in the right direction to get this straightened out I'd be appreciative.
saintsantos said:
/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type.
Click to expand...
Click to collapse
I am building CM-13.0 for LG G4 H811 and found the same problem. It's due to
Change 153678 - cmhw: Add PictureAdjustment stubs
which was just merged this morning. This is the sort of glaring bug that will be found and corrected quickly. Sometimes I wonder whether some folks actually build their code before merging it.
Edit to add:
14:00 EDT - I checked the change comments and the senior devs are aware of the problem and are working on it.
It was reverted about 20 minutes ago. You can either repo sync again, or cd to frameworks_opt_hardware and git revert a8ef044be1eb70c0f8a17f0c40d4c5c08bf71593
http://review.cyanogenmod.org/#/c/153678/
saintsantos said:
Hey guys,
I'm having an issue when building cyanogenmod 13.0. It gets to about 20 min into the build, then fails with this error:
Code:
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:22: The import cyanogenmod.hardware.HSIC cannot be resolved
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:46: HSIC cannot be resolved to a type
ERROR: /home/edwin/phonelab/cm-shamu/frameworks/opt/hardware/src/org/cyanogenmod/hardware/PictureAdjustment.java:57: HSIC cannot be resolved to a type
make: *** [/home/edwin/phonelab/cm-shamu/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.hardware_intermediates/with-local/classes.dex] Error 41
if anyone can point me in the right direction to get this straightened out I'd be appreciative.
Click to expand...
Click to collapse
Same issue here when building for jem (the Amazon Kindle Fire HD 8.9"). I'm going to run repo sync and rebuild as suggested in post #3.
Neo said:
It was reverted about 20 minutes ago. You can either repo sync again, or cd to frameworks_opt_hardware and git revert a8ef044be1eb70c0f8a17f0c40d4c5c08bf71593
http://review.cyanogenmod.org/#/c/153678/
Click to expand...
Click to collapse
Thanks. I reverted the commit in my repo anyway, but I'm just glad it was caught and handled.