I have a virtualbox setup, running ubuntu 16.04, everything is installed, i got everything being detected, synced repos, vendor/device/kernel trees also.. But when i try to build i keep keep getting error 127, i was trying to build a simple twrp using the omni brances from android 6.0, with p9000 device/vendor trees with minor modifications, i can detect it and start building, but it allways gives me that error.. what i wanna know, is what am i doing wrong? and if its possible for someone to tell me an example that works, by telling me which repos they used and what branches, so that i can verify if its an issue with how i configured my ubuntu and files.. Its my first time building from source, i would like to at least be able to build successfully once, any help will be apreciated.
Related
Hey Guys,
i don't know, if someone other than me have had this error in the past. I searched on Google and on XDA, but I didn't found something compairing to my Error.
I'm new to kernel compiling, so I don't have some information...please don't hit me that I'm doind something like this as my first time ! I want to learn how a kernel is going to be compiled. And as extra kick, it would be great if i can make my custom kernel for just my needs on my SE 2010 X10 Mini Pro
I read slade_87's Thread http://forum.xda-developers.com/showthread.php?t=1382917
I did all, setting up the Environment. Because of my slow Internet Connection, iI don't want to download the whole Android source, so I'm using this Toolchain https://sourcery.mentor.com/sgpp/lite/arm/portal/subscription3053. I'm doind all in a virtual Ubuntu 10.04 LTS 32bit in Vmware player 3.1.4 build-385536.
I copied the standart config from /arch/arm/configs/semc_mimmi/defconfig to .config, like in the Turtorial. I also made "ARCH=arm make menuconfig", no Problem. I didn't change anythine, because I thought I could make a mistake in the config, i just wanted to build the original source, to see if I can get this to work for some Experiments.
The Problem is when I'm executing the compile-command itself. When I'm entering "ARCH=arm CROSS_COMPILE=/home/android/kernel/arm-cc/bin/arm-none-eabi- make". After some lines....2-5 seconds or so.... i keep getting the error on the last few line in my attachment. I tried the cyanogenmod-kernel source, diffrent kernel source file from SE but i keep getting the same error, not on the same line, but always in linux/include/pagemap.h
I'm not so good in C, I'm some kind of BASIC junkie so i'm having quite a horror with C. But i thought, the Devs here, slade_87/doxian/D4rKn3sSyS/paul-xxx, don't have such simple errors, or they do know a way, how to get through this.
Could someone look at this ? Do you know a way of direction, where the error is coming ? I think, because it's always the same with different kernel source files, the errors on my side... but i can't think of any....
Thanks in Advance,
Lost Prophet
First off, I have been running Ubuntu 12.04 x64 (OpenJDK) for a while now, and build regularly for Grouper and d2usc (US Cellular SGS3 variant). Grouper builds fine, flashes fine, runs great. The d2usc also builds fine, flashes fine, but I get zero radio; no bars of any color, Settings - Status reports Unknown Baseband version, same with IMEI and MEID, not even showing grey roaming bars.
This has been going on for about 1-2 weeks now. Zero build errors, the "brunch d2usc" command works great, creates a flashable zip, and the zip flashes. I have to then wipe everything in TWRP, and restore a backup (I do NOT have to do adb nv restore or anything, radio works just fine when restoring backup for Black Bean 7).
Here's what I've tried:
1. Delete entire repo, create new folder and resync. After resync, build. Flash build (again, zero errors), same result.
2. Delete entire repo again, create new folder and resync. After resync, run ./get-prebuilts AND ./extract-files.sh while running official d2usc CM10.1 nightly. Rebuild (zero errors), same result.
At this point I'm at a loss, Grouper (N7) flashes and works great (obviously wifi only version). The d2usc version works great minus the fact that I get no radio, not even roaming. I've tried the CDMA subscription thing, rebooting, and no dice still.
I need some expert advise. Anyone that could provide some clues, suggestions, insight, would be greatly appreciated. It is much easier for me (saves time, etc) to do my personal theming THEN building, so I'm not doing things twice (using apktool to decompile/compile).
Thank you for your time!
-Ryan
-Sent from my US Cellular SGS3
I think I may have gotten to the bottom of this with invisiblek/termleech's help: Building from CM10.1's repo if you don't have the d2usc stuff, it'll sync what it needs straight from CM. That was fine and all. After talking with those two guys, there's another repo called TheMuppets where all the device vendor blobs are kept (which I had totally forgotten about). I had to add this to my Local_Manifest.xml to pull down those updated blobs from this repo.
I am sync'd up, and kicked off my build. That's gotta be it. I'll know in about 45 min to 1 hour.
RMarkwald said:
I think I may have gotten to the bottom of this with invisiblek/termleech's help: Building from CM10.1's repo if you don't have the d2usc stuff, it'll sync what it needs straight from CM. That was fine and all. After talking with those two guys, there's another repo called TheMuppets where all the device vendor blobs are kept (which I had totally forgotten about). I had to add this to my Local_Manifest.xml to pull down those updated blobs from this repo.
I am sync'd up, and kicked off my build. That's gotta be it. I'll know in about 45 min to 1 hour.
Click to expand...
Click to collapse
so how did that go?? i am curious as i am sync'd up but am lost due too my lack of ubuntu experience, also i jumped into learning this with no linux experience. i have the d2usc. i dont follow how github and my sync works together to build . but i hope yours works out
total noob here - web developer turned bad
I was wondering how to merge manufacturer source code into android source code? I see instructions every where for compiling android's source, and the manufacturer's source, and they all say "merge the source code", but they don't say how to do that. i've downloaded, via android's "repo" script, allllllllllllllllllllllllll 20gb of android source code (once it's setup), and i've also got all the LGE source code (for their hardware kernel drivers, i guess?). the instructions are pretty clear, but, there's that 1 damned step that is not clear for this noob "... And, merge the source into the android source code".
what i'm stuck on, is "HOW do i do that, and WHERE do i do that"? Do i just copy the manufacturer source into a specific android source folder, or what?
thanks in advance.
bump.... this is where i'm stuck at too. would like to build from pure source ATT/AOSP Have dl'ed both sources and need to be merged. I have seen several tutorials on building from source but they get vaige and want to use CM all the time. is it possible to do w/o CM? if so how.
Thank you also.
I also was unsure about that point, but after looking at the file, it seems pretty clear. Just extract the content of LGE-file to the android directory, as mentioned in the LGE Readme and overwrite existing files and try your luck with a compile. I tried it, but my installation of OpenJDK conflicts with building Android from sources. Maybe you've got more luck!
00001101 said:
I also was unsure about that point, but after looking at the file, it seems pretty clear. Just extract the content of LGE-file to the android directory, as mentioned in the LGE Readme and overwrite existing files and try your luck with a compile. I tried it, but my installation of OpenJDK conflicts with building Android from sources. Maybe you've got more luck!
Click to expand...
Click to collapse
Thanks for the suggestion, but still no such luck, I tried that and still fails at webcore(permissions denied) =I tried to build as user and as root user and still get some thing, I posted the error in the forums for my phone but no one has replied. but again thank you for the suggestion.
BTY, did you get the JDK to work?
Thanks for your feedback. I couldn't resist and installed Oracles Java version, just to see what problems might be left .
And of course, there came the final point, where I got a 'make no rule to make target' message while compilating, so the process stopped. First with pure AOSP and today with CM 11. Obviously I'm no coder, I just fiddle around with stuff, so there's unfortunatly where I have to give up. But it was interresting to learn a bit about the essentials
Did you have a look at this: http://code.google.com/p/android/issues/detail?id=38879
Following that, it might be, that there is a file missing in your sources?
Following many of the excellent CM building guides on xda as well as CM's wiki, I was able to quite smoothly get my virtual Ubuntu to begin building ICS. However, after about 5 minutes of it happily churning out binaries, the build stops complaining about being unable to recognize out/host/linux-x86/obj/EXECUTABLES/mksnapshot_intermediates/src/builtins.o while compiling V8. I've googled around but have not been able to find this particular error; also given my limited understaning of the build system on Linux am unable to diagnose this rather cryptic situation.
I've tried removing the entire out/host/linux-x86/obj/EXECUTABLES/mksnapshot_intermediates/ folder as well as starting afresh (after make clean) but the error does not go away. From what I've grepped, the recipe for builtins.o is inside builtins.P but not sure if this is where something goes meh.
I'm attaching my current build log as well as the builtins.P file. Will be grateful for any ideas on how to troubleshoot this further.
EDIT: building for Galaxy S i9000, but to me this seems like a more general build error and hence posting here. If you think this thread belongs elsewhere, please do let me know.
Hi everybody,
I'm currently in process of making my first builds of CM13 for my A310F.
The repositories for CM are unofficial, maintained by a user i tried to get in contact with, who didn't respond yet.
Now, while the stock kernel sources of MM are open sourced and a few hacks were already done in the unofficial CM repositories, the CM device/vendor/kernel sources are already a bit deprecated with a few erroneus configurations in the device repo, so I'm on my way to clean it up a bit.
Currently CM itself builds, but after booting most of the hardware features are broken and they were using the 5.1.1 kernel instead of the 6.0.1, and the blobs were not taken over correctly, or not all blobs were taken.
My question is now, how are you managing to get the correct list of the blobs needed? What is the best way to find out which blobs i need to take from the system.img?
I'm wondering the same thing. How do you know which blobs to pull in the first place when you're trying to build up the first rom?
There will be some dlopen errors for missing files in the logcat. After resolving them, it's mainly trial and error
Believe it or not, there is a method to this, and it requires some trial and error and a good sense of knowing what android needs to boot. If you look at the start up classpath and are just generally aware that the modem/network connection and filesystem utils need to be executed first (though for some reason binder and zygote can't start them themselves, despite the fact they are to running under init, but whatevs) so after bootloader hands off to kernel, you can go through the ramdisk and make sure all the on boot, on init on fs related libs/binaries are present. If you use a qcom device, just assume any lib or binary that starts with "libq" or even just the letter "q" is proprietary and required. Qcom is a bit full of themselves (ironic were talking about cm here) but anyways then there's the rild/crypto/fs libs and binaries. rngd, rmt_storage, rild daemons and anything that starts drmsever or netd will be required as well.
You can get significant hints from boot logs as well.
Aside from that, just keep note of what isn't produced by the aosp tree yet is present on the devices stock system, then determine how important it looks for android to able to start up