Database Develop

error building kernel

Hi guys first of all HI TO EVERYBODY!!!!
I'm new to this forum and hope you will help me....
I recently bought a brand new phone, an LG-P990.
I would like to build my personal rom and kernel so I followed this guide
http://forum.xda-dev...d.php?t=1104523
and all went ok but when I saw that there were not any kernel source code in it I decided also to follow the following
http://wiki.cyanogen...nel_from_source
but when I finally launch the compilation with:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
after few minutes I have the following error message:
http://pastebin.com/z5udP72j
how to fix it???
thank you in advance,
Matteo

84matte84 said:
Hi guys first of all HI TO EVERYBODY!!!!
I'm new to this forum and hope you will help me....
I recently bought a brand new phone, an LG-P990.
I would like to build my personal rom and kernel so I followed this guide
http://forum.xda-dev...d.php?t=1104523
and all went ok but when I saw that there were not any kernel source code in it I decided also to follow the following
http://wiki.cyanogen...nel_from_source
but when I finally launch the compilation with:
make ARCH=arm CROSS_COMPILE=$CCOMPILER -j`grep 'processor' /proc/cpuinfo | wc -l`
after few minutes I have the following error message:
http://pastebin.com/z5udP72j
how to fix it???
thank you in advance,
Matteo
Click to expand...
Click to collapse
what is the definition of the $CCOMPILER ?

vadonka said:
what is the definition of the $CCOMPILER ?
Click to expand...
Click to collapse
as stated in the guide...the CCOMPILER is
CCOMPILER=${HOME}/android/system/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi-

Try compile with another toolchain? Linaro?
Sent from my LG-P990 using XDA App

fajarep said:
Try compile with another toolchain? Linaro?
Click to expand...
Click to collapse
why not....but how to do that????

if you have a recent version of ubunut/debian try this:
apt-get update
apt-get install gcc-arm-linux-gnueabi
then define the CCOMPILER like this:
CCOMPILER=arm-linux-gnueabi-

fajarep said:
Try compile with another toolchain? Linaro?
Click to expand...
Click to collapse
I tried with
CCOMPILER="/home/matteo/android/system/prebuilt/linux-x86/toolchain/arm-linux-androideabi-4.4.x/bin/arm-linux-androideabi-
but I have another error now
drivers/mmc/host/sdhci.c: In function 'sdhci_suspend_host':
drivers/mmc/host/sdhci.c:1652: error: too few arguments to function 'mmc_suspend_host'
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
make: *** Waiting for unfinished jobs....
what to do now??? changing toolchain until find a working one?

vadonka said:
if you have a recent version of ubunut/debian try this:
apt-get update
apt-get install gcc-arm-linux-gnueabi
then define the CCOMPILER like this:
CCOMPILER=arm-linux-gnueabi-
Click to expand...
Click to collapse
same error with gnueabi
drivers/mmc/host/sdhci.c: In function ‘sdhci_suspend_host’:
drivers/mmc/host/sdhci.c:1652:2: error: too few arguments to function ‘mmc_suspend_host’
include/linux/mmc/host.h:285:12: note: declared here
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2

84matte84 said:
same error with gnueabi
drivers/mmc/host/sdhci.c: In function ‘sdhci_suspend_host’:
drivers/mmc/host/sdhci.c:1652:2: error: too few arguments to function ‘mmc_suspend_host’
include/linux/mmc/host.h:285:12: note: declared here
make[3]: *** [drivers/mmc/host/sdhci.o] Error 1
make[2]: *** [drivers/mmc/host] Error 2
make[1]: *** [drivers/mmc] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
what kernel source you have?

vadonka said:
what kernel source you have?
Click to expand...
Click to collapse
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6

84matte84 said:
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6
Click to expand...
Click to collapse
Is note the same as the device because my device has a
2.6.32.49-cyanogenmode kernel...

84matte84 said:
following the guide I pulled the kernel from the device...
however in the .config I have the following
"Linux/arm 2.6.37.6 Kernel Configuration"
So i think 2.6.37.6
Click to expand...
Click to collapse
how can you pulled the kernel source from the device?
Are you have the cyanogenmod source? or miui or else?
i suggest that pull the latest cm kernel from the cyanogenmod github.

vadonka said:
how can you pulled the kernel source from the device?
Are you have the cyanogenmod source? or miui or else?
i suggest that pull the latest cm kernel from the cyanogenmod github.
Click to expand...
Click to collapse
Sorry I did not pulled the kernel source but the kernel config as suggested in the tutorial...
I'm working with cyanogenmod source following the cyanogenmod wiki tutorial here
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source

84matte84 said:
Sorry I did not pulled the kernel source but the kernel config as suggested in the tutorial...
I'm working with cyanogenmod source following the cyanogenmod wiki tutorial here
http://wiki.cyanogenmod.com/wiki/Building_Kernel_from_source
Click to expand...
Click to collapse
apt-get update
apt-get install git
git clone git://github.com/CyanogenMod/lge-kernel-star.git
then try with this source

vadonka said:
apt-get update
apt-get install git
git clone git://github.com/CyanogenMod/lge-kernel-star.git
then try with this source
Click to expand...
Click to collapse
this time the kernel compile without problems...now how to load it in the phone? Can I continue following the cyanogenmod wiki???
thank you for your help...

84matte84 said:
this time the kernel compile without problems...now how to load it in the phone? Can I continue following the cyanogenmod wiki???
thank you for your help...
Click to expand...
Click to collapse
I'm sorry if im raw, but why you deal with this? if you dont make any change in the kernel source just use the precompiled cm7 kernel.
im not exactly understand your motive.

vadonka said:
I'm sorry if im raw, but why you deal with this? if you dont make any change in the kernel source just use the precompiled cm7 kernel.
im not exactly understand your motive.
Click to expand...
Click to collapse
This is my first step...for now I need to build an unchanged source and load it on my phone....after when I will able to load a compiled kernel in the phone correctly I will need to modify it...for my university studies...

but because of is the first time I'm asking you the correct steps because I don't want to brik the phone

84matte84 said:
but because of is the first time I'm asking you the correct steps because I don't want to brik the phone
Click to expand...
Click to collapse
i understand.
in that case the kernel zimage in the "/arch/arm/boot" directory.
you also need to copy all file what have the ".ko" extension (modules)
you need to write a kernel installer cwm script, or use someone else script.
you can use my script: https://github.com/vadonka/kernel-installer
if you have some linux shell scripting knowledge you will understand this

[HOWTO] Building from sources [Kernel only for now]

Hello everyone.
This guide will help you in building a kernel from source for your Nexus 4
Later, when 4.2 hits AOSP, i'll add a guide for building that too
You will need a computer running Linux / OSX to build the kernel, natively, or via a VM.
This guide assumes you’re running any Linux distro.
Getting a toolchain:
You need a toolchain to build the kernel.
The preferred one is Google’s toolchain, the same they use to build AOSP.
In a terminal, type:
Code:
git clone [url]https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/[/url]
export PATH=$PATH:$(pwd)/arm-linux-androideabi-4.6/bin
export CROSS_COMPILE=arm-linux-androideabi-
TIp: paste the export statements in your ~/.bashrc to have them exported each login.
Getting the kernel source:
The kernel source for Nexus devices is available from Google’s servers.
Nexus 4 : https://android.googlesource.com/kernel/msm
Github Mirror: https://github.com/android/kernel_msm
Open the terminal, and type the below commands to get the kernel source on your computer.
Code:
mkdir -p android/kernel
cd android/kernel
For Nexus 4, we get the msm kernel sources.
Code:
git clone [url]https://android.googlesource.com/kernel/msm[/url]
Next, we change our directory to the newly fetched source.
Type
Code:
cd msm
Figuring out what to build:
Now, we need to figure out which revision to build.
You need to be exactly sure about this, otherwise there are chances that the compiled kernel won’t work.
The commit to build upon can be found by a few ways.
To get the kernel sources matching the device tree, type the below in the device tree.
Code:
git log kernel
Next, type the below in the kernel tree
Code:
git checkout <commit>
The commit of the version running of the current review units is 7a47627, which is same as branch android-msm-mako-3.4-jb-mr1-fr .
Compiling:
Name of defconfig: mako_defconfig
cd to the directory of the kernel source, then type the below in a terminal.
Code:
export ARCH=arm
export SUBARCH=arm
Code:
make <name_of_defconfig>
make
The kernel image will be ready at arch/arm/boot/zImage
To flash it, you need to make it into a boot.img, more on that later, when we have more sources.

1) what is the branch "android-msm-mako-3.4-jb-mr1-fr" for?
2) what does mr1 mean? sounds like milestone/alpha/beta. Maybe it's not final? Last commit is 2 weeks ago.
3) great guide

m11kkaa said:
1) what is the branch "android-msm-mako-3.4-jb-mr1-fr" for?
2) what does mr1 mean? sounds like milestone/alpha/beta. Maybe it's not final? Last commit is 2 weeks ago.
3) great guide
Click to expand...
Click to collapse
mr1 could stand for "Milestone Release 1", it might not be final.
That being said, you should never checkout a branch directly for compiling a kernel, but the commit directly.

cdesai said:
...You need a toolchain to build the kernel. The preferred one is Google’s toolchain, the same they use to build AOSP.
Click to expand...
Click to collapse
Could you also use linaro to compile the kernel? I believe it's a toolchain anyway, but I'm not too sure on it's benefits or compatibility...

nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage

randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
Are you planning on developing for the N4?
Loved your work on the DHD

espionage724 said:
Could you also use linaro to compile the kernel? I believe it's a toolchain anyway, but I'm not too sure on it's benefits or compatibility...
Click to expand...
Click to collapse
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
Nope, LZO compression is enabled by default

cdesai said:
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
Click to expand...
Click to collapse
Linaro has proven to increase android performance up 30 - 100% not sure if that is with -O3 optimizations or not. That is all I use on my kernels
Sucks this phone is not coming to Sprint, might be time to change carriers...
randomblame said:
nice didn't realize kernel source was already available- can't wait to test this zImage and start testing changes noticed they left out kernel compression makes for a big zimage
Click to expand...
Click to collapse
-mvectorize-with-neon-quad ---> I use this in my makefile for cflags and drops the zImage size from 5.0mb to 4.4mb.

cdesai said:
Linaro isn't a toolchain, but they do make toolchains.
Yes, you can use it to compile the kernel, though it may not compile at all with it, or not work well - your mileage may vary.
Nope, LZO compression is enabled by default
Click to expand...
Click to collapse
ah I didn't see it - 6+mb still pretty big from what I'm used to at least
I'm going through the mind numbing process of bringing in mainline patches and squashing them all together. I'm up to 3.4.1 ... woot where's the hang me emoticon lol
*finally got smart and cloned mainline and reset the head back to each sublevel and merged into my local n4 source
got it all the way up to date with mainline 3.4.18

Thanks cdesai. I didn't think anything was out yet!!

randomblame said:
ah I didn't see it - 6+mb still pretty big from what I'm used to at least
I'm going through the mind numbing process of bringing in mainline patches and squashing them all together. I'm up to 3.4.1 ... woot where's the hang me emoticon lol
*finally got smart and cloned mainline and reset the head back to each sublevel and merged into my local n4 source
got it all the way up to date with mainline 3.4.18
Click to expand...
Click to collapse
Yea, it's big, but partitions on new devices are big as well.
y u no use git to merge
Just add korg as a remote, fetch, merge.
Each version is tagged, so you can do that incrementally too.
Also, kernel.org hosts patches as well, if you prefer that way.
snowman77 said:
Thanks cdesai. I didn't think anything was out yet!!
Click to expand...
Click to collapse
Google <3

I got it straightened out so it's up to date with mainline and I think I've got overclocking up to 1.89ghz ready lots of more fun to be had but damn I'm just teasing myself till tuesday/whenever the thing comes in the mail. hard to test anything without hardware.

I may need a tip. I have followed your guide - which I find great and simple - but I'm having a problem with the arm binaries when I launch the make command after checking out the remotes/origin/android-msm-mako-3.4-jb-mr1-fr and executed make mako_defconfig:
Code:
/bin/sh: 1: arm-linux-androideabi-ld: not found
I have cloned the toolchain and msm repos, and added to the PATH environment var the location of the bin directory. I can reach arm-linux-androideabi-ld from the command line, but no luck executing it:
Code:
[email protected]:~/android/kernel/msm$ /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
And it is there with execution rights:
Code:
[email protected]:~/android/kernel/msm$ ll /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
-rwxrwxr-x 1 echedey echedey 3145332 Nov 10 16:32 /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld*
My repos are in these paths:
Code:
/home/echedey/android/arm-linux-androideabi-4.6
/home/echedey/android/kernel
And my $PATH is:
Code:
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/echedey/android/arm-linux-androideabi-4.6/bi
Am I missing anything?

josjator said:
I may need a tip. I have followed your guide - which I find great and simple - but I'm having a problem with the arm binaries when I launch the make command after checking out the remotes/origin/android-msm-mako-3.4-jb-mr1-fr and executed make mako_defconfig:
Code:
/bin/sh: 1: arm-linux-androideabi-ld: not found
I have cloned the toolchain and msm repos, and added to the PATH environment var the location of the bin directory. I can reach arm-linux-androideabi-ld from the command line, but no luck executing it:
Code:
[email protected]:~/android/kernel/msm$ /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
And it is there with execution rights:
Code:
[email protected]:~/android/kernel/msm$ ll /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld
-rwxrwxr-x 1 echedey echedey 3145332 Nov 10 16:32 /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld*
My repos are in these paths:
Code:
/home/echedey/android/arm-linux-androideabi-4.6
/home/echedey/android/kernel
And my $PATH is:
Code:
/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/home/echedey/android/arm-linux-androideabi-4.6/bi
Am I missing anything?
Click to expand...
Click to collapse
You path has a "n" missing from bin at the end.
You could type arm- and try to use tab-completion to see if it's accessible, then the same thing with full path (~/android/arm-linux-androideabi-4.6)

cdesai said:
You path has a "n" missing from bin at the end.
You could type arm- and try to use tab-completion to see if it's accessible, then the same thing with full path (~/android/arm-linux-androideabi-4.6)
Click to expand...
Click to collapse
Sorry, the missing 'n' came from the c&p. I can actually see the file by tabing it from any path but after the auto completing it tells this weird thing:
Code:
[email protected]:~$ arm-linux-androideabi-ld
bash: /home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld: No such file or directory
I'm a experienced *nix user but I don't get this. The repos are correctly cloned and all files under bin has exec rights. I'm running ubuntu 12.10. Maybe a problem with the shell? I should try any other environment, but that would be like killing flies with missiles. Thanks for your help.

Do you definitely have the appropriate executable at
'/home/echedey/android/arm-linux-androideabi-4.6/bin/arm-linux-androideabi-ld'?
Can you do an ls -lF of that directory?
Perhaps the arm-linux-androideabi-ld file there is actually just a symlink which has lost its target.

@josjator Yeah, seems I have the same problem as you. I'm also using Ubuntu 12.10 with a bash shell. I think it may be a recursive make/shell issue thing (sorry, I'm not too hot on make files). Will keep plugging away to see if I can resolve the problem.

The device trees have hit AOSP
https://android.googlesource.com/device/lge/mako/

dsana123 said:
@josjator Yeah, seems I have the same problem as you. I'm also using Ubuntu 12.10 with a bash shell. I think it may be a recursive make/shell issue thing (sorry, I'm not too hot on make files). Will keep plugging away to see if I can resolve the problem.
Click to expand...
Click to collapse
@josjator: Using the 4.7 toolchain sorted me out (at least it's building now and past the initial problem).
git clone https://android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.7
Click to expand...
Click to collapse
The objdump and ld binaries are much happier now.
BTW, I did download the 4.6 toolchain again (just in case there was some problem in the initial git clone), but I still encountered objdump and ld problems.

Works like a champ on Ubuntu 12.10 exactly as outlined in the OP. Thanks!
Code:
[email protected]:~/Documents/AOSP/kernel/msm$ ls -l arch/arm/boot/zImage
-rwxrwxr-x 1 android android 6314888 Nov 16 23:45 arch/arm/boot/zImage
[email protected]:~/Documents/AOSP/kernel/msm$ uname -a
Linux ubuntu 3.5.0-17-generic #28-Ubuntu SMP Tue Oct 9 19:31:23 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
[email protected]:~/Documents/AOSP/kernel/msm$ arm-linux-androideabi-gcc -v
[...]
gcc version 4.6.x-google 20120106 (prerelease) (GCC)

[Q]Problems of Building CM10.1 for Sony Xperia TX

Hello to all.
I am trying to learn building CM and modifying CM source code in order to running 3G and WiFi connections simultaneously on my Sony Xperia TX(LT29i).
I have been unlocked my TX and run CyanogenMod 12.1 Homebuildperfectly.
For building CM,i flash back to Xperia Firmware using FTF file
Code:
The following picture link is now my TX build:
i.imgur.com/APktTle.png
I follow wiki step by step:
Code:
wiki.cyanogenmod.org/w/Build_for_hayabusa
Ubuntu version :
Code:
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 14.04.2 LTS
Release: 14.04
Codename: trusty
I get stuck running breakfast command:
Code:
$ breakfast hayabusa
including vendor/cm/vendorsetup.sh
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/hayabusa/cm.mk]]: "vendor/sony/qcom-common/qcom-common-vendor.mk" does not exist. Stop.
Device hayabusa not found. Attempting to retrieve device repository from CyanogenMod Github (github.com/CyanogenMod).
Found repository: android_device_sony_hayabusa
Default revision: cm-10.1
Checking branch info
CyanogenMod/android_device_sony_hayabusa already exists
Syncing repository to retrieve project.
Fetching project CyanogenMod/android_device_sony_hayabusa
Repository synced!
Looking for dependencies
Done
build/core/product_config.mk:239: *** _nic.PRODUCTS.[[device/sony/hayabusa/cm.mk]]: "vendor/sony/qcom-common/qcom-common-vendor.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_hayabusa'
** Do you have the right repo manifest?
Then I follow Helpful Tip– Errors during breakfast,jumping down to the next section Extract proprietary blobs.
Unfortunately,it shows that "modem.b05" doesn't exist.
Code:
-emote object '/system/etc/fireware/modem.b05' does not exist
terminal screenshot's link : i.imgur.com/dX1rh0t.png
--
How can I solve problems?
Any piece of information ,I will be so thankful for your help.

You're missing the android_device_sony_qcom-common repo. Go to github.com/cyanogenmod/android_device_sony_qcom-common and download it manually. Make sure to select the right branch for building CM10.1
Then extract to yourcmsourcedirectory/device/sony/qcom-common and try to build again.

WhiteNeo said:
You're missing the android_device_sony_qcom-common repo. Go to github.com/cyanogenmod/android_device_sony_qcom-common and download it manually. Make sure to select the right branch for building CM10.1
Then extract to yourcmsourcedirectory/device/sony/qcom-common and try to build again.
Click to expand...
Click to collapse
The folder device/sony/qcom-common is already existed and downloaded.
Then I try download the zip file form github.com/cyanogenmod/android_device_sony_qcom-common and test to replace the original one.
Still get stuck running breakfast command, same message occur.
I notice the error message "vendor/sony/qcom-common/qcom-common-vendor.mk does not exist "
Code:
From github.com/cyanogenmod/android_device_sony_qcom-common/tree/cm-10.1 repo
doesn't contain qcom-common-vendor.mk
It is weird.

HandsomeRichard said:
The folder device/sony/qcom-common is already existed and downloaded.
Then I try download the zip file form github.com/cyanogenmod/android_device_sony_qcom-common and test to replace the original one.
Still get stuck running breakfast command, same message occur.
I notice the error message "vendor/sony/qcom-common/qcom-common-vendor.mk does not exist "
Code:
From github.com/cyanogenmod/android_device_sony_qcom-common/tree/cm-10.1 repo
doesn't contain qcom-common-vendor.mk
It is weird.
Click to expand...
Click to collapse
CM team introduced some heavy changes to qcom-common a few months ago, and my bet is that these are responsible for your error. Probably building latest CM12 would work better. Use the git repos by @updateing and you're good to go.

WhiteNeo said:
CM team introduced some heavy changes to qcom-common a few months ago, and my bet is that these are responsible for your error. Probably building latest CM12 would work better. Use the git repos by @updateing and you're good to go.
Click to expand...
Click to collapse
OK,I will try to build CM12 on my device.
Thanks for your friendly help.

AOSP Marshmallow issues

Hi all, can anyone say they've built a AOSP Marshmallow ROM (m-preview-2) ?
I can build Lollipop just fine but even doing a clean install of Linux and downloading 20+ gigs of AOSP repo stuff of m-preview-2, I get the following error...
make: *** No rule to make target `out/target/product/hammerhead/obj/STATIC_LIBRARIES/libunwind_llvm_intermediates/export_includes', needed by `out/target/product/hammerhead/obj/EXECUTABLES/init_intermediates/import_includes'. Stop.
Click to expand...
Click to collapse
If I download the 'master' repo, it compiles fine but I get a boot lock installing it on my Nexus5.
As I say, I can download and compile/install the AOSP Lollipop fine but Marshmallow just seems to not be all there. I understand it's a preview but it's now on it's (probable) last release before going live so I would have hoped it should be at least compilable.
Any help?
Many thanks
Adrian

Repo sync'ed it again and now get these errors....
external/selinux/checkpolicy/policy_define.c:1572:2: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&tclasses, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/policy_define.c:2763:3: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&rdp->dominates, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/policy_define.c:2769:3: warning: comparison of integers of different signs: 'int' and 'uint32_t' (aka 'unsigned int') [-Wsign-compare]
ebitmap_for_each_bit(&types, node, i) {
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
external/selinux/checkpolicy/../libsepol/include/sepol/policydb/ebitmap.h:76:39: note: expanded from macro 'ebitmap_for_each_bit'
for (bit = ebitmap_start(e, &n); bit < ebitmap_length(e); bit = ebitmap_next(&n, bit)) \
^ ~~~~~~~~~~~~~~~~~
3 warnings generated.
host C: checkpolicy <= external/selinux/checkpolicy/checkpolicy.c
host C++: checkpolicy <= out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.cpp
error: invalid argument '-std=gnu++14' not allowed with 'C/ObjC'
make: *** [out/host/linux-x86/obj/EXECUTABLES/checkpolicy_intermediates/policy_parse.o] Error 1
#### make failed to build some targets (01:33 (mm:ss)) ####
Click to expand...
Click to collapse
These seem to me to be pretty fundamental errors if I understand them correctly.
Many thanks
Adrian

same error
adrian.aitken said:
Hi all, can anyone say they've built a AOSP Marshmallow ROM (m-preview-2) ?
I can build Lollipop just fine but even doing a clean install of Linux and downloading 20+ gigs of AOSP repo stuff of m-preview-2, I get the following error...
If I download the 'master' repo, it compiles fine but I get a boot lock installing it on my Nexus5.
As I say, I can download and compile/install the AOSP Lollipop fine but Marshmallow just seems to not be all there. I understand it's a preview but it's now on it's (probable) last release before going live so I would have hoped it should be at least compilable.
Any help?
Many thanks
Adrian
Click to expand...
Click to collapse
i am getting the same error, how did you fix it? thanks

PiSpecialist said:
i am getting the same error, how did you fix it? thanks
Click to expand...
Click to collapse
I haven't - I went back to Lollipop. When Marshmallow comes out officially I'll look again.
Many thanks
Adrian

The marshmallow source code hasn't all been published yet

faZevoLv said:
The marshmallow source code hasn't all been published yet
Click to expand...
Click to collapse
preview-m-2 has and that's what I was talking about.
Many thanks
Adrian

Its bcuz the source isn't complete yet, they didn't release all the code needed to build it yet, which is why no ROMs are out, the only one that comes to mind is XtraSmooth, and I know he just uses the system image and odex's it, the actual AOSP source code isn't complete for marshmallow yet, it will be released on Oct 5th tho so be ready
Sent from my Nexus 6 using Tapatalk

CM11 Kenel compiling trouble !!

Hi. i have tried to compile cm11 kernel by using kernel source from http://github.com/cm-nokia-x2 and gcc toolchain 4.8 from here http://github.com/huyparody/gcc_linaro
i get config.gz from /proc/
and renamed it to ara_defconfig
and when i:
make ara_defconfig
make
after a few minute, it show me a error:
CC drivers/input/touchscreen/cyttsp4_device_access.o
drivers/input/touchscreen/cyttsp4_device_access.c: In function 'cyttsp4_grpdata_store_touch_params':
drivers/input/touchscreen/cyttsp4_device_access.c:1447:19: warning: 'rc3' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: cyttsp4_device_access.c:1447
make[3]: *** [drivers/input/touchscreen/cyttsp4_device_access.o] Error 1
make[2]: *** [drivers/input/touchscreen] Error 2
make[1]: *** [drivers/input] Error 2
make: *** [drivers] Error 2
[email protected]:~/android/kernel/nokia/msm8610$
Click to expand...
Click to collapse
how to solve it!! thanks much

kaotd99 said:
how to solve it!! thanks much
Click to expand...
Click to collapse
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.

zombah said:
Hello,
Use toolchain from CyanogenMod prebuilt repo, here is link: github.com/CyanogenMod/android_prebuilt/tree/cm-11.0/linux-x86/toolchain/arm-eabi-4.4.3
You also don't need to copy config from /proc, it is included in source at arch/arm/configs/msm8610-nokia-defconfig.
Click to expand...
Click to collapse
thanks dev

oh god... i got new error:
i type:
export PATH=/home/kaotd/android/prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin:$PATH
export ARCH=arm
export CROSS_COMPILE=arm-eabi-
and:
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make msm8610-nokia_defconfig
#
# configuration written to .config
#
[email protected]:/home/kaotd/android/kernel/nokia/msm8610# make
scripts/kconfig/conf --silentoldconfig Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
kernel/bounds.c:1: error: bad value (cortex-a7) for -mtune= switch
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
[email protected]:/home/kaotd/android/kernel/nokia/msm8610#
Click to expand...
Click to collapse
can you help me ? thanks.... because im a newbie and sorry about that

kaotd99 said:
can you help me ? thanks.... because im a newbie and sorry about that
Click to expand...
Click to collapse
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7

zombah said:
Hello,
Ahh yep, i forgot switch to memcpy optimizations, here is correct link to newer toolchain android.googlesource.com/platform/prebuilts/gcc/linux-x86/arm/arm-eabi-4.7
Click to expand...
Click to collapse
thanks.. i will try and report to you later!! thanks again

@zombah hi again. i was compiled a kernel( zImage )
now i have "Kernel: arch/arm/boot/zImage is ready"
so how can i compare it with boot.img ?

Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.

zombah said:
Hello,
If you wont use inline kernel building inside CyanogenMod, you probably need to unpack boot.img content replace kernel and then pack boot.img again with replaced kernel. Remember that it is dangerous if your kernel is not bootable, you'll stuck to recovery only boot and if your recovery also lost only unbricking will help.
Use CyanogenMod mkbootimg.c/unpackbootimg.c for that, here is repo github.com/CyanogenMod/android_system_core/tree/cm-11.0/mkbootimg
Here is how to compile them separatly of whole system:
Code:
gcc -o mkbootimg mkbootimg.c ../libmincrypt/sha.c -I../include
gcc -o unpackbootimg unpackbootimg.c ../libmincrypt/sha.c -I../include
you'll need to download dependencies also.
Click to expand...
Click to collapse
thanks much

can you tell me which file contain OverClock number of nokia x2 ? and which kernelPatch i can apply with this kernel ?

Hello,
I don't know, i'm not interested in overclocking and never investigated this question.
And i don't recommend you to play with overclocking without deep embedded development skills, it is very easy to kill your device with wrong power modifiers.

i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !

kaotd99 said:
i'm understand, thanks for your suggestion.
not about nokia x2ds but can i ask you a question?
-can i make a kernel source for a mtk device ? because i have a mtk china phone which not have kernel source from manufacturer !
Click to expand...
Click to collapse
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?

zombah said:
Hello,
Sure it is possible, why not. But you need at least serial/uart console on device, otherwise how you will debug kernel boot problems?
Click to expand...
Click to collapse
thanks... now i'm trying to port double-tap to wake feature from Nokia Stock Kernel. There is any suggestion ?? Thanks

i'm trying to add this: https://github.com/ryanaepple/android_kernel_motoe/commit/080003bc8e61349bf7c8da00fa6923f3c84d1927
and being stuck at editing synaptics_dsx_i2c.c and synaptics_dsx_i2c.h
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h

kaotd99 said:
can you tell me which files is Touchscreen driver of nokia x2 ?? i think it is synaptics_i2c_rmi4.c/.h
Click to expand...
Click to collapse
Hello,
Nokia X2 have Cypress TMA4XX touchscreen, driver location is drivers/input/touchscreen/cyttsp4*