Kernel Compile Problem - Honor 5X Questions & Answers

I'm trying to compile a kernel from the many source works in progress, but for some reason I'm getting hung up on this error (in several places, both __before_atomic and __after_atomic):
<> error: implicit declaration of function ‘smp_mb__before_atomic’ [-Werror=implicit-function-declaration] <>
I'm running Ubuntu 14.04 on it's own drive (not virtual machine).
I've searched google and haven't found much that helps. I'm obviously missing something but I can't figure it out. Ugh
Any help would be appreciated.

Related

Best way to compile Busybox?

After searching around , it seems there are several ways to compile Busybox.
Codesourcery toolchain direct compile method
http://mobisocial.stanford.edu/news/2011/02/compile-busybox-on-android-os/
http://omappedia.org/wiki/Android_Installing_Busybox_Command_Line_Tools
Running make gives:
gcc: error trying to exec 'cc1': execvp: No such file or directory
What exact folder belongs in the path?
What exact statement belongs for the cross compiler prefix in make menuconfig?
Source integration method
https://github.com/Gnurou/busybox-android
This method wants you to include the files with the android source and rebuild.
Is there a way to instead compile this directly?
Scripted NDK compile method
http://matrixrewriter.com/wiki/tiki-index.php?page=Building+BusyBox+binaries+for+Android
This method goes well until near the end of the script when the script returns:
/usr/include/string.h.274: error: expected ')' before '!=' token
I am completely lost after searching for this error.
Which of these three methods, if any, is best? Is there another easier way?

[I9001][REQ][Kernel] 3.0.x I9001

Hi, I'm VisualTech48 and i own a Galaxy S Plus (I9001).
Our great Developers [Arco98, Ivendor, Doomsday98, Oisis, etc.] are developing ICS Roms and trying to make Jelly Bean too but we are missing a key element of this game.
It's the 3.0.x Kernel. We really need a good coder.
If anyone knows, or can help us code this kernel we are Ready to donate, and help by giving logs if even needed.
If we donate to someone, he/she must:
Help our devs with codeing
Give us a booting kernel
We have done allready a part of the project but we need help with codeing, that is why I even started this thread.
What has oisis done:
Added board-ariesve.c here:
arch/arm/mach-msm/board-ariesve.c
Included Ariesve board to Kconfig and Makefile.
Added missing files:
include/linux/fsa9480.h
arch/arm/mach-msm/include/mach/msm_reqs.h
Click to expand...
Click to collapse
Compilation error:
Code:
arch/arm/mach-msm/board-ariesve.c: In function 'pm8058_gpios_init':
arch/arm/mach-msm/board-ariesve.c:329: error: variable 'sdcc_det' has initializer but incomplete type
arch/arm/mach-msm/board-ariesve.c:330: error: unknown field 'direction' specified in initializer
arch/arm/mach-msm/board-ariesve.c:330: warning: excess elements in struct initializer
error, forbidden warning: board-ariesve.c:330
make[1]: *** [arch/arm/mach-msm/board-ariesve.o] Error 1
What needs to be done:
include and port file from 2.6.35.X - arch/arm/mach-msm/board-ariesve.c
include/find missing drivers for i9001
Click to expand...
Click to collapse
We whould really apriciate if someone can help us because this kernel can open a whole new page for our phone.
Why did i remade a new thread? Because i think we have more chances of reply then in the I9000 Forum.
Thank you for reading this, VisualTech48
Original Thread: http://forum.xda-developers.com/showthread.php?t=1742976

[Q] [CM10.2] libhardware_legacy not compiling because of wifi

Hi!
I'm trying to compile my first cyanogen rom for my Galaxy 3 (i5800). I downloaded the Android source from androidarmv6 and the device folder from marcellusbe's repo and i edited it to include samsung fimg drivers (original device folders has openfimg which IMHO is still not good for daily usage because of lag, very limited opengles support etc...) and the device configuration and filesystem table to support MTD converted phones. At first compiling went pretty good i just got some: "Thumb does not support this addressing mode *" that i fixed by adding
Code:
LOCAL_CFLAGS += -marm
to involved Android.mk however after resolving those errors it started compiling host libraries and it started giving TONS of no such file or directory errors, but compilation didn't stop so i didn't touch anything, then this error appeared and i can't find any patch/solution/workaround:
Code:
target thumb C: libhardware_legacy <= hardware/libhardware_legacy/wifi/wifi.c
hardware/libhardware_legacy/wifi/wifi.c: In function 'update_ctrl_interface':
hardware/libhardware_legacy/wifi/wifi.c:473:5: warning: suggest parentheses around assignment used as truth value [-Wparentheses]
hardware/libhardware_legacy/wifi/wifi.c: In function 'wifi_start_supplicant':
hardware/libhardware_legacy/wifi/wifi.c:894:20: error: dereferencing pointer to incomplete type
hardware/libhardware_legacy/wifi/wifi.c:911:26: error: dereferencing pointer to incomplete type
make: *** [/home/francesco/cm10_port/cm_armv6/out/target/product/apollo/obj/SHARED_LIBRARIES/libhardware_legacy_intermediates/wifi/wifi.o] Error 1
I also downloaded the latest wifi.c from cyanogen github but nothing.
Someone knows how to resolve this?
Thanks in advance!

[Q] Cross compiling Python module using Android gcc Long bit error

I am attempting to compile Python along with the modules "openssl pil zope2" for Android using the "Python-for-android" project (https://github.com/kivy/python-for-android).
However it is not successful and errors out with the below error:
Code:
Getting distribution for 'zope.security==3.7.4'.
In file included from
/home/zac/Documents/Projects/Apps/python-for-android/build/hostpython/Python-2.7.2/Include/Python.h:58:0,
from src/zope/security/_proxy.c:19:
/home/zac/Documents/Projects/Apps/python-for-android/build/hostpython/Python-2.7.2/Include/pyport.h:849:2:
error: #error "LONG_BIT definition appears wrong for platform (bad
gcc/glibc config?)."
[B]#error "LONG_BIT definition appears wrong for platform (bad gcc/glibc
config?)."[/B]
^
src/zope/security/_proxy.c: In function 'init_proxy':
src/zope/security/_proxy.c:1006:3: warning: dereferencing type-punned
pointer will break strict-aliasing rules [-Wstrict-aliasing]
Py_INCREF(&SecurityProxyType);
^
error: Setup script exited with error: command
'arm-linux-androideabi-gcc' failed with exit status 1
An error occurred when trying to install zope.security 3.7.4. Look
above this message for any errors that were output by easy_install.
While:
Installing test.
Getting distribution for 'zope.security==3.7.4'.
Error: Couldn't install: zope.security 3.7.4
What I am wondering is if anyone else has ever had a similar issue when trying to use the Android gcc, I have build zope.security just fine using the ARM gcc so it is not a platform issue but some bug/issue with the provided Android gcc in the NDK

[help] Anything defined in cpufreq.h is causing implicit declaration problems

Hi, I'm build cyanogenmod with CAF kernel LA.BR.1.1.3-05510-8x16.0 with small modifications. I'm running into a problem where any function defined in include/linux/cpufreq.h is causing implicit declaration warnings, which are treated as errors. I know I can use cc call-disable, but that is likely to cause errors later on. I have uploaded a log of building and the error, and the defconfig I'm using to build the kernel. http://1drv.ms/1QyaAXD Any help would be appreciated.
zowpow said:
Hi, I'm build cyanogenmod with CAF kernel LA.BR.1.1.3-05510-8x16.0 with small modifications. I'm running into a problem where any function defined in include/linux/cpufreq.h is causing implicit declaration warnings, which are treated as errors. I know I can use cc call-disable, but that is likely to cause errors later on. I have uploaded a log of building and the error, and the defconfig I'm using to build the kernel. http://1drv.ms/1QyaAXD Any help would be appreciated.
Click to expand...
Click to collapse
Hi,
I've been into same error;
It mostly happens when you try to compile 64 bit kernel for a device that is currently running 32 bit one.
I FIXED mine by by removing the '-Werror' related warnings. Go to the main Makefile in your kernel directory and search for 'werror' whatever the error is; remove the lines or use '#' before to comment it out.

Categories

Resources