yashsingh1/xdaforums huggingface dataset:
[Galaxy S I9000 Android Development] kasper_h:
AMD X2 64bit 2.8GHz with 3GB RAM.

Completely clean build for galaxysmtd takes about 3 hours.

And I like CarbonROM, runs perfect :)
[Galaxy S I9000 Android Development] ts1506:
Out of curiosity, do you guys use CCACHE ? If yes , how much space have you allocated.

For me , it takes about 3 hours for a make clobber build , am looking at ways of speeding it up.

Core i5-2400 Quad core @ 3.1 to 3.4 GHz

8GB DDR3 RAM

2x 1TB 7200rpm 64MB Cache HDD

Radeon HD6670 GDDR5

Ubuntu 13.04
[Galaxy S I9000 Android Development] kasper_h:
Your specs should allow faster build, way better than my build PC....

I have 10GB CCACHE.
[Galaxy S I9000 Android Development] ts1506:
Thanks , I will try CCACHE to see if it helps.

Make clobber builds are a pain.
[Galaxy S I9000 Android Development] kasper_h:
I usually do a "rm -rf out/target/product/galaxysmtd". Prevents problems on rebuilds, but a build takes only 60-70 minutes in stead of 180 after a make clobber.
[Galaxy S I9000 Android Development] :
'make clean' should be enough in most cases. 'make clobber' is if you really change a lot, I mean really a lot. You can read in the Makefile what it really "cleans". With a 'make clean' and using ccache you should get the fastest builds. I had ~16 GB of ccache-cache when my pa builds (4.1.2) finished.

Btw. you can monitor the current status of ccache with 'watch -n1 -d ccache -s' on another console/terminal/shell.
[Galaxy S I9000 Android Development] The_Wolf91:
I've successfully compiled (ported from source) a rom for my I9000 (galaxysmtd) but the recovery cannot wipe anything (data/cache/dalvik) and can't flash because it is unable to mount any partitions (system/data/datadata for example). The only workaround is to flash another kernel to get it working, but I want to build with that problem fixed already.... what would be the problem? Here is my local_manifest.xml

<project name="android_device_samsung_galaxysmtd" path="device/samsung/galaxysmtd" remote="cm" revision="cm-10.1"/>

<project name="android_packages_apps_SamsungServiceMode" path="packages/apps/SamsungServiceMode" remote="cm" revision="cm-10.1"/>

<project name="android_device_samsung_aries-common" path="device/samsung/aries-common" remote="cm" revision="cm-10.1"/>

<project name="android_kernel_samsung_aries" path="kernel/samsung/aries" remote="cm" revision="cm-10.1"/>
[Galaxy S I9000 Android Development] kasper_h:
You could look in the out/target/product/galaxysmtd/recovery/root

Here are all the files that end up in the building of recovery. It should contain a .fstab file where all partitions to be mounted are specified.

Verstuurd van mijn GT-I9000
[Galaxy S I9000 Android Development] The_Wolf91:
There is no ".fstab" but there is a "fstab.aries" which contains this:

# Android fstab file.
#<src> <mnt_point> <type> <mnt_flags and options> <fs_mgr_flags>
# The filesystem that contains the filesystem checker binary (typically /system) cannot
# specify MF_CHECK, and must come before any filesystems that do specify MF_CHECK

# LVM Volumes
/dev/lvpool/system /system ext4 ro wait
/dev/lvpool/userdata /data ext4 noatime,nodev,nosuid,nomblk_io_submit,errors=panic wait,encryptable=footer

EDIT

In "out/target/product/galaxysmtd/recovery/root/etc" there is a file called "recovery.fstab" which contains these strings:

# mount point	fstype	device	options (length for cryptfs encryption footer)

/recovery	mtd	recovery
/boot	mtd	boot
/radio	mtd	radio

/data	ext4	/dev/lvpool/userdata length=-16384
/cache	yaffs2	cache
/datadata	yaffs2	datadata

/sdcard	vfat	/dev/block/mmcblk0p1 lun=/sys/devices/platform/s3c-usbgadget/gadget/lun0/file
/system	ext4	/dev/lvpool/system

/external_sd	vfat	/dev/block/mmcblk1p1 lun=/sys/devices/platform/s3c-usbgadget/gadget/lun1/file

EDIT 2

Clockworkmod's log when I try to "wipe data/factory reset"

I:Checking for extendedcommand...
I:Skipping execution of extendedcommand, file not found...
W:failed to mount /dev/lvpool/userdata (No such file or directory)
I:Can't format unknown volume: /emmc

Entire log here: http://pastebin.com/u1L3CduL

EDIT3

I tried to "install from sdcard" the update.zip of Titanium Backup. The first CWM's log is from my compiled rom (CM stock kernel), the second after flashing Mackay Kernel (last version):

CM Stock Kernel

-- Installing: /sdcard/TitaniumBackup-6.0.5.zip
Finding update package...
I:Update location: /sdcard/TitaniumBackup-6.0.5.zip
Opening update package...
Installing update...

about to run program [/sbin/busybox] with 3 args
mount: mounting /dev/lvpool/userdata on /data failed: No such file or directory
run_program: child exited with status 255
package_extract_file: can't open /data/app/com.keramidas.TitaniumBackup.apk for write: No such file or directory
unmount of /data failed; no such volume
script result was [Done !]
Installing Titanium Backup 6.0.5 ...
Done !

Mackay Kernel

-- Installing: /sdcard/TitaniumBackup-6.0.5.zip
Finding update package...
I:Update location: /sdcard/TitaniumBackup-6.0.5.zip
Opening update package...
Installing update...

about to run program [/sbin/busybox] with 3 args
Installing Titanium Backup 6.0.5 ...
script result was [Done !]
Done !

Any help? Please, it is depressing... :(
[Galaxy S I9000 Android Development] iyahman:
yop guys

can you tell me why when i disable

export PATH=$PATH:/home/iyahman/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

in my bashrc. and do a make clobber I can still build my rom ? I mean I just have no link now to my toolchain. no?

I have see this cause I want to build my rom with linaro and I suppose I need to change

export PATH=$PATH:/home/iyahman/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin

to my linaro directory. but before I add this i have try to disable the cyanogen toolchain without succes visibly.
[Galaxy S I9000 Android Development] DerTeufel1980:
The toolchain is defined in one of the *.mk files in the build dir. Can't remember which one currently

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
I have said before in this thread that these lines in bashrc are useless, because they are overridden by the build-scripts.

If you want to move to linaro toolchain (which will not work for cm10.1 by the way without massive code changes), you should look at the android_build project of other ROMs that are build using Linaro (e.g. carbondev).
[Galaxy S I9000 Android Development] kasper_h:
E.g.

https://github.com/CarbonDev/android_build/commit/90834385dc6bda878f9a8a0359721a79e77e0633
[Galaxy S I9000 Android Development] The_Wolf91:
Any idea? :(
[Galaxy S I9000 Android Development] kasper_h:
It is really odd the problem you have. It looks as if the LVM partitions (/data & /system) don't get mounted properly.

You are using a pure stock CM10.1 build? Source is completely up-to-date?
[Galaxy S I9000 Android Development] The_Wolf91:
I'm building from source an hybrid ROM based on AOKP which is not "officialy" supported by I9000 and yes, I update source regularly...
[Galaxy S I9000 Android Development] kasper_h:
It looks as if something goes wrong with the recovery ramdisk. Do you use your own device/samsung/aries-common & kernel/samsung/aries trees or you use the CM10.1 ones?
[Galaxy S I9000 Android Development] The_Wolf91:
I'm using the CM10.1 ones: I've added device/samsung/aries-common & kernel/samsung/aries in local_manifest
[Galaxy S I9000 Android Development] DerTeufel1980:
Are you sure your repos are at cm-10.1 branch. If you added it manually, one of the repos could be checked out wrong

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
I really have no idea then how to explain this....
[Galaxy S I9000 Android Development] The_Wolf91:
Yes, here it is:

<project name="android_device_samsung_aries-common" path="device/samsung/aries-common" remote="cm" revision="cm-10.1"/>

<project name="android_kernel_samsung_aries" path="kernel/samsung/aries" remote="cm" revision="cm-10.1"/>
[Galaxy S I9000 Android Development] driodmaster92:
i have a Linux installed with a 100gb partition and now i want to expand my partition without re installing Linux ...i read there are scripts to do this but i could not find....
[Galaxy S I9000 Android Development] kasper_h:
I have done so in the past using an ubuntu live-CD
[Galaxy S I9000 Android Development] DerTeufel1980:
If I were you, I would delete device/samsung and maybe also kernel/samsung/aries and bootable/recovery completely.

Then run

. build/envsetup.sh && brunch galaxysmtd

Roomservice should grep everything for you then.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] kasper_h:
+1

Would be the best option now.
[Galaxy S I9000 Android Development] The_Wolf91:
I've deleted folders you said, but there isn't "roomservice.py" in /build/tools in based AOKP rom, in fact after giving ". build/envsetup.sh && brunch galaxysmtd" it gave me an error which said that there aren't the folders needed. So, after deleting those folders, I repo synced and then started a clean build. I will let you know if it works or not! :)
[Galaxy S I9000 Android Development] ts1506:
Use gparted to shrink the other partition, and add it to your linux one.
[Galaxy S I9000 Android Development] The_Wolf91:
Build compiled, but what you said didn't fixed problem...
[Galaxy S I9000 Android Development] aways:
if you are building pure cyanogenmod you can't have this issue .
[Galaxy S I9000 Android Development] The_Wolf91:
I'm not building a pure CyanogenMod, I'm building from (source) an AOKP based rom which is not supported for I9000 and I'm using galaxysmtd tree from CyanogenMod.
[Galaxy S I9000 Android Development] aways:
from where are you using vendor/samsung ?
[Galaxy S I9000 Android Development] The_Wolf91:
From The Muppets's github: https://github.com/TheMuppets/proprietary_vendor_samsung, but I've extracted proprietary files from my phone with "./extract-files.sh"
[Galaxy S I9000 Android Development] kasper_h:
And what did you do to the device tree to get the ROM to compile (AOKP does not compile with stock CM trees).
[Galaxy S I9000 Android Development] The_Wolf91:
I don't know if it is the right answer, but I edited Malcho's galaxysmtd.mk from here http://rootaxbox.no-ip.org/malcho/AOKP Beast/ to correct Rom's specific paths and have added galaxysmtd in vendorsetup.sh and AndroidProducts.mk properly.
[Galaxy S I9000 Android Development] aways:
hardware/samsung*
[Galaxy S I9000 Android Development] The_Wolf91:
Included in Manifest.xml: <project path="hardware/samsung" name="android_hardware_samsung" remote="cm" revision="cm-10.1" />
[Galaxy S I9000 Android Development] aways:
what rom are you building ?
[Galaxy S I9000 Android Development] The_Wolf91:
https://github.com/ReVolt-ROM
[Galaxy S I9000 Android Development] aways:
maybe problem from sources ask to [MENTION=3524398]rubervalrf[/MENTION] have same problem or not i think rubervalrfl have to compile Revolt.
[Galaxy S I9000 Android Development] rubervalrfl:
Yes I had the same problem and solved with a indirect help your Aways, I just copied the overlays of galaxysmtd galaxysBmtd for my folder, and problem solved.
[Galaxy S I9000 Android Development] The_Wolf91:
I don't understand where did you copy /device/samsung/galaxysmtd/overlay folder?
[Galaxy S I9000 Android Development] rubervalrfl:
Sorry, when Aways spoke thought it was the error of intersisf, I decided to put it this way, what you are having the same error, I compile the Revolt normal only for I9000B.
[Galaxy S I9000 Android Development] The_Wolf91:
My problem is that CWM is unable to mount data and system in recovery, so it's impossible to flash apps or wipe data/system. But the compiled ROM works well, it's only a recovery problem (I discovered that flashing a custom kernel instead of stock CM, recovery works as it should).
[Galaxy S I9000 Android Development] rubervalrfl:
This happened to me on another ROM, I think that is because of the images that are too big for the i9000 cwm.

Try to compile with the semaphore.
[Galaxy S I9000 Android Development] kasper_h:
Max size is 7.5MB = 7.5*1024*1024 = 7864320 bytes

For the boot.img
[Galaxy S I9000 Android Development] The_Wolf91:
Mine (stock CM) is 6.2MB... So it's not due to it, right?
[Galaxy S I9000 Android Development] DerTeufel1980:
If it would be a space issue, kernel would not be booting at all, and you would need to Odin back.

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] aways:
if you can't fix, compile rom and use or share it with another kernel
[Galaxy S I9000 Android Development] kasper_h:
Off course that is the final solution if nothing else works :)

At the same time, it is curious how some things simply do not work whereas for other they do. My ICS kernel was always build with the ramdisk implementation of stratosk with separate kernel building. After moving to JB, this did not boot for me. Stratosk has been very helpful in sending me files, I have been trying all sort of things with file permission. But it simply wouldn't work. That was when I switched to using CyanogenMod inline kernel building... but it still feels bad I gave up on it ;)
[Galaxy S I9000 Android Development] The_Wolf91:
I would have liked to share ROM with Mackay Kernel included, so a couple of day ago I asked him how to do it and I choose to replace the boot.img & kernel modules in the ROM zip instead of "get the mackay kernel branch & device aries-common device tree and build with it", because the second method gave me some errors (and I'm not completely sure on what to add in local_manifest to include Mackay Kernel in my ROM). It booted regularly and worked well, BUT I tried to flash an update.zip of Titanium Backup, which had to install a backed up app. It seemed that all went good, but when I tried to reboot system I got a bootanimation's loop (really don't know why..). The strange thing is that if I compile the ROM with stock kernel and then flash Mackay Kernel, it works well (also tested flashing an "update.zip" in recovery).
[Galaxy S I9000 Android Development] rubervalrfl:
Really I could not solve this mystery, but as already compile the kernel for semaphore I9000B, when this happens I put it going good, funny that installs everything correct, only that CWM is bug.
[Galaxy S I9000 Android Development] driodmaster92:
/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S: Assembler messages:

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldr r6,[ r5,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldr r6,[ r5,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

/home/aditya/illu/kernel/samsung/aries/arch/arm/kernel/entry-armv.S:42: Error: ARM register expected -- `ldreq r6,[ lr,#0x00 ]'

make[3]: *** [arch/arm/kernel/entry-armv.o] Error 1

getting this with cm and semaphore kernel both
[Galaxy S I9000 Android Development] DerTeufel1980:
Remove the spaces in your [ something ]

Edit: you are building with 4.8 toolchain, aren't you? You also should take a look at memset fixes (from linux 3.9 I believe), or use slab memory allocator instead of slub (not recommended), to make the kernel boot

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] DerTeufel1980:
Please report back if it worked

Gesendet von meinem GT-N7105 mit Tapatalk 2
[Galaxy S I9000 Android Development] rodman01:
LZMA arch/arm/boot/compressed/piggy.lzma
/bin/sh: lzma: not found

Looks like you don't have lzma installed.[/QUOTE]

I have this lzma error message too, but cannot find how and were to install the lzma...can someone please help me to the right way :confused:?

The for me strage thing is that I already got my rom compiled a few days ago. But then i mixed up something and "destroyed" my working tree. Now I did a complete new repo sync and that twice...but still the same error: lzma:command not found...
[Galaxy S I9000 Android Development] kasper_h:
sudo apt-get install lzma
[Galaxy S I9000 Android Development] rodman01:
Thanks for the quick answer, but unfortunately no success: sudo: apt-get: command not found

I am on or with mac os, if this perhaps is a relevant information, but without sudo it is not installing too
[Galaxy S I9000 Android Development] rodman01:
WOW I finally got it fixed a couple of minutes ago :good:...I repaired the volume of my pc and the permissions with board tools and now the build process went through without errors and I have the rom.zip again. So lzma was already installed, but for some reasons and all my tries, I must have messed up some files and permissions.

n-x86/framework/signapk.jar -w build/target/product/security/testkey.x509.pem build/target/product/security/testkey.pk8 /var/folders/52/h2pwpg6n72z8kc5gmt7ll2z00000gn/T/tmpfSCHcx /Volumes/myandroid/android/system/out/target/product/galaxysmtd/cm_galaxysmtd-ota-0daaf82983.zip
done.
Package Complete: /Volumes/myandroid/android/system/out/target/product/galaxysmtd/cm-10.2-20131006-UNOFFICIAL-galaxysmtd.zip
[Galaxy S I9000 Android Development] yadavjpr:
Need Help

Hello,

I am trying to build CM11 on my machine but build failed. Here is logs:

http://pastebin.com/cCss4k3L

I see adb: not found logs when I run extract-files.sh script. See below logs:

http://pastebin.com/dKb5GAeb

Thanks in advance.
[Galaxy S I9000 Android Development] aways:
copy from any SGS rom modem.bin into out/target/product/galaxysmtd/
[Galaxy S I9000 Android Development] yadavjpr:
Thanks, after some googleing, I found that I need to create a symlink of adb in /usr/local/bin/

Now working fine :)
[Galaxy S I9000 Android Development] yadavjpr:
I am getting error when I build ROM today. It was working fine before ~10 days. Can someone help me.

http://pastebin.com/NNK2BHkv

Thanks
[Galaxy S I9000 Android Development] iyahman:
Do a "make clean" before rebuild
[Galaxy S I9000 Android Development] jayc137:
Kernel: arch/arm/boot/Image is ready
AS arch/arm/boot/compressed/head.o
CC arch/arm/boot/compressed/misc.o
CC arch/arm/boot/compressed/decompress.o
/bin/sh: 1: Syntax error: ";" unexpected
make[2]: *** [arch/arm/boot/compressed/piggy.] Error 2
make[2]: *** Waiting for unfinished jobs....
CC crypto/md4.mod.o
CC drivers/char/broadcom/gist.mod.o
CC drivers/char/broadcom/sigmorph.mod.o
CC drivers/char/frandom/frandom.mod.o
CC drivers/net/wireless/bcmdhd/dhd.mod.o
CC fs/cifs/cifs.mod.o
LD [M] crypto/md4.ko
LD [M] drivers/char/broadcom/gist.ko
LD [M] drivers/char/broadcom/sigmorph.ko
LD [M] drivers/char/frandom/frandom.ko
LD [M] drivers/net/wireless/bcmdhd/dhd.ko
LD [M] fs/cifs/cifs.ko
make[1]: *** [arch/arm/boot/compressed/vmlinux] Error 2
make: *** [zImage] Error 2

Getting this when compiling using XZ Compression,

Never mind guys solved it by modifying my arch/arm/boot/compressed/Makefile

Had to add

suffix_$(CONFIG_KERNEL_XZ) = xzkern
[Galaxy S I9000 Android Development] Blue59:
hey how did you fix it? Anyone can help me please? i can't solve that same error hastebin.com/zowigaxewo.vbs
[Galaxy S I9000 Android Development] DerTeufel1980:
Remove the spaces inside the brackets
[Galaxy S I9000 Android Development] pmos69:
Also look here for a couple of workarounds: https://www.virtualbox.org/ticket/6620

I am actually using VMWare at the moment.
[Galaxy S I9000 Android Development] pmos69:
Can you list all the pacman packages you had to install? (arch uses pacman, right?)

I'll update the OP with that if you provide info.
[Galaxy S I9000 Android Development] rycus86:
OK, so I ended up running the extract-files script from cygwin under Windows.

It pulled the files that copied them back to Ubunto.

Started compiling then got some errors and that's when I found out that I have to use an x64 OS: https://groups.google.com/forum/#!msg/android-building/61CoTjyGg_o/3tMYEfyVwnEJ

So, lets do it again from the beginning... :)

(PS: I did not know that VirtualBox now supports x64 guest operating systems...)
[Galaxy S I9000 Android Development] pmos69:
:/

Will update the OP...

[done]
[Galaxy S I9000 Android Development] pmos69:
Updated OP, replacing manual manifest editing with breakfast.
[Galaxy S I9000 Android Development] kasper_h:
Just out-of-curiosity. Why the specific need for the oracle java jdk 1.6. I am using openjdk to build CM9 without any issues...
[Galaxy S I9000 Android Development] pmos69:
Not a specific need.

I simply had to choose a version that works to include in the guide.

This one works. Others can work too.

The objective is: Follow the guide and get guaranteed results.
[Galaxy S I9000 Android Development] rycus86:
All right so got my first build compiled. :)

Here's my extra for building in VirtualBox:

The guest OS has to be an x64 system, Ubuntu 12.04 in my case (VirtualBox info said that even x86 host OSes can run x64 clients however it's not optimal...)

VirtualBox doesn't like Samsung USB so no ADB from virtualbox.

To get the required files from my device I installed Cygwin on my Win7Pro then copied the extract scripts from the galaxysmtd and aries-common directories under system/devive/samsung folder to a Cygwin directory.

I modified the target path of download and commented the last lines of the scripts to skip setup-something.sh. Running these two scripts pulled the files from my phone.

I copied these files/folders to the appropriate directories on Ubuntu (the original paths in the script) then executed the setup scripts (aries-common first then galaxysmtd but I think it doesn't matter). After that I just followed the remaining steps from tutorial, great work by the way, thank you wery much.

Another workaround for the non-working ADB would be to extract the required files from a semi-official CM10 build but I was too lazy to pick them by hand according to the list txt file.

Please note that I didn't try to flash the build yet, it's a bit late here. :)
[Galaxy S I9000 Android Development] pmos69:
All I see is that ramdisk.IMG and ramdisk-recovery.IMG are missing or could not be opened, so the error should be prior to this.
[Galaxy S I9000 Android Development] elitevet:
:confused: open-files limit ?

cyanobacter@cyanobuilder:~/android/system/kernel/samsung/aries$ ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
scheduling priority (-e) 0
file size (blocks, -f) unlimited
pending signals (-i) 15885
max locked memory (kbytes, -l) 64
max memory size (kbytes, -m) unlimited
open files (-n) 1024
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
real-time priority (-r) 0
stack size (kbytes, -s) 8192
cpu time (seconds, -t) unlimited
max user processes (-u) 15885
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
[Galaxy S I9000 Android Development] pmos69:
I don't have that issue on a default Ubuntu install
[Galaxy S I9000 Android Development] elitevet:
Yeah, bad sync again on kernel_samsung_aries... Done git clone on it overnight - it ended with no errors (had to use -j2, anything more or without the option would produce hungups and resolving errors). Syncing now...

sent from CM10 powered SGS
[Galaxy S I9000 Android Development] gangstaboy13:
Thanks for this awesome guide compiling 20120808 ofcourse without problems!
[Galaxy S I9000 Android Development] mierkat09:
Would this work with the galaxy s 4g? Or would i have to port it?
[Galaxy S I9000 Android Development] gangstaboy13:
When are the sources of 20120808 online? Every time I do repo sync and then compile I'll get an old version of cm10 help?