yashsingh1/xdaforums huggingface dataset:
[Galaxy S Advance I9070 General] Freewaymad:
Recovery Build Error

Has anyone got this error? I am trying to build a recovery.

Export includes file: system/extras/ext4_utils/Android.mk -- out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/libext4_utils_static_intermediates/export_includes
Export includes file: external/zlib/Android.mk -- out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/libz_intermediates/export_includes
Export includes file: system/core/libsparse/Android.mk -- out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/libsparse_static_intermediates/export_includes
Export includes file: bootable/recovery/voldclient/Android.mk -- out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/libvoldclient_intermediates/export_includes
make: *** No rule to make target `out/target/product/sabresd_6dq/obj/STATIC_LIBRARIES/libsdcard_intermediates/export_includes', needed by `out/target/product/sabresd_6dq/obj/EXECUTABLES/recovery_intermediates/import_includes'. Stop.

Does anyone know how to fix it? Please help.

Thanks
[Galaxy S Advance I9070 General] BOOTMGR:
Yep. I'm familiar with git so i'm sure that i've synced jellybean branch (TC & CM). Another thing i noticed is that under settings > about, cyanogenmod version is showing unknown.
[Galaxy S Advance I9070 General] KINGbabasula:
We don't have recovery partition. Probably the error isn't related to this but anyway you wouldn't be able to flash it. Our recovery is packed in the ramdisk

I meant cm-10 branch. Jellybean is another one :)

Inviato dal mio GT-I9070 utilizzando Tapatalk
[Galaxy S Advance I9070 General] Freewaymad:
I could be wrong, but I thought that was only on some phones, not all. I am building this from the source.:confused:

Thanks for the reply

---------- Post added 11th March 2014 at 12:00 AM ---------- Previous post was 10th March 2014 at 11:46 PM ----------

I am compiling CM 10.2 on Ubuntu 12.04 Precise.

Thanks
[Galaxy S Advance I9070 General] vickyushu:
cherry-pick fc2ac71d0d9e147c607bff9371fe2ef25d8470af

error: could not apply fc2ac71... verifier: Bypass monitor-{enter,exit} depth checks

hint: after resolving the conflicts, mark the corrected paths

hint: with 'git add <paths>' or 'git rm <paths>'

hint: and commit the result with 'git commit'

Recorded preimage for 'runtime/verifier/register_line.cc'

git cherry-pick fc2ac71d0d9e147c607bff9371fe2ef25d8470af

error: 'cherry-pick' is not possible because you have unmerged files.

hint: Fix them up in the work tree,

hint: and then use 'git add/rm <file>' as

hint: appropriate to mark resolution and make a commit,

hint: or use 'git commit -a'.

fatal: cherry-pick failed

what to do now any solution

---------- Post added at 07:39 PM ---------- Previous post was at 07:37 PM ----------

runtime/verifier/register_line.cc: needs merge

error: you need to resolve your current index first

how to resolve this
[Galaxy S Advance I9070 General] Flo0008:
Because of the first part of "cherry picking" -failed:

Delete the folder you applied the patches in your working direction and repo sync them ...

If you applied the patches in frameworks/base do this: rm -rf frameworks/base && cd frameworks && repo sync base

So, now you have to apply all the patches manually (Got to the github repository of the commits) and do all addings/deletions manually. I know, this is so so much work, but there is no second solution for this (I had to do it in 2 Roms already)

Second part:

Maybe I am false but I think that file is missing or something ... Or the more possible thing is this issue is related to the error before (If cherry pick fails, sometimes there are added additional, not needed lines to a file - like

<<<<<<HEAD xyzxyz

>>>>>>HEAD commit-number

Is possible, please correct me if I am false.

Hope I could help.
[Galaxy S Advance I9070 General] vickyushu:
lunch full_janice-userdebug

build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/janice/full_janice.mk]]: "vendor/cm/config/common_full_phone.mk" does not exist. Stop.

WARNING: Trying to fetch a device that's already there

WARNING: device/samsung/janice/omni.dependencies file not found

build/core/product_config.mk:227: *** _nic.PRODUCTS.[[device/samsung/janice/full_janice.mk]]: "vendor/cm/config/common_full_phone.mk" does not exist. Stop.

** Don't have a product spec for: 'full_janice'

** Do you have the right repo manifest?
[Galaxy S Advance I9070 General] vickyushu:
Thanks
[Galaxy S Advance I9070 General] Flo0008:
So, firstly go in device/janice folder and rename cm.dependencies to omni.dependencies. Then rename cm.mk to omni.mk. Look now into the renamed file omni.mk and control and change all in this file mentioned paths to the right one .. Like this path:

vendor/cm/config/common_full_phone.mk

Look into the vendor folder (in your project folder) and change it like this:

vendor/omni/config/common_full_phone.mk

But this file can have another name like this, too:

vendor/omni/config/full_phone.mk

So control all paths from omni.mk if they are there or perhaps have another name.

You understand what i mean?
[Galaxy S Advance I9070 General] vickyushu:
i did change above but i didn't understand the control part can u clearify it more

---------- Post added at 06:25 AM ---------- Previous post was at 06:20 AM ----------

build/core/product_config.mk:222: *** Can not locate config makefile for product "omni_janice". Stop.
[Galaxy S Advance I9070 General] Flo0008:
If you open your omni.mk you can see lots of different paths, right? There is a path for the bootanimation, ... ... So, now your work is it to change the path especially for your OMNI Rom ... If there is a path like "vendor/cm/bootanimation" in your omni.mk, change it to "vendor/omni/bootanimation"

Now look into your vendor folder (it is in your project folder) ... So, now look into vendor/omni/bootanimation ... Is this file here, so you can change the next path ...

You have to control if the files exist in your vendor folder, they can have other names as mentioned in the omni.mk, too ...

Ok?
[Galaxy S Advance I9070 General] vickyushu:
see this
[Galaxy S Advance I9070 General] Flo0008:
Please a pick from the config folder here too
[Galaxy S Advance I9070 General] BOOTMGR:
I think jellybean is the name of CM10 branch.

Anyways i solved those issues, CM10 device tree by TeamCanjica is broken (missing many blobs etc). Kernel was not booting because jellybean branch didn't disabled CONFIG_U8500_SHRM_ENABLE_FEATURE_SIGNATURE_VERIFICATION.

I got some progress on CM10 but one thing bothers me is

E/ENSWrapper( 1836): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.VFM.H264Dec h=0x41c6e230 cParameterName=OMX.google.android.index.useAndroidNativeBuffer2 IndexType=unknown OMX_INDEXTYPE [ 0x00000023 ]
E/ENSWrapper( 1842): return OMX_ErrorNotImplemented - GetExtensionIndex OMX.ST.AFM.pcmprocessing.spl h=0x4251af80 cParameterName=STE.ADM IndexType=unknown OMX_INDEXTYPE [ 0x1562c559 ]

are those errors?

Those appear on screen when video is playing. Video is working fine no issue at all.

But still want to know what's that?
[Galaxy S Advance I9070 General] AntaresOne:
On CM10 OpenMAX was never fully fixed
[Galaxy S Advance I9070 General] KINGbabasula:
That's an error but can be ignored
[Galaxy S Advance I9070 General] vickyushu:
Oracle JDK 6 is NOT installed.

dpkg: error processing oracle-java6-installer (--configure):

subprocess installed post-installation script returned error exit status 1

Setting up gsfonts-x11 (0.22) ...

Errors were encountered while processing:

oracle-java6-installer

E: Sub-process /usr/bin/dpkg returned an error code (1)

why i'm getting this error
[Galaxy S Advance I9070 General] Flo0008:
Do the first steps of the guide again ...
[Galaxy S Advance I9070 General] vickyushu:
delete
[Galaxy S Advance I9070 General] fbs:
Is this tutorial still up-to-date? I'm thinking in following it to build a pure cm11..
[Galaxy S Advance I9070 General] Chirag_Galani:
[MENTION=5093942]KINGbabasula[/MENTION]

Add this line in ur local manifest.

<project path="packages/apps/DeviceSettings" name="TeamCanjica/android_packages_apps_DeviceSettings" revision="master" />

Also, change kernel line to the following:

<project path="kernel/samsung/u8500" name="TeamCanjica/Samsung_STE_Kernel" revision="3.0.31" />
[Galaxy S Advance I9070 General] fbs:
Fetching projects: 100% (454/454), done.

Syncing work tree: 70% (318/454) Traceback (most recent call last):

File "/home/hbb/cm11/.repo/repo/main.py", line 408, in <module>

_Main(sys.argv[1:])

File "/home/hbb/cm11/.repo/repo/main.py", line 384, in _Main

result = repo._Run(argv) or 0

File "/home/hbb/cm11/.repo/repo/main.py", line 143, in _Run

result = cmd.Execute(copts, cargs)

File "/home/hbb/cm11/.repo/repo/subcmds/sync.py", line 690, in Execute

project.Sync_LocalHalf(syncbuf)

File "/home/hbb/cm11/.repo/repo/project.py", line 1158, in Sync_LocalHalf

lost = self._revlist(not_rev(revid), HEAD)

File "/home/hbb/cm11/.repo/repo/project.py", line 2178, in _revlist

return self.work_git.rev_list(*a, **kw)

File "/home/hbb/cm11/.repo/repo/project.py", line 2335, in rev_list

p.stderr))

error.GitError: TeamCanjica/Samsung_STE_Kernel rev-list ('^8315856dcaa292a18c3740e0c597edd42f78fe72', 'HEAD', '--'): fatal: bad object 8315856dcaa292a18c3740e0c597edd42f78fe72
[Galaxy S Advance I9070 General] Freewaymad:
Upgrade From ICS4.0 bootloader to JB4.3 bootloader in an OTA

Hi,

Maybe this is not the right place to ask, but I hope someone can help me. How do I customize the update script to update u-boot? Because android only upgrades the boot.img, system.img, and recovery partitions, the automatically generated update package does not support upgrading bootloader. So...would I unzip the update.zip, and then modify the updater_script by implementing the following operations:

# Write u-boot to 1K position.

# u-boot binary should be a no padding uboot!

# For eMMC(iNand) device, needs to unlock boot partition.

ui_print("writting u-boot...");

package_extract_file("files/u-boot-no-padding.bin", "/tmp/u-boot-no-padding.bin");

sysfs_file_write("class/mmc_host/mmc0/mmc0:0001/boot_config", "1");

simple_dd("/tmp/u-boot-no-padding.bin", "/dev/block/mmcblk0", 1024);

sysfs_file_write("class/mmc_host/mmc0/mmc0:0001/boot_config", "8");

show_progress(0.1, 5);

then put the "u-boot-no-padding.bin" in the update package and zip it? Should this script be at the beginning of the updater_script or the end?

:confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused::confused:

Please help.

Thanks,
[Galaxy S Advance I9070 General] shut_down:
For what phone is it? Better find some thread for your phone, we do not have ICS so I guess that you will not find answer here.
[Galaxy S Advance I9070 General] Freewaymad:
This a Freescale tablet and I just need a little help with updater-script to get it to flash in an OTA. There is not much, if any, support for this. I have built two different roms from the source for this based on JB4.3 and I am stuck on getting the bootloader updated. I've tried to flash it using TWRP, but that did not work. Upon some research, that is how I came to find the it is a matter of the bootloader.

Thank you for your reply.
[Galaxy S Advance I9070 General] Prodean:
error: Cannot fetch TeamCanjica/Samsung_STE_Kernel00 KiB/s

warn: --force-broken, continuing to sync

fatal: unable to access 'https://github.com/DirtyUnicorns-KitKat/TeamCanjica/Samsung_STE_Kernel/': Could not resolve host: github.com

I got error while trying to sync repo for building Dirty Unicorns... Please help!!
[Galaxy S Advance I9070 General] Prodean:
fetch="git://github.com/" />

Don't you have to add this into the local manifest.xml? +Kingbabasula
[Galaxy S Advance I9070 General] t4n017:
You're trying to access: https://github.com/DirtyUnicorns-KitKat/TeamCanjica/Samsung_STE_Kernel/ which doesn't exists.

It has to be: https://github.com/TeamCanjica/Samsung_STE_Kernel
[Galaxy S Advance I9070 General] Prodean:
but I had followed the whole guild carefully...
[Galaxy S Advance I9070 General] t4n017:
Copy your local_manifest so we can take a look ..
[Galaxy S Advance I9070 General] Prodean:
<?xml version="1.0" encoding="UTF-8"?>

<manifest>

<project path="kernel/samsung/u8500" name="TeamCanjica/Samsung_STE_Kernel" revision="3.0.31" />

<project path="device/samsung/janice" name="TeamCanjica/android_device_samsung_janice" revision="cm-11.0" remote="github" />

<project path="device/samsung/u8500-common" name="TeamCanjica/android_device_samsung_u8500-common" revision="cm-11.0" remote="github" />

<project path="hardware/u8500" name="TeamCanjica/android_hardware_u8500" revision="cm-11.0" remote="github" />

<project path="vendor/samsung/u8500-common" name="TeamCanjica/android_vendor_samsung_u8500-common" revision="cm-11.0" remote="github" />

<project path="patches" name="KINGbabasula/STE_patches" revision="cm-11.0" remote="github" >

<copyfile src="patch.sh" dest="patch.sh" />

</project>

<project path="packages/apps/DeviceSettings" name="TeamCanjica/android_packages_apps_DeviceSettings" revision="master" />
[Galaxy S Advance I9070 General] t4n017:
You forgot remote="github" on kernel, probably is that.

Also, the OP is a bit outdated, and the patches too. Send me a PM with the rom you're trying to build and I'll send you the right patches and point other changes you should make (you'll need some changes if you aren't building CM).
[Galaxy S Advance I9070 General] Prodean:
Ohhh! Thanks !!!
[Galaxy S Advance I9070 General] Toni5830:
As you all know, we can now compile janice kernel with GCC4.7 and 4.8, so I thought that I could compile something with these new versions, I googled a bit how to change gcc for rom compiling and I saw that I need to edit this line in envsetup.sh

export ANDROID_EABI_TOOLCHAIN=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/i686-linux-android-4.6/bin
;;
[COLOR="Red"]arm) toolchaindir=arm/arm-linux-androideabi-4.6/bin[/COLOR]
;;
mips) toolchaindir=mips/mipsel-linux-android-4.6/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac

But few lines below you can see

case $ARCH in
arm)
[COLOR="Red"]toolchaindir=arm/arm-eabi-4.6/bin[/COLOR]
if [ -d "$gccprebuiltdir/$toolchaindir" ]; then
export ARM_EABI_TOOLCHAIN="$gccprebuiltdir/$toolchaindir"
ARM_EABI_TOOLCHAIN_PATH=":$gccprebuiltdir/$toolchaindir"
fi
;;
mips) toolchaindir=mips/mips-eabi-4.4.3/bin
;;
*)
# No need to set ARM_EABI_TOOLCHAIN for other ARCHs
;;
esac

so a diffferent toolchain! I noticed this many time ago, I looked for their differences and I also used arm-linux-androideabi toolchain to build a kernel for stock rom..it booted but it had some problem (wifi not working, probably a module problem...)

So my questions are:

1) is arm-linux-androideabi toolchain used to build rom while

arm-eabi

is used to build

only

kernel??

2) should I change arm-linux-androideabi-4.6 with arm-linux-androideabi-4.8 and arm-eabi-4.6 with arm-eabi-4.8 or only the first one as I read here on xda?? (but not only, for example here https://github.com/crossfire77/linaro-4.8 or here http://xdaforums.com/galaxy-nexus/general/howto-build-rom-linaro-toolchain-t1988315 (I don't want to use Linaro!! these link are an example for the instructions))

3) if answer to question #2 is "only first one as you read in the link you provided", then which one should I use? and why are there 2 toolchains if I use only 1?? else ignore this :D:D

Hope I was clear

Thank you :good:
[Galaxy S Advance I9070 General] KINGbabasula:
To change toolchain for the kernel you shouldn't edit envsetup.sh but in the device tree you have to put a flag i don't remember now in BoardConfig.mk

1. Probably but i'm not sure

2. You should change only arm-eabi

3. You should use arm-eabi

Inviato dal mio GT-I9070 utilizzando Tapatalk
[Galaxy S Advance I9070 General] Flo0008:
[MENTION=4769087]Toni5830[/MENTION] ...

To compile the kernel with any toolchain add this in device/Samsung/janice in BoardConfig.mk at the end:

# Kernel

TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-linaro-4.8

Instead 4.8 you can choose your toolchain :)

Regards, Flo
[Galaxy S Advance I9070 General] Toni5830:
Thanks

Anyway changing those lines in envsetup.sh did the trick, kernel compiled with toolchain I selected (I'm using it right now), I guess androideabi builds ROM, while arm-eabi is for kernel..

Sent from Italy using Tapatalk
[Galaxy S Advance I9070 General] M132:
I'm trying to compile CM 11 (git://github.com/CyanogenMod/android.git -b cm-11.0), but patch.sh gives me these errors at the end:

Patching frameworks/base

Patching frameworks/av
error: patch failed: include/media/stagefright/OMXCodec.h:107
error: include/media/stagefright/OMXCodec.h: patch does not apply

Patching frameworks/native
error: patch failed: include/binder/Parcel.h:102
error: include/binder/Parcel.h: patch does not apply
error: patch failed: libs/gui/GLConsumer.cpp:140
error: libs/gui/GLConsumer.cpp: patch does not apply
error: patch failed: include/binder/Parcel.h:28
error: include/binder/Parcel.h: patch does not apply

Applying vibrator fix

Patching system/core
cp: cannot create „system/core/system_core.patch”: No such file or directory
bash: cd: system/core: No such file or directory
fatal: can't open patch 'system_core.patch': No such file or directory
rm: cannot remove „system_core.patch”: No such file or directory
Patching packages/services/Telephony
cp: cannot stat on „patches/packages_services_Telephony.patch”: No such file or directory
bash: cd: packages/services/Telephony: No such file or directory
fatal: can't open patch 'packages_services_Telephony.patch': No such file or directory
rm: cannot remove „packages_services_Telephony.patch”: No such file or directory

Make throws even more errors (error: 'android::Flattenable' is not a template type). How can I fix it? :(

EDIT: After running ". patch.sh" current working directory gets changed to /
[Galaxy S Advance I9070 General] Flo0008:
[MENTION=4769087]Toni5830[/MENTION]

Is it possible that you try toolchain 4.7 or 4.8, because building kernel fails for me and I cant find the error in terminal ...

Would be awesome :)
[Galaxy S Advance I9070 General] M132:
I've managed to fix these patches myself :laugh: For those, who face the same issues, I made a repository with fixed patches. To use it, open your local manifest and change KINGbabasula/STE_patches to M132/STE_patches on this line:

<project path="patches" name="KINGbabasula/STE_patches" revision="cm-11.0" remote="github" >

EDIT: [HIGHLIGHT]These patches are also outdated![/HIGHLIGHT] In local manifest change

<project path="patches" name="M132/STE_patches" revision="cm-11.0" remote="github" >
<copyfile src="patch.sh" dest="patch.sh" />

to

<project path="patches" name="TeamCanjica/BuildBot" revision="master" remote="github" >

Remove patches directory, resync, and instead of . patch.sh use REPO_BRANCH="cm-11.0" DEVICE="janice" patches/cherry-pick.sh
[Galaxy S Advance I9070 General] Toni5830:
I successfully built a kernel for Miui using gcc 4.8; I'm using ste_kernel sources from TC

Did you merge Kingbabasula's fixes to build with gcc4.7 and 4.8?

Sent from Italy using Tapatalk
[Galaxy S Advance I9070 General] Flo0008:
They are already implemented in TC Samsung STE kernel .. But it worked already for me too ... Thank you :)

Gesendet von meinem GT-I9070 mit Tapatalk
[Galaxy S Advance I9070 General] M132:
No matter which toolchain I use, I always end up with a broken kernel. Trying to boot results in freeze at the "Samsung GALAXY S Advance GT-I9070" screen. No adb, no boot animation, no reboots, just nothing. :crying:
[Galaxy S Advance I9070 General] KINGbabasula:
You probably didn't include ramdisk in your builds

Inviato dal mio GT-I9070 utilizzando Tapatalk
[Galaxy S Advance I9070 General] M132:
How to do it? I tried making whole ROM, and just make -j8 bootimage. Both seem to build ramdisk, because I can find ramdisk.cpio file, charger, recovery executables and battery images in out directory. I am missing something? :rolleyes:
[Galaxy S Advance I9070 General] Flo0008:
To make a whole rom do

make -j8 otapackage

;)
[Galaxy S Advance I9070 General] M132:
I know, by writing "I tried making whole ROM, and just make -j8 bootimage." I meant I did both, otapackage and bootimage.
[Galaxy S Advance I9070 General] Flo0008:
If you build a whole rom you only have to type make -j8 otapackage ... you will get a .zip file with everything else, kernel, modules, apps, ... Everything is in there ...
[Galaxy S Advance I9070 General] M132:
I know.... Kernel from otapackage does NOT work.
[Galaxy S Advance I9070 General] Flo0008:
Did you get any error during building? What rom do you build?
[Galaxy S Advance I9070 General] M132:
CM 11. I had some errors with Mali driver (because gcc was called with -DSVN_REV=Unversioned directory argument), so I replaced svnversion with an empty shell script and it compiled correctly.
[Galaxy S Advance I9070 General] Flo0008:
Which toolchain did you use ... and can you look into build/core/tasks/kernel.mk: Did you change the toolchain path (with linux-x86) to this path: https://github.com/flo-slim/build/commit/241f6ca99db678093cf15915fb30a1280efa13ec
[Galaxy S Advance I9070 General] M132:
I didn't. I tried with prebuilt/linux-x86/toolchain/arm-eabi-4.4.3 and Linaro arm-eabi-4.9.
[Galaxy S Advance I9070 General] Flo0008:
For the beginning, I prefer to use the default things ... don't use any other toolchain and you will see your build works ...

Surely you have to download the 4.9 toolchain, the arm-eabi-4.9 and arm-androideabi-4.9 toolchain ...

1. Change the toolchain path like I did it in the link above!

2. Did you download the GCC 4.9 toolchain (I mean did you add it in your manifest in . repo)?

3. If you want to use GCC 4.9 do this things:

https://github.com/flo-slim/build/commit/e3371318d635fba4b307c99b5c46c0f6451cb82f

Instead of 4.8 you have to type 4.9

4. Add this two lines at the end of device/samsung/janice/BoardConfig.mk:

# Kernel toolchain

TARGET_KERNEL_CUSTOM_TOOLCHAIN := arm-eabi-4.9

5. Open build/core/combo/TARGET_linux-arm.mk

Change this in line 38:

TARGET_GCC_VERSION := 4.7

TARGET_GCC_VERSION := 4.9

This changes are needed for another toolchain, hope I forgot nothing ...
[Galaxy S Advance I9070 General] M132:
That's exactly what I did... I downloaded Linaro toolchain from releases.linaro.org and replaced stock one with it in both, prebuilt/linux-x86/toolchain and prebuilts/gcc/linux-x86/arm directories. Then I changed BoardConfig.mk and TARGET_linux-arm.mk, and compiled whole ROM with make -j8 otapackage. After that, I wiped data, boot, system and cache partitions and flashed my freshly compiled ROM with CWM. Rebooted, and nothing, phone got stuck on "Samsung Galaxy S Advance GT-I9070" screen, I could neither enter recovery nor debug it with adb. I flashed another kernel with Heimdall and it worked, so I thought that toolchain might be too new or something, and reverted changes I made. I recompiled whole ROM again, this time with stock toolchains, but this one behaved the same.
[Galaxy S Advance I9070 General] KINGbabasula:
Don't use 4.9 toolchains. They are still not working. Try 4.7 or 4.8
[Galaxy S Advance I9070 General] mhmod222:
what is cache directory

and where it should be?
[Galaxy S Advance I9070 General] Flo0008:
ccache is a kind of compilation tool, it acts like a compiler cache which allows you to speed up rebuilds, trust me, it really gives you lots of improvements in the building speed of your pc ... I prefer to make on your Ubuntu or similar operating system to make a folder called 'android', there you add your wished roms like 'cm-11.0' or so and there you can make ccache ... you only have to change the path of ccache right (where it is located)

CCACHE_DIR='path to your ccache folder in android folder'
[Galaxy S Advance I9070 General] Prodean:
I got some error when building.. here is the error.log : https://drive.google.com/file/d/0B0afRmUYrYpPbUlZWWxsN2ViSWc/edit?usp=sharing

makefile :https://drive.google.com/file/d/0B0afRmUYrYpPdDJZZm1CRnI4c3c/edit?usp=sharing

outlog :https://drive.google.com/file/d/0B0afRmUYrYpPX0RRWm1YZEtqTFk/edit?usp=sharing