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] [solved] some question to build Roms on server

hi,
i have setup my Server to Build daily builds for Cyanogenmod.
i have start the first time manually the process.
can it work with this selfmade script?
PHP:
#!/bin/bash
cd ~/android/system/
repo sync
cd ~/android/system/vendor/cm
./get-prebuilts
cd ~/android/system
source build/envsetup.sh && brunch endeavoru
and how i can copy or move the newest build to the Download directory?
i know that i can do it with "cp" or mv" but with the daily changed date in the Zip file?
and the last Question... how can i edit the "master" build.prop? i mean the Build.prop they didn´t change after "repo sync"
i use this Cyanogenmod Wiki http://wiki.cyanogenmod.org/w/Build_for_endeavoru
thanks for helping
http://lars-mueller.mobi/download/endeavoru/

Re: [Q] some question to build Roms on server
Should work, but I always do . build/envsetup.sh && brunch xxx instead of your way.
Sent from my One X using xda premium

it´s the same without source build.
do you know how can i copy the files with the script?

AW: [Q] some question to build Roms on server
Okay I have solved my problems. I move the filed via " mv /my/files/cm10.1-"Y-m-d".zip /destination/path/" to the public download directory..
And that is the directory http://lars-mueller.mobi/download/endeavoru
geschrieben mit dem Android 4.2.2 powerd HOX

Re: [Q] some question to build Roms on server
Oo nice!
I guess those are broken just like the official builds?
Sent from my One X using xda premium

why the Builds are broken, i try it tomorrow

Vendor blobs have been subject to a DMCA takedown. So the builds are missing 20mb of blobs.
Sent from my One X using xda premium

[Kernel Base][3.4.55][Dev]Bare Repositories of TW/AOSP Kernel (4.3 Sammy Sources!)

Up-to-Date Bare Repositories for TW/AOSP 4.2.2 Kernel​samsung-kernel-jfltexx​
Short Info:
I've made this repository to have a central place for everyone to fork their kernel base from. The advantage of this repo is that it is always up-to-date (as in the latest linux kernel version). Imagine the difference from starting at a 3.4.0 kernel base and 3.4.52 kernel base, there are thousands of new patches in that patch range. :good:
Repository Url:
Code:
https://github.com/broodplank/samsung-kernel-jfltexx
Repository Info:
Name: samsung-kernel-jfltexx
Description: Bare repositories for jfltexx (i9505)
Branches: tw-4.2.2 and aosp-4.2.2 (aosp 4.3 coming when 4.3 kernel sources are released)
tw-4.2.2 = Stock i9505 TouchWiz Kernel from Samsung sources patched until latest linux kernel version
aosp-4.2.2 = i9505g Google Edition Kernel (for AOSP 4.2.2 Google Edition and TouchWiz 4.2.2) (for i9505)
Getting the sources:
If you want to compile the kernel directly without much changes it's advised to clone it:
Code:
git clone [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url] -b branchname
If you want to make your own kernel it's advised to fork the kernel:
- Login at github
- Go to https://github.com/broodplank/samsung-kernel-jfltexx
- Click Fork at the right top of the page
Click to expand...
Click to collapse
Usage Info:
Initializing first config:
Code:
make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
Configuration:
Easiest variant (QT based GUI, needs libqt4-dev libqt4-core and libqt4-gui)
Code:
make xconfig
Default variant:
Code:
make menuconfig
Other less popular variants:
(GTK based, doesn't need any special packages)
Code:
make gconfig
(Ncurses based, needs libncurses5, libncurses5-dev and libncursesw5)\
Code:
make nconfig
Building Kernel:
Code:
export ARCH=arm
export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
make -jx (where x is the amount of cpu cores + 1)
Toolchains:
Toolchains that are suited for building the sources are:
arm-eabi-4.6
Click to expand...
Click to collapse
Building boot.img:
Code:
./build_bootimg
(Choose the rom type you will be using and it will be created in build/output)
Flashing boot.img and modules:
Code:
./flash_bootimg
(This is a process that pushes boot.img to your phone and then to the kernel partition, after that you can choose whether to push modules or not, and finally you can choose to wipe dalvik-cache or not and it will reboot.
Updating Info:
If you have forked the repository do this to fetch the updates from this repository:
First add it to the remote:
Code:
git remote add bare [url]https://github.com/broodplank/samsung-kernel-jfltexx[/url]
git fetch bare
Then search for the commit(s) that you want to merge
For 1 commit:
Code:
git cherry-pick [commit hash here, this is the last part of a commits url]
(for example: https://github.com/broodplank/samsung-kernel-jfltexx/commit/612bbea08b67f16dd5628cb8cd8406973f8fe821 would be: 612bbea08b67f16dd5628cb8cd8406973f8fe821)
For a range of commits:
Code:
git cherry-pick [commit a hash]^..[commit b hash]
Where commit a is the oldest commit and commit b the newest.
for example:
Code:
git cherry-pick 0bff3bdba64c58ea6100d72763f2be3acc9659db^..612bbea08b67f16dd5628cb8cd8406973f8fe821
This would patch the sources from 3.4.40 to 3.4.52

Latest Repository Changes:
3-08-2013
- Switched to real samsung 4.3 sources
29-07-2013
- Updated aosp-4.2.2 and tw-4.2.2 to 3.4.55
25-07-2013
- NEW BRANCH: AOSP-4.3
- NEW BRANCH: TW-4.3
- Added MSM8960 Headers from Google!
23-07-2013
- Update to 3.4.54
14-07-2013
- Update to 3.4.53
- Merge sensor fix from faux123
13-07-2013
- Updated defconfigs for proper building
09-07-2013
- Update to 3.4.52
- Sensor fix by ausdim
- Large update to readme
06-07-2013
- Add samsung sources
- Patch to latest version 3.4.51
- add boot.img creator
05-07-2013
- Initial commit, make repository

Thanks, I just forked it.
I'm a noob at this but am learning fast. I've modified and compiled the 3.0.31 kernel for the 9210T but I'd like to now try 3.4. Appears none of the celox changes for board_msm8x60.c source came across from 3.0 to 3.4 so I think I've got my work cut out for me.
m0tter

This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?

harise100 said:
This guide is not working for me.
If I follow your guide the resulting kernel boots, but I have no sound and no 3G (PIN pad doesn't show up).
I'm on MF8 stock ROM. Yours, Ausdims or my own (based on Samsung Update 2 sources) work fine.
This is what I did:
$ git clone https://github.com/broodplank/samsung-kernel-jfltexx -b tw-4.2.2
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig (no changes!)
$ make -j3
$ ./build_bootimg && ./flash_bootimg (selected 1 for TW)
What am I doing wrong?
Click to expand...
Click to collapse
InitRamfs??
Permisions of initramfs?

ausdim said:
InitRamfs??
Permisions of initramfs?
Click to expand...
Click to collapse
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
Don't know.
I used the script to build the boot.img. If I do the same with my sources, it works.
In both cases, I haven't touched those files.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks

ausdim said:
Im not on pc to check that and help you but your problem about radio (pin) sounds initramfs problem.
Unpack an stock boot.img and use that ramfs.
Thanks
Click to expand...
Click to collapse
Thank you for trying to help me... but it still doesn't work. Same result.

harise100 said:
Thank you for trying to help me... but it still doesn't work. Same result.
Click to expand...
Click to collapse
Tonight Ill do a little research on this and tell you the solution.

I remember when I started to make my first kernel, I had similar problems with the Samsung sources.
Wanam gave me his jf_defconfig file and it worked. He said that the config file by Samsung is crap. But I forgot to ask for details.
If I use my config file on your sources, it results in a bootloop, whereas they work fine with Samsung update 2 sources.
Does that make sense?
Sent from my GT-I9505 using xda app-developers app

Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2

.c0dy said:
Still figuring out, why i cant even successfully compile the sources. With ktoonse sources it works.
But i'm still a beginner. Will see about that xP
Gesendet von meinem GT-I9505 mit Tapatalk 2
Click to expand...
Click to collapse
What is your problem?
Sent from my GT-I9505 using xda app-developers app

harise100 said:
What is your problem?
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
I hate it -.- xD
Now it worked. And I do not know why... As I am pretty new to this, as already said, - could this be the problem? :
I think I made this:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ make xconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
Click to expand...
Click to collapse
instead of:
$ make VARIANT_DEFCONFIG=jf_eur_defconfig jf_defconfig
$ export ARCH=arm
$ export CROSS_COMPILE=/path/to/toolchain/bin/arm-eabi-
$ make xconfig
Click to expand...
Click to collapse
So I used xconfig before setting ARCH and CROSS_COMPILE.
Could that be the problem?
Atm i can not paste the error. The first one had something to do with a buffersize. Could "fix" that by setting "CONFIG_FRAME_WARN=1024" higher. Because it said it was 1032.
Second error was something like "‘ret’ may be used uninitialized in this function [-Wuninitialized]".
---------- Post added at 08:08 PM ---------- Previous post was at 07:32 PM ----------
Will add a new post for this, if it's okay.
And i hope it's okay to ask in here
So, first, as wrote in my previous post the compiling worked.
Now, i did the following:
1. Changed in the config: "kernel compression mode -> LZO
2. Removed "Optimize for size"
3. And changed the flag in the makefile to O3.
kernel/workqueue.c: In function 'freeze_workqueues_begin':
kernel/workqueue.c:483:11: warning: array subscript is above array bounds [-Warray-bounds]
error, forbidden warning: workqueue.c:483
make[1]: *** [kernel/workqueue.o] Error 1
make[1]: *** Waiting for unfinished jobs....
While writing this I reset "Optimize for size" and restart compiling. Now it does seem to work.
So i guess there is a problem with the flag. Where is the right place of the flag?

If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
If you want to use O2 or O3, it requires some modification of config and make files.
The build boot.img script worked for me right away.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
Ah okay, thanks. Will see if I can find a few more infos about that

broodplank1337 said:
Tonight Ill do a little research on this and tell you the solution.
Click to expand...
Click to collapse
Did you find anything?
I do have a working build environment and I can compile and install a kernel that is better than stock kernel.
Only these sources don't work. How is that possible?
Sent from my GT-I9505 using xda app-developers app

.c0dy said:
Ah okay, thanks. Will see if I can find a few more infos about that
Click to expand...
Click to collapse
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app

harise100 said:
I'll give it a try when I get home.
Sent from my GT-I9505 using xda app-developers app
Click to expand...
Click to collapse
It will work if you have the right toolchain, I use this one:
http://www.mediafire.com/download/i...linaro_4.7.4-2013.07-build_2013_07_12.tar.bz2
It's an optimized Linaro toolchain (http://forum.xda-developers.com/showthread.php?t=2098133)

broodplank1337 said:
check out this commit: https://github.com/broodplank/andro...mmit/69b6e56fb4151f547368fc77d5ad682fbf99ea7b
Click to expand...
Click to collapse
Thanks Will try that.
I already compiled a kernel, but it just booted until the samsung logo.. after that instant reboot... :/

Compile of CM12.1 error

Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####

Same error here. Ask if they solved it.
http://forum.xda-developers.com/galaxy-s5/help/kltechnduos-compile-error-t3134865

Unfortunatelly, still no reply on linked thread
Sent from my HTC One X using XDA Free mobile app

I have the same error, see if someone can help us

Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?

teemo said:
Which Java do you build with?
Kitkat: Java 6
Lollipop: Java1.7
Did you try to make clean or clobber or simply "rm -rf out" ?
Click to expand...
Click to collapse
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Using Java 1.7 from time of first build CM 12.1. No problem with it till now. Yes, tried rm -rf out, I got same error after almost 4 hours of building. Sorry, I'm noob, so I don't know, what "make clean" or "clobber" is.
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?

teemo said:
I don't remember the difference of clean and clobber, they delete old files before compiling. But rm rf out does the same, just faster.
Is there other errors above or is it only this error 41?
Click to expand...
Click to collapse
All errors is in my initial post. First error is error 1. Don't know if this errors depends one on second ...
Sent from my HTC One X using XDA Free mobile app

milda25 said:
Hi devs,
I would like to ask you about this problem:
Many times I have compiled succesfully CM ROM (12.1) without any problems. Compiles still the same (same machine, same OS, ...) and since yesterday I get this error. I can not solve it. Please, does anyone know what to do?
Thanks in advance.
Code:
target Strip: recovery (/root/android/system/out/target/product/endeavoru/obj/EXECUTABLES/recovery_intermediates/recovery)
----- Making recovery image ------
Copying baseline ramdisk...
Modifying ramdisk contents...
cp: nelze získat informace o*„/root/android/system/out/target/product/endeavoru/root/init.recovery.*.rc“: Adresář nebo soubor neexistuje
make: [/root/android/system/out/target/product/endeavoru/ramdisk-recovery.img] Error 1 (ignored)
/root/android/system/out/target/product/endeavoru/recovery.img maxsize=8562048 blocksize=4224 total=7170048 reserve=88704
Made recovery image: /root/android/system/out/target/product/endeavoru/recovery.img
target Java: org.cyanogenmod.platform.sdk (/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /root/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/root/android/system/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (03:30 (mm:ss)) ####
Click to expand...
Click to collapse
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!

Are you doing forced sync?
These days we sometimes need to
repo sync --forced-sync

@bigtor_gj, @teemo Thanks for the tips, will try ASAP and send a feedback.
Sent from my HTC One X using XDA Free mobile app

biktor_gj said:
At your sorce dir, go to vedor/cmsdk, then run:
git reset --hard
After it finishes, go back to your source folder and run:
repo sync
That fixed that exact same error for me. It feels like there's some commit not going through when you simply do a repo sync or something..
Credits where they're due: http://forum.datadevelopement.com/o...building-lollipop-oneplus-one-t2947949/page37
Good luck!
Click to expand...
Click to collapse
Code:
target Java: org.cyanogenmod.platform.sdk (/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes)
javac: file not found: /home/rafitcu/Android/Cm12.1/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/cyanogenmod/platform/Manifest.java
Usage: javac <options> <source files>
use -help for a list of possible options
make: *** [/home/rafitcu/Android/Cm12.1/out/target/common/obj/JAVA_LIBRARIES/org.cyanogenmod.platform.sdk_intermediates/classes-full-debug.jar] Error 41
#### make failed to build some targets (02:02:04 (hh:mm:ss)) ####
No solved for me

Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.

Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app

da_reeseboy said:
Jumping in here - I'm having the same issue building pac for the lg g2. The last successful build I had was on 8/30. Since then, I've gone as far as formatting my build box and reloading ubuntu, then getting a fresh sync - still no success. (I thought it might have been an update to Ubuntu that messed it up)
I'm still looking for a solution as well.
Click to expand...
Click to collapse
milda25 said:
Same last sucessful date here
Sent from my HTC One X using XDA Free mobile app
Click to expand...
Click to collapse
You have given me an idea, I am testing a solution and so far it seems to work, if the compilation ends successfully, the share here.

Unfortunately, git reset --hard and repo sync --force-sync doesn't solved the problem. Still same error on same position of building

What java version is everyone using? Run java -version and put the results here.
Code:
[email protected]:~$ java -version
Picked up JAVA_TOOL_OPTIONS: -javaagent:/usr/share/java/jayatanaag.jar
java version "1.7.0_79"
OpenJDK Runtime Environment (IcedTea 2.5.6) (7u79-2.5.6-0ubuntu1.15.04.1)
OpenJDK 64-Bit Server VM (build 24.79-b02, mixed mode)

I switched from OpenJDK to Oracle's JDK... no difference. I just found the vm I started building on in July, untouched with no updates done. I will resync and try a build on it to see if its an update to one of the packages installed for building that is causing the issue.
...This will take some time...

http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?

teemo said:
http://forum.cyanogenmod.org/topic/115010-build-fails-javac/
Edit: Is THIS your issue ?
Click to expand...
Click to collapse
Thank you for the responses - those are both along the lines of the issue. The first post never mentioned what he deleted tho. The second one is definitely related as I can make it further in my build before failing when I revert that commit, but it still fails.
As few posts as there are online about having this issue, I don't think a commit is directly causing it, otherwise there wouldn't be any successful builds from anyone for the last couple weeks. I think its related to a security update that a few of us did, and most of the devs don't update if its not broken lol. I should know this afternoon...
Edit: I mean its an incompatibility between the changes to cmsdk and some security update I did.