I get this error when I run make command while compiling Android kernel. Please help me.
kurtulus145 said:
I get this error when I run make command while compiling Android kernel. Please help me.
Click to expand...
Click to collapse
Send a text file containing the entire log right from command execution or .sh file execution. Also which phone and processor are u developing on?
KingRaheel said:
Send a text file containing the entire log right from command execution or .sh file execution. Also which phone and processor are u developing on?
Click to expand...
Click to collapse
I upload on attachments.
Device: Asus Memopad 7 ME176CX
Processor: Intel Atom Z3745
kurtulus145 said:
I upload on attachments.
Device: Asus Memopad 7 ME176CX
Processor: Intel Atom Z3745
Click to expand...
Click to collapse
Did u try compiling again using a fresh copy of source? What exact changes did u make? Did u use menuconfig command? Is your source code on github? You should tell all this when u need help else we may not be able to help u out efficiently.
KingRaheel said:
Did u try compiling again using a fresh copy of source? What exact changes did u make? Did u use menuconfig command? Is your source code on github? You should tell all this when u need help else we may not be able to help u out efficiently.
Click to expand...
Click to collapse
No other source file is available. I have not made any changes to the source code. I have edited some things with menuconfig command. No source code in Github. I downloaded it from Asus's site.
kurtulus145 said:
No other source file is available. I have not made any changes to the source code. I have edited some things with menuconfig command. No source code in Github. I downloaded it from Asus's site.
Click to expand...
Click to collapse
What i meant by fresh copy is the downloaded kernel files from asus website which has no alterations done by youto it. Try compiling it without doing any changes using menuconfig or any other command and see if u get the zImage. If u do then use menuconfig and apply one change at a time,compile and see if it causes issues. From your log its clear that some change has caused instability to most of the kernel modules. Kernel building is not easy.
If u want attention of other developers then upload your source code on github and post link here. Can't assure attention but it may help:good:
KingRaheel said:
What i meant by fresh copy is the downloaded kernel files from asus website which has no alterations done by youto it. Try compiling it without doing any changes using menuconfig or any other command and see if u get the zImage. If u do then use menuconfig and apply one change at a time,compile and see if it causes issues. From your log its clear that some change has caused instability to most of the kernel modules. Kernel building is not easy.
If u want attention of other developers then upload your source code on github and post link here. Can't assure attention but it may help:good:
Click to expand...
Click to collapse
I tried the make command without making any changes with the menuconfig command. I got the same error again. I upload source code on GitHub.
I uploaded github.
Link:https://github.com/kurtulus145/k013_kernel
Help!!!
Related
Can anybody compile mkbootimg for linux x86? Since the one's I found in other threads dosen't have --base support. And I don't understand how you compile the mkbootimg.h :/
Here you go.
Simple advice: do an android generic build so you'll get lots of usefull tools compiled.
Reagards
gecka said:
Here you go.
Simple advice: do an android generic build so you'll get lots of usefull tools compiled.
Reagards
Click to expand...
Click to collapse
Thx, I want to do that but don't know how, new to linux and android development
Everything explained here:
http://source.android.com/download
gecka said:
Everything explained here:
http://source.android.com/download
Click to expand...
Click to collapse
Thx, I know that one, but not how to compile the code :/
behnaam said:
Thx, I know that one, but not how to compile the code :/
Click to expand...
Click to collapse
Well it is explained....
Building the code
To build the files, run make from within your working directory:
$ cd ~/mydroid
$ make
Click to expand...
Click to collapse
Just start following the steps and tell me if you have a problem.
How could i compile mkbootimg?
Download AOSP
. build/env_setup.sh (Make sure your SHELL is bash(Or at least not zsh)
make mkbootimg
Or
make mkbootimg mkbootfs fastboot adb
(If you have to do a full build you can but for few tools might as well not).
I now this thread is a bit old, but there may be some people able to solve my problem here..
unrandomsam said:
Download AOSP
. build/env_setup.sh (Make sure your SHELL is bash(Or at least not zsh)
make mkbootimg
Or
make mkbootimg mkbootfs fastboot adb
(If you have to do a full build you can but for few tools might as well not).
Click to expand...
Click to collapse
That works indeed! And I am on OS X with MacPorts. Thanks guys!
Now… I needed to compile a different mkbootimg, the one that makes use of md5, for the bcm21553 CPU family. I had the full directory with the Android.mk and the .c file. I solved removing the mkbooting directory from the AOSP and putting this new one instead.
Isn't there any other way? I hoped it was just a matter of writing make in the new module/tool directory after setting the environment but such isn't the case.
And another thing: what the heck are the .mk files?? Are they specific to the Android SDK? I can't find anything in Internet.
hi xda community,
i am trying to make my own kernel for xperia sp. i am following http://forum.xda-developers.com/showthread.php?t=1748297
i am stuck at step 5, part B.
When i type make '/home/jk-chaos/android/kernel/sony/205/kernel/arch/arm/configs/viskan_huashan_defconfig'
or make viskan_huashan_defconfig
this comes up
"make: Nothing to be done for `/home/jk-chaos/android/kernel/sony/205/kernel/arch/arm/configs/viskan_huashan_defconfig'."
"make: *** No rule to make target `viskan_huashan_defconfig'. Stop."
i am just compiling stock kernel, no other additions.
using ubuntu 14.04
please guide me to further get this working
afterwards i will add features to this kernel which i need. ofcourse the features u people create and provide. ALL WITH YOUR HELP.
Will be Appreciated,
J.K.
Your best bet is to ask in the thread that you linked to...unfortunately your links are broken...
a tool for you to Edit current Boot images.
http://forum.xda-developers.com/general/general/tool-abime-android-boot-image-editor-t2847426
worked fine afterwards when i corrected kernel source path. :good:
thanks to @pec0ra for pointing that out
Hi,
It's nice to see new people making kernels
I think this error happens when the file isn't found.
What you should check :
That the file exists (double check that you entered the right name)
That the file has correct permission (user jk-chaos should be able to read it)
That you execute the command from the right directory : You must be in your kernel root folder when you "make". In your terminal it must look like :
Code:
~/android/kernel/sony/205/kernel$
Tell me if it isn't any of this and I'll look into it more deeply.
Regards,
pec0ra
Click to expand...
Click to collapse
mods plz close the thread
Hi everyone,
i've downloaded keyguard source from AOSB Github (https://github.com/AOSB/android_frameworks_base/tree/kitkat/packages/Keyguard), and after made all changes i need, i would like to compile/build it as an .apk, but i don't know how to do that
Someone can help me please ?
I'm using Windows.
I will be grateful to people who give me answers
Android Studio ☺
worf_1977 said:
Android Studio ☺
Click to expand...
Click to collapse
Thank you for your help.
But i when i try to build it, i've git an error and it says:
Error:FAILURE: Build failed with an exception.
* What went wrong:
Task 'assemble' not found in root project 'Keyguard'.
* Try:
Run gradle tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output.
Click to expand...
Click to collapse
Any idea ? :/
EDIT: I solved it; but after make project, i don't know where is my apk :X
EDIT²: When i try to build it with eclipse, i've got 1271 errors
Bump, any other ideas ? :/
It should be placed into your $OUT folder, whatever would it be...
Hey. I am following modpunk tread on CM 12.1 build for Samsung Galaxy Alpha.
I have done almost all the steps in the README.
Now I wonder how I copy proprietary vendor files.
The README only tell me to run "./extract-files.sh", cant find where this hidden file is located.
Here is the steps in the README;
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Thanks in advance.
protruckker said:
Hey. I am following modpunk tread on CM 12.1 build for Samsung Galaxy Alpha.
I have done almost all the steps in the README.
Now I wonder how I copy proprietary vendor files.
The README only tell me to run "./extract-files.sh", cant find where this hidden file is located.
Here is the steps in the README;
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Thanks in advance.
Click to expand...
Click to collapse
http://wiki.cyanogenmod.org/w/Build_for_klte Just one as an example, I'm using klte.
The guide states you can find it under
SOURCECODEFOLDER/device/Samsung/CODENAME
Where SOURCECODEFOLDER is the folder where you downloaded the cyanogenmod source code (repo sync) and CODENAME is the code name for your device.
For Samsung devices, if you are getting any errors related to the building of some system applications like "TimeService.apk", I'd suggest you to use the files hoted at " TheMuppets" github repository.
I have done the "repo sync". After this big download I am going to directory:
"cyanogenmod/system/device/"
In this directory I only have these folders:
Common, Generic, Google, Qcom and Sample
protruckker said:
I have done the "repo sync". After this big download I am going to directory:
"cyanogenmod/system/device/"
In this directory I only have these folders:
Common, Generic, Google, Qcom and Sample
Click to expand...
Click to collapse
Can you put the link of the guide you are trying to follow? It seems like you are missing the step "breakfast", probably because there's no official build for your device. You are trying to port cyanogenmod, right?
Inviato dal mio SM-G900F utilizzando Tapatalk
Ciuffy said:
Can you put the link of the guide you are trying to follow? It seems like you are missing the step "breakfast", probably because there's no official build for your device. You are trying to port cyanogenmod, right?
Inviato dal mio SM-G900F utilizzando Tapatalk
Click to expand...
Click to collapse
yep, I am trying to port it.
Here is the "guide" I am following. Its just a readme with the build steps.
URL:
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
protruckker said:
yep, I am trying to port it.
Here is the "guide" I am following. Its just a readme with the build steps.
URL:
git.cryptomilk.org/projects/android/android_device_samsung_slte.git/tree/README?h=cm-12.1
Click to expand...
Click to collapse
Not a definitive answer, but it looks like something has gone wrong with your syncing. As you can see from the readme, the manifest should include "projects/android/android_device_samsung_slte.git" and
"projects/android/android_kernel_samsung_slte.git". By looking at the file tree of the _device_ one, there is actually a file called "extract-files.sh". Use an utility like "locate" or a search bar in your desktop manager to see if you actually have this file, as the repo sync should have cloned the git repository!
Ciuffy said:
Not a definitive answer, but it looks like something has gone wrong with your syncing. As you can see from the readme, the manifest should include "projects/android/android_device_samsung_slte.git" and
"projects/android/android_kernel_samsung_slte.git". By looking at the file tree of the _device_ one, there is actually a file called "extract-files.sh". Use an utility like "locate" or a search bar in your desktop manager to see if you actually have this file, as the repo sync should have cloned the git repository!
Click to expand...
Click to collapse
I think I have found the problem. I did spell a folder name wrong. Think thats it.
protruckker said:
The repo is about 50 Gb so should I try to sync it again?
Click to expand...
Click to collapse
50? You sure? Have you tried using the -c option while syncing? My CM 12.1 source code is working and it's "merely" 25 GBs or less.
Anyway, if you are missing *every* file from that git repo, you definetely should. Make also sure the manifest file that the readme tells you to create includes everything as shown! Check first if you are missing only some files... At the very least, you might just download the missing extract-files from that git repo.
Ciuffy said:
50? You sure? Have you tried using the -c option while syncing? My CM 12.1 source code is working and it's "merely" 25 GBs or less.
Anyway, if you are missing *every* file from that git repo, you definetely should. Make also sure the manifest file that the readme tells you to create includes everything as shown! Check first if you are missing only some files... At the very least, you might just download the missing extract-files from that git repo.
Click to expand...
Click to collapse
The problem was that I spelled the "local_manifests" folder wrong.
Now I have a "Samsung" folder in there.
Thanks
protruckker said:
The problem was that I spelled the "local_manifests" folder wrong.
Now I have a "Samsung" folder in there.
Thanks
Click to expand...
Click to collapse
Great! Have fun with your ported Cyanogenmod. Glad I could help.
We have a button dedicated just to thanks!
Hi,
I was wondering if anyone with the expertise would know how to compile a module that was made for marshmallow to bring it to nougat. Sadly the developer has abandoned the project and closed the xda thread, while not responding to messages.
https://forum.xda-developers.com/xposed/modules/lp-knock-code-screen-t3272679
that is the module in question. I have tried to decompile the apk and recompile after making a few changes, however it just worsened the case.
mindzombies said:
Sadly the developer has abandoned the project and closed the xda thread, while not responding to messages.
Click to expand...
Click to collapse
Any chance you cloned its git repo? Not only he won't answer any message but he had the incredibly selfish-prick act of deleting the git repo for Knock code so no one can work on it!
acidrums4 said:
Any chance you cloned its git repo? Not only he won't answer any message but he had the incredibly selfish-prick act of deleting the git repo for Knock code so no one can work on it!
Click to expand...
Click to collapse
acidrums4 said:
so no one can work on it!
Click to expand...
Click to collapse
Nor kang it!
Sent from my lithium using XDA Labs
Yep, that is the main reason I haven't been able to work on it myself. Nor am i good enough to reverse engineer the apk.
Here you have the source code.
I haven't the ability to work on it for myself and it would be safer if someone more capable would do it, but at least i gave you the source code and hope it'a useful.
I would recommend you as well to open a new thread with the source code link on first page to get more people to work on it and hope we can get the knock code back.
Big ups, tell me if it was helpful.
https://drive.google.com/file/d/1bDILNuiQSCIOx2BXDGxpagGf6UeoerbJ/view?usp=drivesdk
Edit: remember this is a non-flashable zip, in case you were wondering, it's the apk just decompiled, unzip it and inside you have the whole amount of java files that contain the source code
You will need an app able to unzip files and read java files.
Otherwise download it to your computer (recommended)