Guest t0mm13b Posted July 18, 2011 Report Posted July 18, 2011 (edited) A question for those of you who has built CM7 from source - am running a compile right now, question is this, out of curiousity, how do you get CM7 to compile for VMSPLIT2G option? :) By default, the build scripts compile CM7 under VMSPLIT3G.... Reasoning for curiousity - take the gb leaked rom's kernel which is VMSPLIT2G, drop it into the VMSPLIT2G CM7 rom and away you go (or so the theory goes... could be wrong here - dunno) Cheers :) Edited July 18, 2011 by t0mm13b
Guest wbaw Posted July 18, 2011 Report Posted July 18, 2011 Kallt Kaffe made some patches, Burstlam compiled it last month:
Guest t0mm13b Posted July 18, 2011 Report Posted July 18, 2011 Kallt Kaffe made some patches, Burstlam compiled it last month: Ahh okie, cheers, is there a environment variable you set to trigger that or something extra you supply on the command line along with . build/envsetup.sh && brunch blade Peace out :)
Guest wbaw Posted July 18, 2011 Report Posted July 18, 2011 (edited) Ahh okie, cheers, is there a environment variable you set to trigger that or something extra you supply on the command line along with Peace out :) No, it's much more involved than that. Kallt Kaffe made an incomplete set of vmsplit 2g patches to get cm7 running on another device with no kernel source (might have been the v9, zte & huawei seem to be the main gpl offenders), Burstlam patched it a bit more, but gave up with a few things still not working. Maybe you could pm Burstlam to see what he did & if there's anything you can do to get a few more things working. Edited July 18, 2011 by wbaw
Guest t0mm13b Posted July 18, 2011 Report Posted July 18, 2011 No, it's much more involved than that. Kallt Kaffe made an incomplete set of vmsplit 2g patches to get cm7 running on another device with no kernel source (might have been the v9, zte & huawei seem to be the main gpl offenders), Burstlam patched it a bit more, but gave up with a few things still not working. Maybe you could pm Burstlam to see what he did & if there's anything you can do to get a few more things working. IIRC, there was a approved submission to Gerrit for VMSPLIT2G option, the unknown quantity is how to trigger it! :D
Guest wbaw Posted July 19, 2011 Report Posted July 19, 2011 IIRC, there was a approved submission to Gerrit for VMSPLIT2G option, the unknown quantity is how to trigger it! :D Maybe try adding TARGET_USES_2G_VM_SPLIT := true To BoardConfig.mk Burstlam should be able to help more. I only just compiled my first plain vanilla build the other day.
Guest t0mm13b Posted July 19, 2011 Report Posted July 19, 2011 (edited) Maybe try adding TARGET_USES_2G_VM_SPLIT := true To BoardConfig.mk Burstlam should be able to help more. I only just compiled my first plain vanilla build the other day. Cheers for the above B) Congrats on your first plain vanilla build! \o/ B) Did the same here - CM7 build on a Atom N270 - its certainly doable - 4hrs!!! lol!!! Torture test for it mind you it did break on its own - segmentation fault 3 times and had to re-start it.... but it did produce this at the end of it all the hard work :D Package complete: /home/t0mm13b/CyanogenMod/out/target/product/blade/update-cm-7.1.0-RC1-Blade-KANG-signed.zip (Will try it out later on after I give the Atom - what with protons/neutrons/electrons a rest - LOL) Edited July 19, 2011 by t0mm13b
Guest wbaw Posted July 19, 2011 Report Posted July 19, 2011 (edited) My Phenom gets through it pretty quickly, nowhere near 4 hours, more like 40 minutes, you should try using a proper cpu ;) I felt like a proper Gentoo user, I usually rarely compile anything if I can avoid it. Doing the first repo sync took forever though. You'll probably need more patches, some kernel modules, leaked rom wifi driver & a few other things to get it all working. Edited July 19, 2011 by wbaw
Guest t0mm13b Posted July 19, 2011 Report Posted July 19, 2011 My Phenom gets through it pretty quickly, nowhere near 4 hours, more like 40 minutes, you should try using a proper cpu ;) I felt like a proper Gentoo user, I usually rarely compile anything if I can avoid it. Doing the first repo sync took forever though. You'll probably need more patches, some kernel modules, leaked rom wifi driver & a few other things to get it all working. My next paycheck - hunt for a decent workhorse ;) This was done on Arch Linux, compiling away with KDE4.6.3 running :) in fairness - it handled it like Atlas no problem and handled it well :)
Guest Phoenix Silver Posted July 19, 2011 Report Posted July 19, 2011 In my laptop atom 330 take quite 2 hours to compile In my home server complete branch take 40 mins (correct 40 mins) But good idea to have all in 2g. :)
Guest wbaw Posted July 20, 2011 Report Posted July 20, 2011 Need to either be patient & wait for zte to release some kind of .35 source, or hassle the life out of them until they start doing things properly & set up a github, imo. Using an illegal binary blob kernel without source & making the rest of CM7 fit it is the wrong way to do things.
Guest wbaw Posted July 20, 2011 Report Posted July 20, 2011 (edited) it doesnt seem to build with the vmsplit 2g patches :( target Prelink: libc (out/target/product/blade/symbols/system/lib/libc.so) build/tools/apriori/prelinkmap.c(100): build/core/prelink-linux-arm-2G.map:26 base 0x6ff00000 out of range. make: *** [out/target/product/blade/symbols/system/lib/libc.so] Error 1 make: *** Waiting for unfinished jobs.... [edit] - normal build done in 10 minutes though, you need to trade in those atom cpus. Edited July 20, 2011 by wbaw
Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 (edited) it doesnt seem to build with the vmsplit 2g patches :( target Prelink: libc (out/target/product/blade/symbols/system/lib/libc.so) build/tools/apriori/prelinkmap.c(100): build/core/prelink-linux-arm-2G.map:26 base 0x6ff00000 out of range. make: *** [out/target/product/blade/symbols/system/lib/libc.so] Error 1 make: *** Waiting for unfinished jobs.... [edit] - normal build done in 10 minutes though, you need to trade in those atom cpus. Okie - thanks for letting me know... Weird that it was approved on gerrit and committed to repo :blink: And yeah I'll give the atom the shift when pay day happens \o/ :D Edited July 20, 2011 by t0mm13b
Guest wbaw Posted July 20, 2011 Report Posted July 20, 2011 (edited) I think burstlam said somewhere he had to alter it to get it to build for the blade, but I don't know what he did. Kallt submitted those patches to get it to build for an unofficial build he was doing for another device, iirc. Edited July 20, 2011 by wbaw
Guest sm4tik Posted July 20, 2011 Report Posted July 20, 2011 My next paycheck - hunt for a decent workhorse ;) This was done on Arch Linux, compiling away with KDE4.6.3 running :) in fairness - it handled it like Atlas no problem and handled it well :) How did you handle python-python2,symlinking?Just wondering how much work would it need to edit the build scripts etc. instead.. might need python3 one day and the symlink will be useless.
Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 How did you handle python-python2,symlinking?Just wondering how much work would it need to edit the build scripts etc. instead.. might need python3 one day and the symlink will be useless. Simple! I have $HOME/bin as the first directory in the $PATH environment variable, and symlinked to the python2 binary instead of python3 binary. ;) No further work needed nor editing any scripts. Oh and by the way, the build will guarantee to fail on a CPU that has hyperthreading - read, NON-DUAL core processor.... B) :D
Guest sm4tik Posted July 20, 2011 Report Posted July 20, 2011 Simple! I have $HOME/bin as the first directory in the $PATH environment variable, and symlinked to the python2 binary instead of python3 binary. ;) No further work needed nor editing any scripts. Oh and by the way, the build will guarantee to fail on a CPU that has hyperthreading - read, NON-DUAL core processor.... B) :D Oh I see,I've just symlinked it in /usr/bin..bad,I know ;) Btw, 3GHz pIV,no problems with building CM7,if you don't consider time a problem :D
Guest t0mm13b Posted July 20, 2011 Report Posted July 20, 2011 Oh I see,I've just symlinked it in /usr/bin..bad,I know ;) Btw, 3GHz pIV,no problems with building CM7,if you don't consider time a problem :D Cool! :D No problem symlinking to the python2 binary - it can always be removed as its a temporary work-around :) Just on the big machine (not netbook), Intel® Pentium® 4 CPU 2.80GHz, make crashes the whole build process.... :huh:
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now