I am building a custom rom and I got into this error:
https://github.com/masterdoctor/Lin...i/LineageOS-|-Build-Tutorial-|-Huawei-P8-Lite
I used this tutorial for building the rom and done exactly what says in the tutorial.
I am at the step of building the rom,but command "croot" and "mka" don't work. It gives me "unknown command" and lists some apps with the same command.
Althrough, make command works, I did it in ~/android/system
It listed a LOT of code, after 3 minutes left me with this codeah,I forgot to copy it and I closed the terminal)
After 10 minutes of waiting:
This is what I got:
Running kati to generate build-aosp_arm.ninja...
No need to regenerate ninja file
Starting build with ninja
ninja: Entering directory `.'
ninja: error: '/.txt', needed by '/root/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp', missing and no known rule to make it
build/core/ninja.mk:151: recipe for target 'ninja_wrapper' failed
make: *** [ninja_wrapper] Error 1
[email protected]:~/android/system#
here is the code of "croot" too:
[email protected]:~/android/system# croot
No command 'croot' found, did you mean:
Command 'proot' from package 'proot' (universe)
Command 'root' from package 'root-system-bin' (universe)
Command 'chroot' from package 'coreutils' (main)
croot: command not found
[email protected]:~/android/system#
here is the code from "mka":
[email protected]:~/android/system# mka
No command 'mka' found, did you mean:
Command 'mkp' from package 'check-mk-server' (universe)
Command 'mkfa' from package 'julius' (multiverse)
Command 'mma' from package 'mma' (universe)
Command 'moka' from package 'alliance' (universe)
Command 'm-a' from package 'module-assistant' (universe)
mka: command not found
[email protected]:~/android/system#
Has someone an idea on how to fix this, please?I already filled my hdd from repo sync and I don't want to quit this project
It seems that you don't have installed all android building tools, talking about mka and croot.
If you're building with gbmasterdoctors guide: First go to /android/system folder and then run "source build/envsetup.sh" and then run command "lunch cm_hi6210sft-userdebug"
And then normally continue with "croot" and "mka"
Vika__ said:
If you're building with gbmasterdoctors guide: First go to /android/system folder and then run "source build/envsetup.sh" and then run command "lunch cm_hi6210sft-userdebug"
And then normally continue with "croot" and "mka"
Click to expand...
Click to collapse
, too late, I reinstalled Ubuntu 16.04 x64on my laptop and I'm doing everything from the start
Still, thx very much if this is the right solution
XTutorials said:
, too late, I reinstalled Ubuntu 16.04 x64on my laptop and I'm doing everything from the start
Still, thx very much if this is the right solution
Click to expand...
Click to collapse
Well. That works on cm13 so i guess its same for 14. Hopefully i helped :good:
Vika__ said:
If you're building with gbmasterdoctors guide: First go to /android/system folder and then run "source build/envsetup.sh" and then run command "lunch cm_hi6210sft-userdebug"
And then normally continue with "croot" and "mka"
Click to expand...
Click to collapse
I'm back, still with errors,tried to build CM 14.1, again LOS 14, again CM 14.1, again LOS 14...
I've got past the ninja error with an tweak in .bashrc, but now I get this error:
make: *** No rule to make target '/.txt', needed by '/root/android/system/out/target/common/obj/PACKAGING/checkpublicapi-cm-last-timestamp'. Stop.
[email protected]:~/android/system#
My question is, can you explain me how you builded CM 13? Not detailed, I know the essentials, but that step what are you saying with envsetup.sh and lunch cm_hi6210sft weren't in LOS 14 Tutorial.
P.S: I tried your fix many time for cm 14.1 and los 14, didn't work. When I lunch it was saying device not found in list or something almost the same, I think you understand.
Thanks in advance!
:good:
Related
Please, give me some help with a simple question about apt-get:
I can not find (to install) some programs like "vnc4server". Is this normal?
I have uncommented every line at /etc/apt/sources.lst .
And here is my console output:
[email protected]:~$ sudo apt-get install vnc4server
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package vnc4server is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
E: Package 'vnc4server' has no installation candidate
Click to expand...
Click to collapse
Thanks.
Can you please give me a hand with building my CM for the Nexus 7 GSM?
I have a number of problems.
When running "brunch tilapia" as specified in the CM tutorial for building for the Nexus 7 GSM, I get the following errors:
I don't get a zip file output in the "out" Directory
I am getting the following errors:
/bin/bash: flex: command not found
Warning: assignment from incompatible pointer type [enabled by deafult]
13: warning: extra tokens at end of #ifdef directive [enabled by default]
warning: 'fin' may be used uninitialized in this function [-Wmaybe-uninitialized
warning: implicit declaration of function 'read_all' [-Wimplicit-funtion-declaration]
You are attemtping to build with an unsupported version of java.
find: 'src' : no such file or directory
No private recovery resources for TARGET_DEVICE tilapia
Please help!
I tried wiping and re-installing, wiping the repo and re-initializing that.
I followed all the steps I believe, must just be unlucky.
Peace,
shandy1996
Perhaps you know this, but there is a thread for building cm10.1 for the n7 here: http://forum.xda-developers.com/showthread.php?t=1846651.
Some of the warnings you have listed are normal and are nothing to worry about. However, it looks like you are missing the package flex, so try 'sudo apt-get install flex', depending on what Linux distro you are using, then try again.
Thanks, but still one quiestion...
Why do I not get any .zip file output?
I am not sure as to why this is, but an answer would be much appreciated.
Thanks for you help, hopefully i can sort it out
Peace and thanks again,
shandy1996
It's because the build aborts as soon as it realizes that a required build package is missing. In a way it's kind of an all or nothing thing... you don't get a zip package until you have everything in place and set up properly.
Did you try installing the package 'flex' as suggested? I'm not positive, but that might be the issue, unless there are other errors or missing packages.
Also, have you posted in the thread on building cm10.1? You would probably get more help there!
I installed flex and it solved that error, but still no zip output.....
Ok ,what did it say at the end when it stopped? Also, what version of Linux are you using and what guide are you following? The guide linked in the other thread works great.
I used the guide on the CyanogenMod wiki for building for the Nexus 7 GSM.
I am running Ubuntu 12.10 64-bit.
The error i get at the end of the build process is:
Code:
make: *** No rule to make target 'vendor/asus/tilapia/proprietary/tf_daemone', needed by '/home/jacob/androis/system/out/target/product/tilapia/obj/EXECUTABLES/tf_daemon_intermediates/tf_daemon'. Stop.
ah ok, i had this exact same issue, i think it might be an internal thing, not your fault. for some reason the file tf_daemon seems to be missing, so someone suggested manually placing it in the proper place. i was directed to find the file here: https://github.com/AOKP/vendor_asus_grouper/tree/jb/proprietary/bin. so i downloaded it and put it in the folder /vendor/asus/tilapia/proprietary, and this problem was solved
I have been trying to build CM 10.2 all day and now keep getting errors while it is building. Here are the last few lines I am getting during the build before it stops. I am using Ubuntu 12.04 to build with.
Export includes file: external/strace/Android.mk -- /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/strace_intermediates/export_includes
Notice file: external/strace/NOTICE -- /home/mike/android/system/out/target/product/mako/obj/NOTICE_FILES/src//system/xbin/strace.txt
Import includes file: /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/vim_intermediates/import_includes
Export includes file: external/vim/src/Android.mk -- /home/mike/android/system/out/target/product/mako/obj/EXECUTABLES/vim_intermediates/export_includes
make: *** No rule to make target `vendor/lge/mako/proprietary/etc/DxHDCP.cfg', needed by `/home/mike/android/system/out/target/product/mako/system/etc/DxHDCP.cfg'. Stop.
make: *** Waiting for unfinished jobs....
Click to expand...
Click to collapse
Anyone have any ideas what my problem is?
mikeric said:
I have been trying to build CM 10.2 all day and now keep getting errors while it is building. Here are the last few lines I am getting during the build before it stops. I am using Ubuntu 12.04 to build with.
Anyone have any ideas what my problem is?
Click to expand...
Click to collapse
I think you don't have the proprietary blobs.
From http://wiki.cyanogenmod.org/w/Build_for_mako#Extract_proprietary_blobs
Now ensure that your Nexus 4 is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/mako directory (you can cd ~/android/system/device/lge/mako if necessary). Then run the extract-files.sh script:
$ ./extract-files.sh
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with "command not found" errors.
eris23 said:
I think you don't have the proprietary blobs.
From http://wiki.cyanogenmod.org/w/Build_for_mako#Extract_proprietary_blobs
Now ensure that your Nexus 4 is connected to your computer via the USB cable and that you are in the ~/android/system/device/lge/mako directory (you can cd ~/android/system/device/lge/mako if necessary). Then run the extract-files.sh script:
$ ./extract-files.sh
You should see the proprietary files (aka “blobs”) get pulled from the device and moved to the right place in the vendor directory. If you see errors about adb being unable to pull the files, adb may not be in the path of execution. If this is the case, see the adb page for suggestions for dealing with "command not found" errors.
Click to expand...
Click to collapse
I redid the proprietary files and now I am getting it to run for a while then getting this at the end while building. While it is extracting the proprietary blobs I am getting a lot of errors, but not adb errors.
target thumb C: openvpn <= external/openvpn/android.c
make: *** No rule to make target `vendor/lge/mako/proprietary/etc/DxHDCP.cfg', needed by `/home/mike/android/system/out/target/product/mako/system/etc/DxHDCP.cfg'. Stop.
make: *** Waiting for unfinished jobs....
In file included from external/openvpn/misc.h:30:0,
from external/openvpn/android.c:8:
external/openvpn/integer.h: In function 'index_verify':
external/openvpn/integer.h:106:5: warning: comparison of unsigned expression >= 0 is always true [-Wtype-limits]
external/openvpn/android.c: In function 'env_set_add_android':
external/openvpn/android.c:29:18: warning: initialization discards 'const' qualifier from pointer target type [enabled by default]
external/openvpn/android.c:25:9: warning: unused variable 'and_env_value' [-Wunused-variable]
Click to expand...
Click to collapse
Does anyone have any suggestions?
Sent from my Nexus 4 using Tapatalk 4
Is your n4 already running cm10.2?
If not the blobs would be wrong and some are named different in cm10.1
Edit: try to extract the missing file from an official nightly
Sent from my Nexus 4 using xda premium
OK I'll try that, thanks for the suggestion
Sent from my Nexus 4 using Tapatalk 4
I am running cm10.2 nightly 8/15 and tried to pull the proprietary blobs and kept getting all these errors. If I try and build it still wont. This is just a few of the errors.
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b00': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b01': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b02': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.b03': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/firmware/keymaster/keymaster.mdt': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libdrmdecrypt.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libWVStreamControlAPI_L1.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libwvm.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/libwvdrm_L1.so': Permission denied
cannot create '../../../vendor/lge/mako/proprietary/vendor/lib/drm/libdrmwvmplugin.so': Permission denied
Click to expand...
Click to collapse
Looks like you messed up the permissions in your build env ...
Repo sync -d
Might solve this
Sent from my Nexus 4 using xda premium
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Restl3ss said:
I know, I know. I'm probably gonna get a lot of "it can't be done and this is why" if what I've googled is any indication. However, difficult does not equate to impossible.
Firstly, one of the big messages I encountered online was that windows is not case sensitive, thus it can't be done even if you had a toolchain. However, it's entirely possible to turn windows 100% case sensitive (i've got cygwin mkdir Abc and aBc to prove it)
So to do this, go to control panel / programs / turn windows features on or off.
When opened, check the box that says "subsystem for UNIX-based applications" and hit okay.
Now open a browser window. Download This.
Install it, and on options near the beginning of the install check EVERYTHING.
Reboot at the end of the installation. Windows is now fully case-sensitive.
So now, after repo sync and running through the motions (get-prebuilts, breakfast, extract-files, etc)
I now encounter problem number two. Javac: command not found.
So to get around this, download an unofficial build of openjdk-1.7.0 and manually drop it in cygwin.
So after this, I type brunch d2lte
I now encounter problem number three. Build info comes up but ends abruptly at
bash: schedtool: command not found
or something like that anyway. Googling schedtool reveals information about what it does. So, to get rid of the error message, I create a dummy schedtool binary and drop it in cygwin's bin folder. Doesn't fix the build, but makes that nasty error go away.
So now, both brunch and mka will display build info then return you promptly to the command line with no error. However, what does work is the "make" command.
So, I type make bootimage.
Here comes problem number 4.
I get an error message for build/core/java.mk on line 23, saying my target SDK is invalid (here's my version), (here's available)
or something like that.
So to fix, open build/core/java.mk in notepad++, navigate to line 23, and remove the following
Code:
$(error $(LOCAL_PATH): Invalid LOCAL_SDK_VERSION '$(LOCAL_SDK_VERSION)' \
Choices are: $(TARGET_AVAILABLE_SDK_VERSIONS))
else
After which, your build will move forward to..... error number 5
Code:
make: *** No rule to make target '/home/Swisgaar/android/system/out/host/windows-x86/bin/mkbootimg.exe', needed by '/home/Swisgaar/android/system/out/target/product/d2lte/boot.img'. Stop.
Which i fixed, by downloading a .exe version of mkbootimg and dropping it in system/out/host/windows-x86/bin manually, which you can get from here.
After which, moving on to the next error, and the one i'm currently stuck on,
Code:
make[1]: Entering directory '/home/Swisgaar/android/system/kernel/samsung/d2'
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:327: /home/Swisgaar/android/system/kernel/samsung/d2/scripts/Kbuild.include: No such file or directory
make: *** empty variable name. Stop.
/home/Swisgaar/android/system/kernel/samsung/d2/Makefile:416: recipe for target 'scripts_basic' failed
make[2]: *** [scripts_basic] Error 2
Makefile:130: recipe for target 'sub-make' failed
make[1]: *** [sub-make] Error 2
make[1]: Leaving directory '/home/Swisgaar/android/system/kernel/samsung/d2'
build/core/tasks/kernel.mk:169: recipe for target '/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config' failed
make: *** [/home/Swisgaar/android/system/out/target/product/d2lte/obj/KERNEL_OBJ/.config] Error 2
Currently working on a fix. Any help is appreciated.
This experiment really isn't necessary, but it's just that, an experiment. I figure, this is my hobby, so why not.
Click to expand...
Click to collapse
Hey bro you are doing such a good thing for developers so please continue this thread and make some thing new
All the best :good:
hi all
we have included this device in open devices project
you can check news about project on
http://developer.sonymobile.com/know.../open-devices/
feel free to fork, build, fix and push back
Br
J
Wohooo! Finally! [emoji106] [emoji2] [emoji3]
Excellent! An AOSP ROM is the only thing I can think is missing from an otherwise perfect device.
GCC here we come..
Andoroid L (5.0) code, binaries and guides are published
No working camera or modem, looks like we've still got awhile guys...
great news,thankss
nice
I'm syncing it now. I'm going to do a blind build (not changing anything just going with what's already there) because I have yet to unlock my bootloader and won't until they can figure out a way so at least the camera and noise cancellation don't get messed up when unlocking (if I go back to a sony stock rom I know it won't matter on AOSP)
graffixnyc said:
I'm syncing it now.
Click to expand...
Click to collapse
Preparing to build as well. Like you, I haven't BL unlocked and won't until the DRM issues are resolved.
jerpelea said:
Andoroid L (5.0) code, binaries and guides are published
Click to expand...
Click to collapse
Your work is really appreciated. FYI, I convinced a friend to buy a Z3C in large part due to your AOSP commitment. [emoji106]
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
illogic6 said:
Guessing we'll need to reverse engineer the camera and modem binaries? Is that right?
Click to expand...
Click to collapse
no
Reverse Engeneering
In other words - SONY will deliver the required drivers or better all required driver will be there in a while...
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
m0d said:
I get compile error:
Code:
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c: In function 'bta_av_audio_sink_getconfig':
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: error: 'p_sink' undeclared (first use in this function)
if (bta_av_co_audio_sink_has_scmst(p_sink))
^
external/bluetooth/bluedroid/main/../btif/co/bta_av_co.c:557:52: note: each undeclared identifier is reported only once for each function it appears in
make: *** [out/target/product/aries/obj/SHARED_LIBRARIES/bluetooth.default_intermediates/../btif/co/bta_av_co.o] Error 1
make: *** Waiting for unfinished jobs....
help appreciated
Click to expand...
Click to collapse
just re sync your tree and fix is there
That inform you in: <insert the cpu thread number of your computer> ??? Please
I got a build to finish. I'll post the boot and system img for someone to try.. I'm not going to go through the trouble yet to make a flashable zip until we at least know it boots. I'll upload the images now
Posted the images: http://forum.xda-developers.com/z3-compact/development/img-aosp-5-0-boot-imgs-t2940499
So @NisseGurra flashed the build I made yesterday here is what he found to be broken:
no wifi, no network, some reboots, no usb storage, no external sd, no sound or camera
But its very snappy, looking forward to a functional aosp
Thank you for the guides,
I was able to compile AOSP for D5803 successfully.
A couple of issues,
First,
Has the Cherry-Pick for external/libnfc-nci/ that is provided in the guide been merged?
As I get the following error,
Code:
/external/libnfc-nci $ git cherry-pick 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
fatal: bad object 83cf98d0a5018e023eb9cc8b4e394957f9a6989f
(Updated on blog to correspond with Shinano Issue.)
Second,
I get the following error when I try to output zipped package,
Code:
[B]No private recovery resources for TARGET_DEVICE aries
No recovery.fstab for TARGET_DEVICE aries[/B]
make: *** no rule to make target `otapackage'. stop.
Does this have anything to do with: TARGET_BOOTLOADER_BOARD_NAME := D5803
or that it is called aosp_d5803 (aosp_d5803.mk)
UPDATE: otatools seems to work, [" . build/envsetup.sh && time lunch aosp_d5803-userdebug && make otatools "].
But I can not find the output / output directory for package
Oh,
Is there supposed to be a userdata.img too?
Looking around a different sources mention it, however there is no userdata.img when I compiled it.
Thank you for your time