No rule to make target '[...]/kbuild/services4/srvkm/env/linux/osfunc.o', needed by '[...]kbuild/pvrsrvkm_sgx540_120.o' #3
Comments
|
You're correct - provided that you have the Android build system dependencies installed, simply syncing this project is enough to build any supported device. No need to pull in or extract anything else. That being said, your error message is really strange - I never seen that happen till now. Just to verify, here are the commands you should use to build tuna (otapackage is optional): Just to be sure, I'll run a freshly synced build later on to verify the behavior. |
|
I haven't had much time to look into this, but I decided to try and build the same synchronized source but different target directory on a fresh Ubuntu 14.04 (Lubuntu) install, to be sure I'm running in the same package environment as Google recommends. I hit the same issue where OpenJDK 1.7 is needed, not OpenJDK 1.8 like Google's official instructions say. I used exactly the commands above and it failed in the same manner. For the record, the source was synchronized with the git repository first checked out at commit 0243e8a (EDIT: Sorry, I now realize I don't need to use I had to look this up, but SGX refers to the PowerVR SGX540 graphics chip available on OMAP devices like Galaxy Nexus, not Intel's new 'Software Guard Extension' secure enclave technology available on new x86 CPUs (I saw references to Android x86 while building so I wasn't sure) I'll try and look into this issue more later this week |
|
After spending some time looking into it, I wasn't able to fix the issue. It looks like the issue is reproducible by other people. I came across commit 18120b3 on the android_device_samsung_tuna repositories' Android 7.0 Nougat branch, which removes the entire SGX_MODULES make target that was causing the build to fail for me. I don't know how important that kernel module is to correct operation of the ROM, so I'm not sure if it's a solution. (I should mention at one point (using make -j4 I think) the build somehow succeeded and produce some multigigabyte binaries (named system etc). I wasn't able to reproduce the build success after that, and given I didn't target an otapackage ZIP file I didn't want to risk flash the resulting images.) I considered doing a repo sync on a commit containing a prior working manifest.xml file, but I need to construct/obtain a manifest_static.xml file. An aside: It would be good to integrate some continuous integration infrastructure to automatically do a fresh build on every single commit. The free tiers on products like Travis CI have resource limits (timeouts less than a couple hours) so I don't think they're suitable (but they might be). I'll have a look how other community maintained AOSP projects do it. |
|
I have compiled the 7.0 Nougat branch without errors (using a modern i5-4590 8gb RAM than an older Core 2 Duo with 4gb RAM it took about 1.5 hours in total with first I used TWRP as my recovery and adb sideload to upload the ROM. After wiping all partitions (including system) except internal memory (/sdcard) and USB OTG. After flashing the ROM I produced with OpenGApps Nano, my phone stayed at the Android logo for 8 hours until I pulled the battery. I simply ended up using your aosp_n_tuna_2016-08-30.zip ROM, which booted and appears to be working fine. Assuming my Galaxy Nexus survives and prospers (I think its NAND flash memory is starting to die though), I might try again later and hopefully eventually contribute to this project. The problem would still be exhibited on the aosp-6.0 branch as of writing, but you may close this issue if you'd like. For completeness, I note I did encounter the following error during compilation: ...and the solution from here fixed my problem: export JACK_SERVER_VM_ARGUMENTS="-Dfile.encoding=UTF-8 -XX:+TieredCompilation -Xmx4g"
./prebuilts/sdk/tools/jack-admin kill-server
./prebuilts/sdk/tools/jack-admin start-server |
First off, it's pretty damn amazing to have a Galaxy Nexus Marshmallow AOSP ROM available after Google wasn't able to even release a 4.4 KitKat because TI dropped support for OMAP4. Great work guys!
That said, I was unable to build the ROM after doing a git checkout. I've ran the commands on the README.md in association to the AOSP build documentation. Also, as recommended by the AOSP documentation I am outputting to a separate physical drive, which happens to be mounted under a directory named '/vm'.
I am using Debian Stable (Jessie) and added jessie-backports to install OpenJDK 1.8 as suggested by the documentation. I was surprised when I ran the build script said it needed 1.7 contrary to the documentation, so I went ahead and installed OpenJDK 1.7 as well.
Anyway, after setting everything up, I ran a
make -j2(I am building on an older Core 2 Duo CPU). The build was going well for a few hours, until it got the following:(I tried again with just a
make(ie, single thread) and had same failure.)This is my first build of Android, so I may be doing something wrong. I'm very comfortable with git, but its the first time I'm using repo or doing an Android build.
Other than running the commands in the README.md, I don't believe there are any other git repositories I need to manually checkout other than this one...
The text was updated successfully, but these errors were encountered: