Troubles while building custom CM(13) for kccat6xx - Android Q&A, Help & Troubleshooting

Ok so I searched for quite a while now and fixed few issues but I don't seem to be able to fix this one.
I'm trying to build a custom CM for kccat6xx(roughly a Samsung Galaxy S5+), beeing my first time I'd assume I'll run into some problems but I think I got more than enough to post here.
Lil' summary:
I followed normal CM guide for klte(since those devices works more or less the same way I'd assume the guide would be more or less the same), I synced and all, got android SDK, OpenJDK(which was quite annoying since first sync was detecting my computer as a MAC while running Gentoo Linux, got fixed in a sync the day after tho) made custom local manifest and made the pre-build thingies
I ran into a first issue at that point, considering libinit_msm or so that was removed from qcom_common in latest commits, had to reverse it to make the build works(dirty but eh, works at least) and after that got several issues that I won't list here that I, for the most fixed.
Then I ran on the issue I'm stuck in for about a day now
Code:
make: *** No rules to make target «*/home/govanify/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/R.stamp*», needed for «*/home/govanify/android/system/out/target/common/obj/APPS/BasicDreams_intermediates/src/R.stamp*»
I tried to edit out BasicDreams, just in case, but then Bluetooth would block. Knowing it is just after BasicDreams in the alphabet I figured out it'll do it for all packages. So then I tried to manually build vendor/cmsdk/cm/res and got this issue:
Code:
make: *** No rules to make target «*/home/govanify/android/system/out/host/linux-x86/bin/acp*», needed for «*/home/govanify/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/R.stamp*»
I continued then by trying to compile frameworks/base, but of course:
Code:
make: *** No rules to make target «*/home/govanify/android/system/out/host/linux-x86/bin/aidl*», needed for «*/home/govanify/android/system/out/target/common/obj/JAVA_LIBRARIES/framework_intermediates/src/core/java/android/accessibilityservice/IAccessibilityServiceConnection.java*»
So I finally tried to build aidl manually, but then again:
Code:
make: *** No rules to make target «*/home/govanify/android/system/out/host/linux-x86/obj/lib/libc++.so*», needed for «*/home/govanify/android/system/out/host/linux-x86/obj/EXECUTABLES/aidl_intermediates/aidl*»
I figured out it'll be endless so I stopped here and tried to do a global make of Cyanogen, maybe it'll integrate dependencies after all
But as you already imagined:
Code:
make: *** Aucune règle pour fabriquer la cible «*/home/govanify/android/system/out/target/common/obj/JAVA_LIBRARIES/tcmiface_intermediates/classes.jar*», nécessaire pour «*/home/govanify/android/system/out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/classes-full-debug.jar*». Arrêt.
So yeah, help would be very much appreciated, if you want to replicate the issue grab my manifest here: githubDOTcom/GovanifY/main_kccat6xx/blob/master/kccat6xx.xml (I have less than 10 post so unfortunatelly no link) repo sync and a brunch kccat6xx should do the work. You don't need afaik vendor bins since the bin step is not even started at that point, so I guess build should run into the issue smoothly.
Thanks a lot for any help once again, I'm really running out of ideas on that one

Seems like this got fixed by a mma -B in res folder, thanks ciwrl and Decad3nce from #cyanogen-dev for pointing me out!
Edit: res builds correctly but build still fails so issue still open

Last answer to this post: Issue was with a multi-thread error of CyanogenMod build system itself. Getting on a clean ubuntu install fixed this issue(got others in the meanwhile but I was able to build the ROM at the end, still having major issues tho)

I have cyanogen 13 on samsung s5 i have these problems..Help me to fix them
1.When i unistall a app it reboots with out permision or anything and the app is not deleted
2. When i press security settings it says'Unfortunately,Settings has stopped.'

Related

[REF][3/28] Compiling Jt1134's AOSP

I compiled this tonight and just have some info if others are interested in it.
Link to ROM thread: http://forum.xda-developers.com/showthread.php?p=12437432#post12437432
Dev machine: newest CentOS x64 on VMWare Workstation 7, about a day old
I already had Git installed, but if you're new to this you'll need it (and some dependencies):
Code:
yum install gettext-devel expat-devel curl-devel zlib-devel openssl-devel
wget http://kernel.org/pub/software/scm/git/git-1.7.4.2.tar.bz2
tar xvfj git-1.7.4.2.tar.bz2
cd git-1.7.4.2
make prefix=/usr/local all
make prefix=/usr/local install
Repo was a new tool to me, so it wasn't installed... If you don't have repo, download/install it using this set of commands:
Code:
curl http://android.git.kernel.org/repo > /usr/bin/repo
chmod a+x /usr/bin/repo
Now that you have repo you can download everything. Make a folder somewhere and cd there (mine is /phone/aosp), then:
Code:
repo init -u git://github.com/jt1134/platform_manifest.git -b froyo
This sets up the folder, but you need to download everything:
Code:
repo sync
Jt1134 had -j40 as a parameter, but this caused a Python error for me and does not appear necessary. This downloads an incredible amount of projects and takes quite a while (over an hour at ~500K/s). It's exciting, how much is involved.
The next two lines are very quick, but I had to install Bison ('yum install bison') first:
Code:
source build/envsetup.sh
lunch full_fascinate-eng
Then the final line to actually build the whole package:
Code:
make -j$(grep processor /proc/cpuinfo | wc -l) bacon && fixzip
From this point forward I'm walking through the errors I encountered and how I fixed them to get to completion:
It failed on first run and I had to install glibc-devel because a 32 bit header file stubs-32.h was missing ('yum install glibc-devel').
It failed on the second run because I did not have 'flex' installed. ('yum install flex').
Third time looked good, compiled a ton of stuff, then bombed because 'libsecril-client.so' was missing. Exact error:
Code:
/phone/aosp/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/../lib/gcc/arm-eabi/4.4.0/../../../../arm-eabi/bin/ld:
warning: libsecril-client.so, needed by out/target/product/fascinate/obj/lib/libsecgps.so, not found (try using -rpath or -rpath-link)
It was however found in two places:
Code:
/phone/aosp/vendor/samsung/vzwtab/proprietary/lib/libsecril-client.so
/phone/aosp/vendor/samsung/fascinate/proprietary/lib/libsecril-client.so
So what I did is copy it to the output folder (not the optimal solution I'm sure, but it worked):
Code:
cp vendor/samsung/fascinate/proprietary/lib/libsecril-client.so out/target/product/fascinate/obj/lib/
Fourth time through it continued on an compiled a ton of projects, and then... 'gperf' command not found. ('yum install gperf')
Fifth time, I actually went to sleep during this one , woke up to this error:
Code:
/usr/bin/ld: cannot find -lncurses
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/adb_intermediates/adb] Error 1
I fixed this with 'yum install ncurses-devel' and let the process continue, and shortly afterwards got another error:
Code:
In file included from external/qemu/android/skin/window.c:19:
prebuilt/linux-x86/sdl/include/SDL/SDL_syswm.h:55:22: error: X11/Xlib.h: No such file or directory
prebuilt/linux-x86/sdl/include/SDL/SDL_syswm.h:56:23: error: X11/Xatom.h: No such file or directory
I fixed this with 'yum install libX11-devel' and off we go again... a new error!:
Code:
/usr/bin/ld: cannot find -lhistory
collect2: ld returned 1 exit status
make: *** [out/host/linux-x86/obj/EXECUTABLES/sqlite3_intermediates/sqlite3] Error 1
This was fixed by running 'yum install readline-devel' and we're back to a lot more compiling...
Success!! full_fascinate.zip is in the root folder, ready to be moved to the phone.
Hope someone might find this helpful or interesting... let me know if there's anything I can do to make it better!
What dev environment do you guys use to edit these files?
Do you just keep recompiling them and running the rom using the SDK virtual phone?
I'm an experienced developer but I am only familiar with windows development but want to get into some apps development soon.
Eclipse is rather popular.
Sent from my SCH-I500 using XDA App
I'm using Eclipse, run them on the phone for testing, and haven't done much yet.
Would other developers be willing to chime in with their advice/preferences on the whole process? Thanks!
-j40 is only to parallelize the tasks (up to 40 threads I believe) so it's not strictly necessary.
By the way, all the dependencies to build android should be on here: http://source.android.com/source/download.html
And @SmokeyDP, you don't need to build your own version of the OS to write apps, so these instructions aren't really relevant for that if that's all you want to do. Eclipse is probably the most common IDE for Android app development because that's what Google supports directly, but I've heard that IntelliJ IDEA also has nice Android support and just lacks a GUI builder. I've recently switched to IDEA for other Java development and it's a lot faster and more refined than eclipse, so I would suggest trying that if you're going to start learning because you won't be used to either eclipse or IDEA and can choose which one seems the best to you.
I realize you don't need to rebuild the OS to develop an app, but I was asking about developing both since I imagine it's the same IDE and I was curious. Thanks for the info.
SmokeyDP said:
I realize you don't need to rebuild the OS to develop an app, but I was asking about developing both since I imagine it's the same IDE and I was curious. Thanks for the info.
Click to expand...
Click to collapse
Unless you're going to be using the NDK to write apps, you're not going to be using C, which is what the Linux Kernel is written in... and Eclipse's support for C is a lot poorer than its support for Java (honestly, I can't stand its support for either, its interface is quite the unorganized mess, IMO). I, personally, use a different set of tools for each language/toolkit I use, as each have their pros and cons.

[Q][HELP]Calculator build error??? [FIXED]

I'm building AOKP for HTC ace (desire hd/inspire 4g). I get this error:
Code:
make: *** No rule to make target `/home/espmartin/SchutzhundAOKP/out/target/common/obj/JAVA_LIBRARIES/android_stubs_current_intermediates/classes.jar', needed by `/home/espmartin/SchutzhundAOKP/out/target/common/obj/APPS/Calculator_intermediates/classes-full-debug.jar'. Stop.
I've recently suffered HDD failure, and have managed to re-install Ubuntu 13.10, so my builds are all pretty much on a vanilla installation (with Java 1.6).
Any thoughts?
Fixed. Due to incompatible repos
espmartin said:
Fixed. Due to incompatible repos
Click to expand...
Click to collapse
Did you repo sync with reference tag? If so, what did you do to fix it?

trouble building cm13

I've hit a bit of a brick wall while trying to do my first CyanogenMod build (cm13 on trltespr). Not sure if this should be put on the device board itself but I figured I'd try here first. I've extracted proprietary files from the device, followed the guide on the CM wiki, and while trying to build I'm getting the following error from make:
make: *** No rule to make target '/home/cmbuild/android/system/out/target/common/obj/JAVA_LIBRARIES/tcmiface_intermediates/javalib.jar', needed by '/home/cmbuild/android/system/out/target/common/obj/JAVA_LIBRARIES/okhttp_intermediates/classes-full-debug.jar'. Stop.
From what I've gathered I absolutely do not want to skip building either of these libraries, so I'm kind of at an impasse here. Does anyone have any thoughts on what my options may be here?
Actually, i'm starting to get a different error now, quite similar though:
make: *** No rule to make target '/home/cmbuild/android/system/out/target/common/obj/APPS/org.cyanogenmod.platform-res_intermediates/src/R.stamp', needed by '/home/cmbuild/android/system/out/target/common/obj/APPS/BasicDreams_intermediates/src/R.stamp'. Stop.
^regarding above error message, first one comes from simply running 'make', second one comes from running brunch trltespr
Make Clobber your folder
Do a repo sync..
How about try to use mka..

Error building CM13 for Sony Xperia V (libta)

Hi there.
I recently decided to try getting some more fun out of my old (by today's standards, grmbl) Xperia V by upgrading to a newer Android version. So I grabbed a Cyanogenmod 13 nightly and managed to get it all set up, and I'm quite happy about it. However, I ran into an issue with feedback when activating speakerphone. There is a bug report for this issue already, but I cannot link to it because I am a new forum user... it's in the Cyanogenmod Jira and has the ID "CYAN-2110". It's for a different phone but it's the same hardware platform.
Apparently nobody ever fixed this properly by making the device use the correct mic in speakerphone mode, so I decided to jump in and try fixing it myself.
However, for now I am stuck because my CM13 build does not work yet. I followed the build instructions in the guide on the Cyanogenmod wiki on the page "Build_for_tsubasa", except that I ran ./extract-files.sh in ~/android/system/device/sony/blue-common as well as in tsubasa, otherwise breakfast would complain.
After that I managed to start a build which ran for ~15 minutes and compiled a good lot of stuff before erroring out like so:
Code:
make: *** Keine Regel vorhanden, um das Ziel „/home/simmax/android/system/out/target/product/tsubasa/obj/SHARED_LIBRARIES/libta_intermediates/export_includes“,
benötigt von „/home/simmax/android/system/out/target/product/tsubasa/obj/EXECUTABLES/macaddrsetup_intermediates/import_includes“, zu erstellen. Schluss.
make: *** Auf noch nicht beendete Prozesse wird gewartet …
target thumb C: linker <= bionic/linker/linker_libc_support.c
make: Verzeichnis „/home/simmax/android/system“ wird verlassen
#### make failed to build some targets (16:57 (mm:ss)) ####
In case your German is rusty, it says that make was unable to find a rule for building „/home/simmax/android/system/out/target/product/tsubasa/obj/SHARED_LIBRARIES/libta_intermediates/export_includes“ which is needed by „/home/simmax/android/system/out/target/product/tsubasa/obj/EXECUTABLES/macaddrsetup_intermediates/import_includes“.
libta.so appears to be one of the libraries that ./extract-files.sh copied from the phone. It seems to have been copied correctly and is sitting in android/system/vendor/sony/blue-common/proprietary/lib.
I already asked about it on #cyanogenmod-dev, and was told that "copying is not enough, macaddrsetup is trying to link against it so you also need to add it as a shared prebuilt library". Unfortunately the user who provided this insight didn't answer my follow-up question, so this does not really help me because I have no real idea how the build environment works and how to implement his suggestion. Maybe it helps you help me though...
Following up on this:
The issue is that the ./extract-files.sh in devices/sony/blue-common does not create an Android.mk file which is needed for a few of the libraries which it copies. This can be fixed by going the same way as the android_device_sony_huashan repository, by providing a platform-specific ./setup-makefiles.sh which is called from ./extract-files.sh. I did that and am going to make a pull request to the blue-common repo, so that this can be fixed for everyone.
Another part I got stuck on was a series of messages when running ./extract-files.sh, implying that some files it needed were not present on my phone. The real issue was that adb needs root access to pull these files, so it needs to be activated in the developer settings on the phone *and* you need to run "adb root" on the shell of your build machine before running ./extract-files.sh.
The last remaining issue that stands in the way of making a build according to the official script is that there is still a missing proprietary blob (boot/RPM.bin). I assume this also needs to be extracted from the phone somehow, but I am not sure how to make that happen yet.

JAVA_LIBRARIES error while compiling CyanogenMod 11 for i9300

Hi,
I'm trying to compile CM11 for my S3, and no matter what I do I can't get past this error, nor can I find anything helpful online.
Code:
make: *** No rule to make target '/home/kayla/android/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes.jar', needed by '/home/kayla/android/out/target/common/obj/APPS/AdvancedDisplay_intermediates/classes-full-debug.jar'.
My source tree is fully synced, and I have the correct device, proprietary, and kernel folders synced. I've completely re-built multiple times with Oracle JDK 8, 7, and 6, and I still can't get past this error.
Any help would be great, thanks!
kaisparkle said:
Hi,
I'm trying to compile CM11 for my S3, and no matter what I do I can't get past this error, nor can I find anything helpful online.
Code:
make: *** No rule to make target '/home/kayla/android/out/target/common/obj/JAVA_LIBRARIES/core_intermediates/classes.jar', needed by '/home/kayla/android/out/target/common/obj/APPS/AdvancedDisplay_intermediates/classes-full-debug.jar'.
My source tree is fully synced, and I have the correct device, proprietary, and kernel folders synced. I've completely re-built multiple times with Oracle JDK 8, 7, and 6, and I still can't get past this error.
Any help would be great, thanks!
Click to expand...
Click to collapse
cm 11 works only with openjdk 7 so make sure that you use the proper one , you can check it by runing this in yre terminal
Code:
sudo update-alternatives --config java

Categories

Resources