yashsingh1/xdaforums huggingface dataset:
[Android Q&A, Help & Troubleshooting] speed_bot:
libz.so.1: cannot open shared object file: No such file or directory
make: *** [/root/cm10/out/host/linux-x86/obj/STATIC_LIBRARIES/libmincrypt_intermediates/rsa.o] Error 1

a lib is missing compile after make clean and make clobber that should fix it afaik..
[Android Q&A, Help & Troubleshooting] mikshepard:
Thanks, I ran the make clean and make clobber, then repo sync, . build/envsetup.sh, brunch jewel, and got these same results again:

make: *** No rule to make target `/root/cm10/out/target/product/jewel/obj/lib/libacdbloader.so', needed by `/root/cm10/out/target/product/jewel/obj/SHARED_LIBRARIES/libalsa-intf_intermediates/LINKED/libalsa-intf.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /root/cm10/out/target/product/jewel/obj/SHARED_LIBRARIES/libalsa-intf_intermediates/import_includes

Again, pulling that file from my phone and putting in the directory only caused similar errors for other files. Does my local_manifest.xml look right?

<manifest>
<project name="CyanogenMod/android_device_htc_jewel" path="device/htc/jewel" remote="github" revision="jellybean"/>
<project name="CyanogenMod/android_device_htc_msm8960-common" path="device/htc/msm8960-common" remote="github" revision="jellybean"/>
<project name="CyanogenMod/android_kernel_htc_msm8960" path="kernel/htc/msm8960" remote="github" revision="jellybean"/>
</manifest>

Thanks for any help on this, I'm bashing my head trying to figure this out and your guy's input is a big help!

-Mike
[Android Q&A, Help & Troubleshooting] speed_bot:
i cant conifrm about the manifest part but copy paste that lib into that folder for time being...and include it in your vendors..
[Android Q&A, Help & Troubleshooting] ktempleton:
The manifest looks fine to me

Did you do the extract files sh from your phone?
[Android Q&A, Help & Troubleshooting] cbucz24:
ok, so i switched to my other running project and i actually got it to finish completely. just wont boot now.

http://pastebin.com/r5KhLWpx

few background errors i found, that i manually added to get it to install.

upon finish, it was missing files...

bootanimation.zip

backuptool.sh

backuptool.functions

all three of these were missing from finished build?
[Android Q&A, Help & Troubleshooting] speed_bot:
did you lunch or made brunch?
[Android Q&A, Help & Troubleshooting] cbucz24:
lunch...ive never used brunch...ive searched it and still cant really see a use for it

since the build was so long...obviously i cant read the output from start to finish. where would i start to find out why it didnt add those files? and obviously from there, one would assume it is also missing more and thats why it wont boot..but this rom is a lot better start. TeamBAKED i think do a great job going thru things.

At this point, not sure if i will ever get my pacman built...guys on the PA pages are saying updates not getting done and that code is partially outdated and broken, ive not seen an update on pacman's repo in months either...
[Android Q&A, Help & Troubleshooting] ktempleton:
Did you have errors while you were building if you did i would make clean and have another go at it
[Android Q&A, Help & Troubleshooting] speed_bot:
no bro..i need the reason for the services crashing..so get the initial part of log
[Android Q&A, Help & Troubleshooting] ktempleton:
Just a heads up guys when you post a log cat we need the whole log what you may not see as important may be the cause of your issue use paste bin or something similar

---------- Post added at 08:22 AM ---------- Previous post was at 08:19 AM ----------

Hey speed bot I'm building 4.2 and i keep running into no resource identifier found for attribute blah blah. And it seems to be on all of the XML under packages apps any idea how i can fix this
[Android Q&A, Help & Troubleshooting] speed_bot:
i know the problem are with overlays...assuming you are using cm10's device config which has overlays for cm10 not 10.1 thats the only problem...so get overlays from exisiting 4.2 device trees one which suits your res mdpi or hdpi
[Android Q&A, Help & Troubleshooting] cbucz24:
yea, there was some...looked like it had some initial errors related to bluetooth. im swapping out their files with mine now and ill have another go at it in a few..

it was in a bootloop, and i dont know if you noticed but i said this was my first finished build...lol...this log was all that it had, just kept repeating so i waited for it to start over and grabbed it
[Android Q&A, Help & Troubleshooting] ktempleton:
I'm using a tree from 10.1 so maybe they just haven't integrated them yet
[Android Q&A, Help & Troubleshooting] speed_bot:
so your device already has a 10.1 tree..could u plz post your erros ?
[Android Q&A, Help & Troubleshooting] ktempleton:
Actually the device is still in staging
[Android Q&A, Help & Troubleshooting] demkantor:
Have you added your device tree? Do you have cm_a110 in device/micromax/a110 and vendor/micromax/a110 ?
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
no. But there is cm.mk in that. What should be there in that file?
[Android Q&A, Help & Troubleshooting] ravike14:
Why doesn't my rom executes the neccesary files in system/bin.. Even tho I've added the neccesary lines in ramdisk still none of my files get executed.. The ks, qcks , akmd ewmutzd and rmt_storage bin files..

This is slightly off topic, sorry for that, but it's really annoying cuz I tried everything I can and I'm out of options now..
[Android Q&A, Help & Troubleshooting] demkantor:
You are going to need your full device tree, this can be a long and difficult process if some hasn't already made one. I would suggest to first search github and Google to see if anyone has created one for your device, if not, then there are some guides to do so but expect a difficult road ahead.

Also, if there isn't a premade device tree than consider simply porting a ROM with a kitchen or other various methods from a similar device, may get you what you want but be much less time consuming

Best of luck!
[Android Q&A, Help & Troubleshooting] shimp208:
Figured I'd try and help you a little as well! As for what should be in the cm.mk file this is an example taken from the Samsung Nexus 10 (Manta) that you can use as an example:

# Resolution values for bootanimation
TARGET_SCREEN_HEIGHT := 1600
TARGET_SCREEN_WIDTH := 2560

# Release name
PRODUCT_RELEASE_NAME := Nexus10

# Inherit some common CM stuff.
$(call inherit-product, vendor/cm/config/common_full_tablet_wifionly.mk)

# Enhanced NFC
$(call inherit-product, vendor/cm/config/nfc_enhanced.mk)

# Inherit device configuration
$(call inherit-product, device/samsung/manta/full_manta.mk)

## Device identifier. This must come after all inclusions
PRODUCT_DEVICE := manta
PRODUCT_NAME := cm_manta
PRODUCT_BRAND := Google
PRODUCT_MODEL := Nexus 10
PRODUCT_MANUFACTURER := samsung

PRODUCT_BUILD_PROP_OVERRIDES += \
PRODUCT_NAME=mantaray \
BUILD_FINGERPRINT=google/mantaray/manta:4.4.2/KOT49H/937116:user/release-keys \
PRIVATE_BUILD_DESC="mantaray-user 4.4.2 KOT49H 937116 release-keys"

Did you use the official Cyanogenmod porting guide on their wiki page to setup the initial device tree? If not I would recommend starting over and following those instructions to get an idea of what else you will need to port to your device. Let me know if you have any question's I am by no means a porting or compiling expert but I'll be happy to help you as best I can from what I've learned :good:.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
I have setup the whole device trees. Here they are:

https://github.com/Ateekujjawal/android_device_micromax_a110

And yes I used CyanogenMod's official guide on porting.
[Android Q&A, Help & Troubleshooting] Recon Freak:
"device/wiko/stairway/device_a110.mk" Is this folder available in your source and what's in it?
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Its device/micromax/a110/device_a110.mk.

And yes it is available.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Please reply and help me. That is the wrong path. How can I change it. There is no line referring to it.
[Android Q&A, Help & Troubleshooting] Recon Freak:
You have another line calling for it where it should be. Just delete that line.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Where is it bro? Please tell me.
[Android Q&A, Help & Troubleshooting] maniknarang:
Hello, Can anybody please help me out? I posted 3 days ago, but no one did help...!!!

I am building cm11 for HTC Desire C...Here is the error which I am getting:

brunch cm_golfu-userdebug -j8
including vendor/cm/vendorsetup.sh
Trying dependencies-only mode on a non-existing device tree?

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140326-UNOFFICIAL-golfu
TARGET_PRODUCT=cm_golfu
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a5
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-17-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/home/manik/Source/out
============================================

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.4.2
CM_VERSION=11-20140326-UNOFFICIAL-golfu
TARGET_PRODUCT=cm_golfu
TARGET_BUILD_VARIANT=userdebug
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a-neon
TARGET_CPU_VARIANT=cortex-a5
HOST_ARCH=x86
HOST_OS=linux
HOST_OS_EXTRA=Linux-3.11.0-17-generic-x86_64-with-Ubuntu-13.10-saucy
HOST_BUILD_TYPE=release
BUILD_ID=KOT49H
OUT_DIR=/home/manik/Source/out
============================================
/home/manik/Source/out/target/product/golfu/obj/APPS/SignatureTest_intermediates
find: `src': No such file or directory
No private recovery resources for TARGET_DEVICE golfu
make -C kernel/htc/golfu O=/home/manik/Source/out/target/product/golfu/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/manik/Source/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-" headers_install
make[1]: Entering directory '/home/manik/Source/kernel/htc/golfu'
host C++: clang <= external/clang/tools/driver/cc1_main.cpp
host C++: clang <= external/clang/tools/driver/cc1as_main.cpp
make: *** No rule to make target 'device/htc/golfu/init.golfu.usb.rc', needed by '/home/manik/Source/out/target/product/golfu/root/init.golfu.usb.rc'. Stop.
make: *** Waiting for unfinished jobs....
host C++: clang <= external/clang/tools/driver/driver.cpp
CHK include/linux/version.h
make[1]: Leaving directory '/home/manik/Source/kernel/htc/golfu'

Something like init.golfu.usb.rc...

Please help!!!:D
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
I am getting this error while building cm11 for unsupported device Micromax A110 using lunch :

Which would you like? [aosp_arm-eng] 13

device/micromax/a110/device_a110.mk:104: *** commands commence before first target. Stop.

Device a110 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).

Repository for a110 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.

device/micromax/a110/device_a110.mk:104: *** commands commence before first target. Stop.

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

** Do you have the right repo manifest?
[Android Q&A, Help & Troubleshooting] HTCDreamOn:
[MENTION=3570463]brajesh.sharma87[/MENTION] there will probably be a commit in Purity where a line about isPhone is added before the commit you're trying to pick... Sorry I'm being vague but I don't understand java; This is what it means though, there is no is phone activity yet, it needs to be added. (Sorry if activity was the wrong word) so just look for this commit.

I know how to fix the content resolver issues but I gotta go school now so I may be able to help you with them later :) I've had those errors before
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Hi everyone, I am building cm11 for unsupported device a110. When I try to build using brunch, I get this error -

device/micromax/a110/device_a110.mk:104: *** commands commence before first target. Stop.
Device a110 not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Repository for a110 not found in the CyanogenMod Github repository list. If this is in error, you may need to manually add it to your local_manifests/roomservice.xml.
device/micromax/a110/device_a110.mk:104: *** commands commence before first target. Stop.

** Don't have a product spec for: 'cm_a110'
** Do you have the right repo manifest?
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Anybody there to help???
[Android Q&A, Help & Troubleshooting] Recon Freak:
Send me your vendor files and I'll try to build it on my machine and figure it out.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Here is the link to my Github , you will find all repositories there. Device codename is a110.
[Android Q&A, Help & Troubleshooting] Olivier:
You may want to revert this commit.

Gesendet von meinem Xperia S mit Tapatalk
[Android Q&A, Help & Troubleshooting] aweosomeabhijeet:
Anyone here can help me up with this?

http://pastebin.com/LzF7tSHS

My device : Motorola XT530, first build for the device. No solutions found to this yet.
[Android Q&A, Help & Troubleshooting] Gnome:
You got a lot of undefined references that can't be found. Check out the file.
[Android Q&A, Help & Troubleshooting] F-L-Y-E-R:
Just a quick question, if I sync the repo from 'stable/cm-11.0' does it means I'll build SNAPSHOT-M5? If yes is it normal that it isn't included in the filename after I write "source build/envsetup.sh"? Thanks.
[Android Q&A, Help & Troubleshooting] mcgi5sr2:
Hi Awida777

the only way I can get around this is by using hte Evervolv Media-legacy tree. Did you find a better solution?
[Android Q&A, Help & Troubleshooting] kernelhackx:
Afaik the stable/cm-11.0 is the snapshot but M builds wont reflect if you build it, but for sure if you repo init the stable branch you'll be building the snapshot.
[Android Q&A, Help & Troubleshooting] lenkyun:
boot.img seems to not working

I compiled cyanogenmod. But boot.img seems to not working

How can I detect where make it not work.
[Android Q&A, Help & Troubleshooting] kernelhackx:
Why? It doesn't boot? What do you mean by its not working? If you'll be more specific alot can help. :)
[Android Q&A, Help & Troubleshooting] lenkyun:
Yes, It seems not boot.

I had tried to put some init file but it's still not boot.
[Android Q&A, Help & Troubleshooting] kernelhackx:
Did you do something with the kernel? like building it with -O3, etc? And are you using custom toolchains?
[Android Q&A, Help & Troubleshooting] lenkyun:
I use kernel from ZTE Blade V kernel source that has the same CPU as my phone and the same manufacturer.

And I use only toolchains that come with CM 10.1.

Last. My device has no one made device tree. And this is my first time to port android.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Toolchains don't come with rom until that team provides it. To check your Toolchain version, Simply type "gcc -v" in terminal without quotes. You have to install this Toolchain as a required packages.
[Android Q&A, Help & Troubleshooting] lenkyun:
OK, This is result from "gcc -v"

Using built-in specs.
COLLECT_GCC=gcc
COLLECT_LTO_WRAPPER=/usr/lib/gcc/x86_64-linux-gnu/4.6/lto-wrapper
Target: x86_64-linux-gnu
Configured with: ../src/configure -v --with-pkgversion='Ubuntu/Linaro 4.6.3-1ubuntu5' --with-bugurl=file:///usr/share/doc/gcc-4.6/README.Bugs --enable-languages=c,c++,fortran,objc,obj-c++ --prefix=/usr --program-suffix=-4.6 --enable-shared --enable-linker-build-id --with-system-zlib --libexecdir=/usr/lib --without-included-gettext --enable-threads=posix --with-gxx-include-dir=/usr/include/c++/4.6 --libdir=/usr/lib --enable-nls --with-sysroot=/ --enable-clocale=gnu --enable-libstdcxx-debug --enable-libstdcxx-time=yes --enable-gnu-unique-object --enable-plugin --enable-objc-gc --disable-werror --with-arch-32=i686 --with-tune=generic --enable-checking=release --build=x86_64-linux-gnu --host=x86_64-linux-gnu --target=x86_64-linux-gnu
Thread model: posix
gcc version 4.6.3 (Ubuntu/Linaro 4.6.3-1ubuntu5)

I have "arm-eabi-4.4.3" in kernel directory.

But I use it only for compiling kernel. // I followed the kernel compiling guide

I don't know how to setup it for using in full Cyanogenmod compile.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
You can find instructions on how to compile cm kernel on the cyanogenmod oldwiki.
[Android Q&A, Help & Troubleshooting] lenkyun:
http://oldwiki.cyanogenmod.org/wiki/Building_Kernel_from_source

I try to get config.gz and compile with kernel source and I got many error.

Then I compile it with msm7627a-perf_defconfig and It's have no error.

Maybe I have to try another defconfig
[Android Q&A, Help & Troubleshooting] lenkyun:
I have a question.

If kernel can make CWM work.

Does It mean that the same kernel should make boot.img work If there's no problem in ramdisk?
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Boot.img is the kernel!!!!!
[Android Q&A, Help & Troubleshooting] shimp208:
Adding on to what has been said, I would assume you are asking if the kernel you used to get Clockworkmod Recovery working on your device works then to get a complete build of Cyanogenmod running on your device. The answer to that question is usually, although you may have to pull logs to tweak things booting fully.
[Android Q&A, Help & Troubleshooting] lenkyun:
OK I'm misunderstand.

So, The kernel that work with CWM doesn't mean that it will work with system.

Then I have other question.

When I try to boot, it will stuck at bootloader screen.

But with no additional init, I get "123456789ABCDEF unauthorized" from adb.

When I flash the stock boot.img back. It can get into system and "adb logcat" work.

It still has an error But more worry about kernel.

EDIT :

Change "no permission" to "unauthorized"
[Android Q&A, Help & Troubleshooting] kernelhackx:
you flash boot.img in adb mode?
[Android Q&A, Help & Troubleshooting] lenkyun:
Sorry.

It's seems that it is "0123456789ABCDEF	unauthorized"

EDIT :

Oh Maybe It's the adb security.

But why It stuck on boot screen.

I'm finding why.
[Android Q&A, Help & Troubleshooting] kernelhackx:
Dude, try to repo sync again then build. If it still wont boot, might as well check your kernel source's makefile and check the flags and the optimizations, and if you're using a custom toolchain, might as well check the optimizations on the ROM too. And also try flashing a different kernel and see if your ROM boots, if that works it means the error is just with your kernel, then you can at least check it out and eliminate some other problems. Good luck!
[Android Q&A, Help & Troubleshooting] lenkyun:
I finally found the reason why.

My 'init.qcom.rc' in ramdisk has section 'on emmc-fs'.

It mount all /system, /data, /cache

Then I fix it by move to 'on fs'.

Then it can boot now ^_^.

But which value(s) in makefile that made section 'on emmc-fs' supported?
[Android Q&A, Help & Troubleshooting] hell_lock:
I am getting such errors while compiling cm10.1

frameworks/base/core/java/android/view/View.java:2018: error: unmappable character for encoding ASCII
* Align to the end of the view, which is ALIGN_RIGHT if the view???s resolved

There are many errors similar to this and no matter which device tree I use, its always there :/
[Android Q&A, Help & Troubleshooting] lenkyun:
try 'make clobber' and do this again.
[Android Q&A, Help & Troubleshooting] lenkyun:
Hi, I need help.

I had compiled cyanogenmod .

The phone screen appeared cyanogenmod boot logo. After waiting a while it went black screen.

I have to remove battery and re-insert it If I want to boot again. And failed again (with faster boot).

I had wiped all data and cache before install.

After first boot, My computer can't detect device via adb.

This is my device tree

https://github.com/lenkyun/android_device_zte_v817

https://github.com/lenkyun/android_device_qcom_msm7x27a

and this is from logcat

http://pastebin.com/qiZb2QtQ

---------- Post added at 02:59 AM ---------- Previous post was at 02:52 AM ----------

This error because your file contains some character that can't convert to ASCII before compile.

You may need to

save that file as UTF-8 or

'repo sync' or

edit that file by remove that character. (which is appear ???)
[Android Q&A, Help & Troubleshooting] maniknarang:
Thanks for your reply...make clobber did work, but now I get this error:

frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp: In member function 'virtual android::status_t android::CameraClient::sendCommand(int32_t, int32_t, int32_t)':
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:714:23: error: 'CAMERA_CMD_METADATA_ON' was not declared in this scope
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:715:23: error: 'CAMERA_MSG_META_DATA' was not declared in this scope
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:716:23: error: 'CAMERA_CMD_METADATA_OFF' was not declared in this scope
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:717:24: error: 'CAMERA_MSG_META_DATA' was not declared in this scope
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:718:24: error: 'CAMERA_CMD_LONGSHOT_ON' was not declared in this scope
frameworks/av/services/camera/libcameraservice/api1/CameraClient.cpp:720:24: error: 'CAMERA_CMD_LONGSHOT_OFF' was not declared in this scope
build/core/binary.mk:432: recipe for target '/home/manik/Source/out/target/product/golfu/obj/SHARED_LIBRARIES/libcameraservice_intermediates/api1/CameraClient.o' failed
make: *** [/home/manik/Source/out/target/product/golfu/obj/SHARED_LIBRARIES/libcameraservice_intermediates/api1/CameraClient.o] Error 1
make: *** Waiting for unfinished jobs....

CAMERA CLIENT error...Please help again:confused::)
[Android Q&A, Help & Troubleshooting] lenkyun:
Do you use custom libs?
[Android Q&A, Help & Troubleshooting] maniknarang:
No
[Android Q&A, Help & Troubleshooting] kernelhackx:
Try to make clean, then repo sync again. And if you're using a custom toolchain, try building it with the stock toolchian first and see if it builds.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Okay. Thanks to [MENTION=2295876]Recon Freak[/MENTION] for solving some of my errors. Now getting this error :

Download here. Please help.
[Android Q&A, Help & Troubleshooting] hell_lock:
There are way too many files with that error so fixing them would take forever. Repo sync just doesnt work..
[Android Q&A, Help & Troubleshooting] lenkyun:
If you need to reset the files with 'repo sync'.

You need to delete all the files that you need to reset.
[Android Q&A, Help & Troubleshooting] Gnome:
Or you can reference the current repo and create a new one, repo sync will just take you minutes.

repo init --reference=~/(PATH TO CURRENT SOURCE TREE) -u https://(REPO YOU WANT)

Just do that and you'll have a new source tree/files in mnutes.
[Android Q&A, Help & Troubleshooting] hell_lock:
I am doing 'brunch' on a fresh source which is totally untouched. So I don't think it will fix that..
[Android Q&A, Help & Troubleshooting] galaxyfreak:
For fixing camera error:

Remove -DQCOM_ICS_COMPAT flag. It's depreciated and it causes this error.
[Android Q&A, Help & Troubleshooting] ##W4TCH0UT##:
Someone help me. Getting this error while compiling cm11:

make -C kernel/micromax/a110 O=/home/sdkzone/cm11/out/target/product/a110/obj/KERNEL_OBJ ARCH=arm CROSS_COMPILE=" /home/sdkzone/cm11/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7/bin/arm-eabi-" VARIANT_DEFCONFIG= SELINUX_DEFCONFIG= kernel/micromax/a110/kernel/arch/arm/configs/cyanogenmod_a110_defconfig
make[1]: Entering directory `/home/sdkzone/cm11/kernel/micromax/a110'
make[1]: *** No rule to make target `kernel/micromax/a110/kernel/arch/arm/configs/cyanogenmod_a110_defconfig'. Stop.
make[1]: Leaving directory `/home/sdkzone/cm11/kernel/micromax/a110'
make: *** [/home/sdkzone/cm11/out/target/product/a110/obj/KERNEL_OBJ/.config] Error 2
make: *** Waiting for unfinished jobs....