Related
Ok, I setup my 2 build boxes. One Ubuntu 11.10x64 and one Mint 11x86. Installed required packages and downloaded multiple toolchains. I have tried compiling on both machines and on both I get the same errors.
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make: *** Waiting for unfinished jobs....
CHK include/linux/version.h
I have tried make thunderc_perf_defconfig and get the same error. Copied .config from device dropped into source, same error.
Any ideas on what is going on? I'm new to this so any help would be great.
I don't known, maybe gcc
try checking your mount options?
Nope its not gcc; as I said I have installed all required packages including gcc + bison etc. My mount options? Is that the "export ARCH=arm" ? Where I have to set the default compiler? I'm new to the newer flavors of linux. The last distro I used was Mandrake 7.1 ;-) Now I am testing this on 2 builds; an x64 Ubuntu and a x86 Mint(Which is Ubuntu). I have to be missing something on both, but I have followed tutorials guides to the T and still get this error. I get more errors than this by the way. The compiler kicks back Kconfig saying unexpected line of code.
SgtPropain said:
Ok, I setup my 2 build boxes. One Ubuntu 11.10x64 and one Mint 11x86. Installed required packages and downloaded multiple toolchains. I have tried compiling on both machines and on both I get the same errors.
make[2]: *** [silentoldconfig] Error 1
make[1]: *** [silentoldconfig] Error 2
make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.
make: *** Waiting for unfinished jobs....
CHK include/linux/version.h
I have tried make thunderc_perf_defconfig and get the same error. Copied .config from device dropped into source, same error.
Any ideas on what is going on? I'm new to this so any help would be great.
Click to expand...
Click to collapse
I ran a search on your error message about the missing rule to make auto.conf and found this:
https://bbs.archlinux.org/viewtopic.php?id=99089
It relates to the other poster's comment about checking your mount options. It's a short process to fix it.
And if it doesn't work maybe it will at least give you a new error message to research.
glarepate said:
I ran a search on your error message about the missing rule to make auto.conf and found this:
https://bbs.archlinux.org/viewtopic.php?id=99089
It relates to the other poster's comment about checking your mount options. It's a short process to fix it.
And if it doesn't work maybe it will at least give you a new error message to research.
Click to expand...
Click to collapse
just as i thought. that might have happened. its worth a try though.
SgtPropain said:
Nope its not gcc; as I said I have installed all required packages including gcc + bison etc. My mount options? Is that the "export ARCH=arm" ? Where I have to set the default compiler? I'm new to the newer flavors of linux. The last distro I used was Mandrake 7.1 ;-) Now I am testing this on 2 builds; an x64 Ubuntu and a x86 Mint(Which is Ubuntu). I have to be missing something on both, but I have followed tutorials guides to the T and still get this error. I get more errors than this by the way. The compiler kicks back Kconfig saying unexpected line of code.
Click to expand...
Click to collapse
Wrong...
Because you don't have .config file in the source. If you are building kernel from source, you must have the kernel config. That kernel config can be shared in the source code, it depends on that kernel developer, he can shared it in arch/arm/config, access to there then find that kernel defconfig. Or you can get the kernel config of that kernel with another method, but this method just can be applied if the kernel you want to build is for our device: flash that kernel then go to terminal then type:
Code:
su
(Accept the super user)
Code:
cp /proc/config.gz /sdcard
If it show "No such file or directory found" so you should ask that kernel developer for their .config.
If it doesn't show anything, go to sdcard and find if there is a file that named config.gz, it's the kernel config. Get back to terminal then type:
cd /sdcard
gunzip config.gz
Voila!
I actually tried that already.... I have been at this for about three days. XDA was my last resort as I like to figure things out on my own. However I'm stuck @ a brick wall. I have edited /etc/fstab and removed the bs mount options..remounted same error. Mind you I'm doing most of this from a Virtual Environment. Starting to think this is my issue, but it doesn't explain the same error on machine #2. Maybe I'm doing it right, possibly a bad git clone?
thachtunganh said:
Wrong...
Because you don't have .config file in the source. If you are building kernel from source, you must have the kernel config. That kernel config can be shared in the source code, it depends on that kernel developer, he can shared it in arch/arm/config, access to there then find that kernel defconfig. Or you can get the kernel config of that kernel with another method, but this method just can be applied if the kernel you want to build is for our device: flash that kernel then go to terminal then type:
Code:
su
(Accept the super user)
Code:
cp /proc/config.gz /sdcard
If it show "No such file or directory found" so you should ask that kernel developer for their .config.
If it doesn't show anything, go to sdcard and find if there is a file that named config.gz, it's the kernel config. Get back to terminal then type:
cd /sdcard
gunzip config.gz
Voila!
Click to expand...
Click to collapse
Yeah that would be great if I hadn't done that already. In my post I stated I had replaced the .config from my device. I have literately tried everything but doing this from base. IE not from a VM. I appreciate the help but its a "no go".
Beginning of my .config for proof
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.32.9-ck2
# Wed Apr 11 20:41:44 2012
#
CONFIG_ARM=y
CONFIG_SYS_SUPPORTS_APM_EMULATION=y
CONFIG_GENERIC_GPIO=y
CONFIG_GENERIC_TIME=y
CONFIG_GENERIC_CLOCKEVENTS=y
CONFIG_KTIME_SCALAR=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_STACKTRACE_SUPPORT=y
CONFIG_HAVE_LATENCYTOP_SUPPORT=y
CONFIG_LOCKDEP_SUPPORT=y
CONFIG_TRACE_IRQFLAGS_SUPPORT=y
CONFIG_HARDIRQS_SW_RESEND=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_ARCH_HAS_CPUFREQ=y
CONFIG_GENERIC_HWEIGHT=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_GENERIC_HARDIRQS_NO__DO_IRQ=y
CONFIG_VECTORS_BASE=0xffff0000
CONFIG_DEFCONFIG_LIST="/lib/modules/$UNAME_RELEASE/.config"
CONFIG_CONSTRUCTORS=y
Setting up a third independent machine Ubuntu x86 testing..
where do you get that .config from?
pull /proc/config.gz
SgtPropain said:
pull /proc/config.gz
Click to expand...
Click to collapse
What device are you using, and what kernel are you using.
for the time being you can use prebuilt kernel...no need to build kernel from source....
williamcharles said:
for the time being you can use prebuilt kernel...no need to build kernel from source....
Click to expand...
Click to collapse
He isn't building ROM from source. He is learning how to build a kernel from source.
Sorry for the delay; had 2 deaths in the family.
I setup my third box and again I get the same results. I really don't know where I'm going wrong. This kinda makes me lean to, I have bad source code. I'm no pro C programmer; however when building I get Kconfig errors. I opened said file and the comments look all messed up. The compiler I think is reading the comments as code and kicking it back giving me this error.
by the way what are you compiling and please teach me compiling i want to learn it .
I'm compiling a modified kernel for the Optimus V. I can't teach you how to compile because I don't even know if I'm doing it right.
This is a follow up on my "old" "Guide on how I build my own CM9 test builts" thread.
Guide how I build CM10 for my Mango.
For the first time you try to build CM10.
Create ~/bin and download repo to that directory. Afterwards set executable bit to make it possible to ”execute”.
Code:
mkdir -p ~/bin
curl https://dl-ssl.google.com/dl/googlesource/git-repo/repo > ~/bin/repo
chmod a+x ~/bin/repo
Now reboot the computer.
Create ~/android/system and initialize the repository.
Code:
mkdir -p ~/android/system
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b jellybean
Unpack the attached local_manifest.xml.bz2 and place local_manifest.xml into ~/android/system/.repo
Synchronise towards the current git repositories.
Code:
repo sync
Setup the environmental settings and initialize the Mango build.
Code:
. build/envsetup.sh
breakfast mango
Initialize the Mango build.
Code:
cd ~/android/system/device/semc/mango/
./setup-makefiles.sh
Download the prebuilts
Code:
~/android/system/vendor/cm/get-prebuilts
Check for new changes
Code:
cd ~/android/system/
repo sync
Setup the environment again and build the ROM (takes long time)
Code:
. build/envsetup.sh
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-10-DATE-UNOFFICIAL-mango.zip
The next times you try to build it, you only need to do the following.
Delete build.prop, if not will build.prop not get generated.
Code:
rm -f ~/android/system/out/target/product/mango/system/build.prop
Syncronise the git repositories.
Code:
cd ~/android/system/
repo sync
Setup the environmental settings.
Code:
. build/envsetup.sh
Configure/build.
Code:
brunch mango
You will now find the build here (change DATE into the date).
~/android/system/out/target/product/mango/cm-10-DATE-UNOFFICIAL-mango.zip
EDIT (August 14. 2012): If the boot.img is not booting, is it most likely due to the bootloader bug.
To make it "work", do the following (replace mango with your own device)
Code:
cd out/target/product/mango/
rm -f ./boot.img ./combinedroot.cpio ./combinedroot.fs ./ramdisk.img
cp ./root/logo.rle ./root/waste_of_space1
cp ./root/logo.rle ./root/waste_of_space2
cp ./combinedroot/logo.rle ./combinedroot/waste_of_space1
cp ./combinedroot/logo.rle ./combinedroot/waste_of_space2
cd ../../../..
brunch mango
just a technical: is it really necessary to reboot the computer after downloading the repo binary? and if so, why is that??
bokrug said:
just a technical: is it really necessary to reboot the computer after downloading the repo binary? and if so, why is that??
Click to expand...
Click to collapse
It is only necessary on some Linux distributions, where you will not be able to execute anything from that directory, before a reboot. You can try to see if you can do it without. If it is working, do you not need it.
hnl_dk said:
It is only necessary on some Linux distributions, where you will not be able to execute anything from that directory, before a reboot. You can try to see if you can do it without. If it is working, do you not need it.
Click to expand...
Click to collapse
There's no really need to reboot - edit .bashrc in your home directory and add
Code:
export PATH=~/bin/:$PATH
Save, then run:
Code:
source ~/.bashrc
It have to work on all distros
pikpok said:
There's no really need to reboot - edit .bashrc in your home directory and add
Code:
export PATH=~/bin/:$PATH
Save, then run:
Code:
source ~/.bashrc
It have to work on all distros
Click to expand...
Click to collapse
I just want to show the "universal" way.
Not everyone is using bash
hnl_dk said:
I just want to show the "universal" way.
Not everyone is using bash
Click to expand...
Click to collapse
If someone use another shell, e.g. zsh, then he'll know what files he have to edit IMO rebooting is wasting time.
pikpok said:
If someone use another shell, e.g. zsh, then he'll know what files he have to edit IMO rebooting is wasting time.
Click to expand...
Click to collapse
no it is not, as you do not need to edit any files. It will work automatically.
It is as much a waste of time to edit the resource-definition scripts.
hnl_dk said:
no it is not, as you do not need to edit any files. It will work automatically.
It is as much a waste of time to edit the resource-definition scripts.
Click to expand...
Click to collapse
Reboot - about 1 min
Edit one file and paste single command in terminal - for me it's 10secs
But it comes to offtop discussion, so it would be better to end it now
@edit - now when I think about it... bin in home folder won't be added to PATH automatically, at least in Arch Linux. Maybe Ubuntu is more "intelligent" :laugh:
pikpok said:
Reboot - about 1 min
Edit one file and paste single command in terminal - for me it's 10secs
But it comes to offtop discussion, so it would be better to end it now
@edit - now when I think about it... bin in home folder won't be added to PATH automatically, at least in Arch Linux. Maybe Ubuntu is more "intelligent" :laugh:
Click to expand...
Click to collapse
It does not take that long for me to make a reboot
No matter what, is it always good to have more methods to make something work.
It did the last time I tried Arch Linux... and no I am not using Ubuntu (too flashy for me )
Assuming that there is an entry in your ~/.profile that adds ~/bin to PATH, a reboot won't do anything that logout/login wouldn't. Furthermore, logout/login (in this case) won't do anything that sourcing ~/.profile wouldn't. So, simply issuing "source ~/.profile" is sufficient on most distributions. If you are using a distribution or a shell that doesn't do this by default, then you probably already know what you need to do.
I do, however, commend hnl_dk's efforts to make things simpler for newcomers to Android and Linux, even if it's not the the "fastest" or the "best" way. Whenever you start getting into one of those "what if?" arguments, things tend to spiral out of control. Sometimes it's better to just make a few assumptions and go with what is most likely to work.
A reboot might be a bit of an overkill, though. :laugh:
Can't run 64-bit prebuilts on my 32-bit Linux
I have a 32-bit Linux box so get the errors:
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file
Had a quick look around, but are there gcc etc. prebuilts for 32-bit Linux boxes?
TIA,
AK-A
ak-a said:
I have a 32-bit Linux box so get the errors:
/bin/bash: prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-gcc: cannot execute binary file
Had a quick look around, but are there gcc etc. prebuilts for 32-bit Linux boxes?
TIA,
AK-A
Click to expand...
Click to collapse
Did you try to build it as described?
It is working fine on my 32bit debian machine.
If not, please describe hos you try it build it.
hnl_dk said:
Did you try to build it as described?
It is working fine on my 32bit debian machine.
If not, please describe hos you try it build it.
Click to expand...
Click to collapse
Yeah, followed the instructions as per the first post. Will re-try and see if I missed/messed something and report back.
Hey !!! Do you think I should post my AOSP errors in this thread...so that its easier for us to keep track..?? :highfive:
As this is a Tutorial Thread for "how to build cm10 on your own" I don't think it makes sense posting errormessages of errm. "android open source project"? As I am writing this I recognize that I do not really understand what you mean.
CosmoDroid said:
Hey !!! Do you think I should post my AOSP errors in this thread...so that its easier for us to keep track..?? :highfive:
Click to expand...
Click to collapse
Like Snoopo is saying, should that be in this thread. Compiling AOSP is not as "user friendly" as CM, as our devices are officially supported by CM and not AOSP.
If you want, can you make a new thread about compiling "AOSP - Jelly bean".
i always stop at "repo sync"
i always stop at "repo sync"
and it always tell me
"Fetching projects: 21% (66/313) fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=??????"
can you help me
thanks
shufuking said:
i always stop at "repo sync"
and it always tell me
"Fetching projects: 21% (66/313) fatal: unable to connect to github.com:
github.com[0: 207.97.227.239]: errno=??????"
can you help me
thanks
Click to expand...
Click to collapse
Same also happens for me, then I try again and again and again and then it is working.
Lots of people are accessing github, and there is only a limited "whole" for the data to get through.
hnl_dk said:
Same also happens for me, then I try again and again and again and then it is working.
Lots of people are accessing github, and there is only a limited "whole" for the data to get through.
Click to expand...
Click to collapse
thanks for your suggestion
finally i make it.
another question.
when i perform " brunch smultron"
i got lots of "cannot execute binary file"
and final "make: *** [out/target/product/smultron/obj/lib/crtbegin_static.o] Error 126"
do you know what it means?
shufuking said:
thanks for your suggestion
finally i make it.
another question.
when i perform " brunch smultron"
i got lots of "cannot execute binary file"
and final "make: *** [out/target/product/smultron/obj/lib/crtbegin_static.o] Error 126"
do you know what it means?
Click to expand...
Click to collapse
without more details, my best guess is that you may be building it on a FAT32 or NTFS partition?
then there is a good chance that linux is not able to read the executable bits.
This thread is intended for devs & advanced users only.
Here you can learn how to build CyanogenMod 11.0 for any of the 2011 xperia devices.
I will use 'smultron' as an example device, you should replace the codename with the device you want to build.
For the first time you try to build CM11.0
Follow this guide up to "Initialize the CyanogenMod source repository" step (don't execute this step).
http://wiki.cyanogenmod.org/w/Build_for_smultron
Initialize the CyanogenMod source repository
Enter the following to initialize the repository:
Code:
cd ~/android/system/
repo init -u git://github.com/CyanogenMod/android.git -b cm-11.0
Get the required local manifest
Code:
mkdir -p ~/android/system/.repo/local_manifests
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-11.0/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
Download the source code
Code:
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
ln -s vendor/extra/updates.sh updates.sh
./updates.sh
Get the prebuilts
Code:
cd ~/android/system/vendor/cm
./get-prebuilts
Setup the build environment & prepare the device-specific code.
Code:
cd ~/android/system
. build/envsetup.sh
breakfast smultron
Build the ROM (takes long time)
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-11.0-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
The next times you want to build, you only need to do the following:
Sync the repositories & make sure you are using the latest local_manifest.
Code:
cd ~/android/system/
curl https://raw.githubusercontent.com/LegacyXperia/local_manifests/cm-11.0/semc.xml > ~/android/system/.repo/local_manifests/semc.xml
repo sync
Setup the build environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the ROM
Code:
brunch smultron
If the build finishes successfully, you will find the build here (change DATE into the date):
~/android/system/out/target/product/smultron/cm-11.0-DATE-UNOFFICIAL-LegacyXperia-smultron.zip
Steps to build only the kernel:
Sync the repositories.
Code:
cd ~/android/system/
repo sync
Setup the environment
Code:
. build/envsetup.sh
Download some commits from CyanogenMod gerrit which are not accepted yet
Code:
./updates.sh
Build the kernel
Code:
breakfast smultron
make -j4 bootimage
If the build finishes successfully, you will find the boot image here:
~/android/system/out/target/product/smultron/boot.img
Some suggestions for faster builds:
* Enable ccache
* Use the fastest hdd on your pc to store the source, build output & ccache
* You can also buy an ssd, if it's not large enough to hold everything, just store the build output & ccache
* mount /tmp on tmpfs (RAM).
The above have greatly improved my dirty build times with removed /out/target from 1h30m to 30m.
Mounting /tmp on tmpfs made the biggest improvement for me.
Credits: Thanks to hnl_dk for the initial CM9 & CM10 guides.
Reserved
bro your devs are awesome but when you gonna give us the opportunity to taste kitkat
Thanks so muxh
Sent from my Xperia Live with Walkman using xda premium
Sorry for the noob question, first time builder here. You say you prepare the device specific code, but there is no official CM11 for 2011 Xperia. Where does this code come from? Do you upload somehow your ROMs to Cyanogenmod servers? If it is true, that means that if I build CM11 on my own I can get the latest features before you even release them with a nightly?
johnny.tifosi said:
Sorry for the noob question, first time builder here. You say you prepare the device specific code, but there is no official CM11 for 2011 Xperia. Where does this code come from? Do you upload somehow your ROMs to Cyanogenmod servers? If it is true, that means that if I build CM11 on my own I can get the latest features before you even release them with a nightly?
Click to expand...
Click to collapse
Legacy Xperia maintains the device trees on github. All the respective devices have their codes there. No, the builds are not uploaded to CM servers. But, if you build CM11 at whatever respective time you build, the latest feautes merged till that time will be incorporated in the build.
Sent from my Xperia Mini Pro using XDA Premium 4 mobile app
Hi,
For compile KitKat which better 32bit or 64bit Ubuntu ?
r00lz said:
Hi,
For compile KitKat which better 32bit or 64bit Ubuntu ?
Click to expand...
Click to collapse
32 bit
r00lz said:
Hi,
For compile KitKat which better 32bit or 64bit Ubuntu ?
Click to expand...
Click to collapse
The link in the OP states:
"Note:
You want to use a 64-bit version of Linux. According to Google, 32-bit Linux environment will only work if you are building older versions prior to Gingerbread (2.3.x)/CyanogenMod 7. However, as of 10.1 CyanogenMod does not build with 64bit host binaries on some systems. You will have to set something like BUILD_HOST_32bit=1 in your environment when building on such 64bit system. "
Start build.
Hope good luck.
In order to build for Xperia Ray I just have to replace "smultron" with "urushi" in each command, right?
johnny.tifosi said:
In order to build for Xperia Ray I just have to replace "smultron" with "urushi" in each command, right?
Click to expand...
Click to collapse
yes
hint:
I already had a build env for 10.1/10.2, and the first repo init... failed with "gpg bla cannot verify".
"gpg bla" is Finnish for "you need a new repo tool version". I re-installed it with
$ curl http://commondatastorage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
can anybody help with this please http://pastebin.com/2Te1YuPt
Building stops after about 10 minutes with the following error: AttributeError: 'NoneType' object has no attribute 'group'.
Code:
target thumb C++: third_party_WebKit_Source_wtf_wtf_gyp <= external/chromium_org/third_party/WebKit/Source/wtf/ArrayBuffer.cpp
Traceback (most recent call last):
File "../../base/android/jni_generator/jni_generator.py", line 1070, in <module>
sys.exit(main(sys.argv))
File "../../base/android/jni_generator/jni_generator.py", line 1066, in main
options.optimize_generation)
File "../../base/android/jni_generator/jni_generator.py", line 1001, in GenerateJNIHeader
jni_from_javap = JNIFromJavaP.CreateFromClass(input_file, namespace)
File "../../base/android/jni_generator/jni_generator.py", line 514, in CreateFromClass
jni_from_javap = JNIFromJavaP(stdout.split('\n'), namespace)
File "../../base/android/jni_generator/jni_generator.py", line 457, in __init__
contents[1]).group('class_name')
AttributeError: 'NoneType' object has no attribute 'group'
make: *** [/home/johnny/android/system/out/target/product/urushi/obj/GYP/shared_intermediates/ui/gl/jni/Surface_jni.h] Error 1
make: *** Waiting for unfinished jobs....
Any help?
Successfully build smultron on a clean Ubuntu VM. No problems.
ivosat said:
Successfully build smultron on a clean Ubuntu VM. No problems.
Click to expand...
Click to collapse
Same here. Had not a single problem while building. And it works amazingly fast with barely any noticeable bugs.
p0werdirector said:
Same here. Had not a single problem while building. And it works amazingly fast with barely any noticeable bugs.
Click to expand...
Click to collapse
How much data is being used during the whole process...
You will need more than 55 GB free space to build it from scratch ( Linux installation and everything else ).
ivosat said:
You will need more than 55 GB free space to build it from scratch ( Linux installation and everything else ).
Click to expand...
Click to collapse
I have no issues with storage ...cause ofd 1 tb hdd
but how much data i have to download to build it from scratch ?
Does everyone downloads that who build their own build ? !!
(Dont high speed bandwidths costs expensive in your countries ?)
hey guys! I'm doing a test compile of CM, just trying to get it running on the Raspberry Pi 2 for kicks, and I ran into a compile issue:
Code:
Install: /out/host/linux-x86/bin/apicheck
Checking API: checkpublicapi-last
Checking API: checkpublicapi-current
Docs droiddoc: /out/target/common/docs/system-api-stubs
DroidDoc took 14 sec. to write docs to /out/target/common/docs/system-api-stubs
Checking API: checksystemapi-last
Checking API: checksystemapi-current
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Device?
Edited OP with more info*
Oh lol exotic.
Device tree an all other device specific files please.
Trafalgar Square said:
Oh lol exotic.
Device tree an all other device specific files please.
Click to expand...
Click to collapse
added sources to OP
I'm having the same issue compiling CM-13.0 for GT-P5210. Any update? Thank you.
Im having the exact same error:
Code:
Export includes file: system/core/libsparse/Android.mk -- /mnt/raid5/Other/development/CM-13-0/android/system/out/host/linux-x86/obj/EXECUTABLES/simg2img_host_intermediates/export_includes
make: *** No rule to make target `prebuilts/cmsdk/api/.txt', needed by `/mnt/raid5/Other/development/CM-13-0/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
Starting language-specific parse...
Processing types...
C++ analysis...
Generating wrappers...
make: Leaving directory `/mnt/raid5/Other/development/CM-13-0/android/system'
#### make failed to build some targets (13:18 (mm:ss)) ####
trying to build CyanogenMod R7Plus
latest repo sync for -b CM-13.0
used breakfast to get the https://github.com/cyanogenmod/android_device_oppo_r7plus
extracted blobs using the script and a nightly.zip
Update:
to those who come here and have the ".txt" file error seen above.
this is what i did to fix it:
Code:
1. I deleted the whole source
2. i run this script "build-environment-setup.sh" get it here: https://github.com/akhilnarang/scripts
3. I initiated the repo again "repo init -u https://github.com/CyanogenMod/android.git -b "cm-13.0""
4. synced the repo using "repo sync -j4 --force-sync -f --no-tags --no-clone-bundle --no-repo-verify"
from here on continue like in the guides.
I have that error since March and had it temporarily resolved via switching to the stable branch.
Thanks to @celoxocis I finally built the cm13 nightly, although I followed only the second step from his guide.
make: *** No rule to make target '/-1.txt', needed by '/home/android/y300/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
Click to expand...
Click to collapse
Same problem on Huawei Y300 / u8833, AICP MM6.0 sourcecode. After "lunch full_u8833-userdebug" and after "make -j2" got error.
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
---------- Post added at 10:36 PM ---------- Previous post was at 10:35 PM ----------
adeii said:
Same problem on Huawei Y300 / u8833, AICP MM6.0 sourcecode. After "lunch full_u8833-userdebug" and after "make -j2" got error.
Click to expand...
Click to collapse
umaturman said:
I have that error since March and had it temporarily resolved via switching to the stable branch.
Thanks to @celoxocis I finally built the cm13 nightly, although I followed only the second step from his guide.
Click to expand...
Click to collapse
celoxocis said:
Im having the exact same error:
Code:
Export includes file: system/core/libsparse/Android.mk -- /mnt/raid5/Other/development/CM-13-0/android/system/out/host/linux-x86/obj/EXECUTABLES/simg2img_host_intermediates/export_includes
make: *** No rule to make target `prebuilts/cmsdk/api/.txt', needed by `/mnt/raid5/Other/development/CM-13-0/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
make: *** Waiting for unfinished jobs....
Starting language-specific parse...
Processing types...
C++ analysis...
Generating wrappers...
make: Leaving directory `/mnt/raid5/Other/development/CM-13-0/android/system'
#### make failed to build some targets (13:18 (mm:ss)) ####
trying to build CyanogenMod R7Plus
latest repo sync for -b CM-13.0
used breakfast to get the https://github.com/cyanogenmod/android_device_oppo_r7plus
extracted blobs using the script and a nightly.zip
Click to expand...
Click to collapse
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
metrixx02 said:
guys how solved this issue could help me anyone ???
here log ...
http://www.hastebin.com/wekudopujo.rb
Click to expand...
Click to collapse
Use build-environment-setup.sh from the guide. The error is gone when I installed some dependencies.
Does anyone know how to fix this damn error on Opensuse.
Afaik, all distros apart from ones based on ubuntu/debian have this error.
Silesh.Nair said:
Does anyone know how to fix this damn error on Opensuse.
Afaik, all distros apart from ones based on ubuntu/debian have this error.
Click to expand...
Click to collapse
Did you try this guide?
That's not it. It just works fine on debian, Ubuntu or mint. But never on Suse.
Sent from my Moto G (4) using Tapatalk
kronflux said:
hey guys! I'm doing a test compile of CM, just trying to get it running on the Raspberry Pi 2 for kicks, and I ran into a compile issue:
Code:
Install: /out/host/linux-x86/bin/apicheck
Checking API: checkpublicapi-last
Checking API: checkpublicapi-current
Docs droiddoc: /out/target/common/docs/system-api-stubs
DroidDoc took 14 sec. to write docs to /out/target/common/docs/system-api-stubs
Checking API: checksystemapi-last
Checking API: checksystemapi-current
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Click to expand...
Click to collapse
Use
Code:
make update-api && make -j4
adityaupreti said:
it's very vague, so I'm wondering if anyone could provide some insight.
using sources:
https://github.com/peyo-hd/device_brcm_rpi2
https://github.com/peyo-hd/local_manifests
Use
Click to expand...
Click to collapse
Check my post (post #8) I'm this thread for how to fix it. You are missing an dependency. Also make sure you use Java 7 for compile Java 8 is not recommended yet.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
Silesh.Nair said:
That's not it. It just works fine on debian, Ubuntu or mint. But never on Suse.
Click to expand...
Click to collapse
I have no Idea about Suse but it works on Ubuntu.
I suggest to look at the scripts code:
https://github.com/akhilnarang/scripts
Looks at the packages being installed for Ubuntu and Arch (the arch script). Find the equivalent package names for Suse.
Or just switch to Ubuntu. Even OEM use Ubuntu for Stock compilation.
Also make sure you use Java 7 for compilation as Java 8 is not recommended yet.
celoxocis said:
Check my post (post #8) I'm this thread for how to fix it. You are missing an dependency. Also make sure you use Java 7 for compile Java 8 is not recommended yet.
---------- Post added at 10:41 AM ---------- Previous post was at 10:38 AM ----------
I have no Idea about Suse but it works on Ubuntu.
I suggest to look at the scripts code:
https://github.com/akhilnarang/scripts
Looks at the packages being installed for Ubuntu and Arch (the arch script). Find the equivalent package names for Suse.
Or just switch to Ubuntu. Even OEM use Ubuntu for Stock compilation.
Also make sure you use Java 7 for compilation as Java 8 is not recommended yet.
Click to expand...
Click to collapse
Haha why ur telling to me tell that guy who have error
adityaupreti said:
Haha why ur telling to me tell that guy who have error
Click to expand...
Click to collapse
Ah well scrolled down thought your post was his (due to huge quote) and replied. He will get it when he checks the thread.
Code:
make: *** No rule to make target '/.txt', needed by '/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
Try installing the bc program.
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