yashsingh1/xdaforums huggingface dataset:
[Android] mcarrion78:
build/core/tasks/kernel.mk:40: ***************************************************************

build/core/tasks/kernel.mk:41: * Using prebuilt kernel binary instead of source *

build/core/tasks/kernel.mk:42: * THIS IS DEPRECATED, AND WILL BE DISCONTINUED *

build/core/tasks/kernel.mk:43: * Please configure your device to download the kernel *

build/core/tasks/kernel.mk:44: * source repository to kernel/samsung/toro

build/core/tasks/kernel.mk:45: * See http://wiki.cyanogenmod.com/wiki/Integrated_kernel_building

build/core/tasks/kernel.mk:46: * for more information *

build/core/tasks/kernel.mk:47: ***************************************************************

make: *** No rule to make target `out/host/linux-x86/bin/mkbootimg', needed by `out/target/product/toro/boot.img'. Stop.

Im getting this error and have no idea why. I had been compiling fine until today. Any suggestions???
[Android] mg2195:
Assuming he's building aosp just adding in kernel source will not work since aosp doesn't support online kernel building

I GI semi successful a few pages back...basically added a file, and edited another one
[Android] incarnation95:
if i am to compile for samsung galaxy s2 where could i find the device tree?

i read the forum but i am confused a bit! could somebody direct me to the device tree :)

thanks
[Android] dastin1015:
There are many variants of the Galaxy S2. Which version do you have?
[Android] incarnation95:
i9100G
[Android] dastin1015:
https://github.com/CyanogenMod/android_device_samsung_i9100g
[Android] kevin130:
Not sure why but when i did repo sync and tried to compile i started getting this error. I used your tree dastin.

Install: /home/kevin/CYANOGENMOD/out/target/product/shooter/system/bin/netcfg

target SharedLib: libsurfaceflinger (out/target/product/shooter/obj/SHARED_LIBRARIES/libsurfaceflinger_intermediates/LINKED/libsurfaceflinger.so)

target Executable: wpa_supplicant (out/target/product/shooter/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant)

Install: /home/kevin/CYANOGENMOD/out/target/product/shooter/system/etc/security/cacerts/1df5ec47.0

/home/kevin/CYANOGENMOD/prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.6/bin/../lib/gcc/arm-linux-androideabi/4.6.x-google/../../../../arm-linux-androideabi/bin/ld: out/target/product/shooter/obj/EXECUTABLES/wpa_supplicant_intermediates/src/drivers/drivers.o: in function wpa_drivers:drivers.c(.data.rel.wpa_drivers+0x0): error: undefined reference to 'wpa_driver_wext_ops'

collect2: ld returned 1 exit status

make: *** [out/target/product/shooter/obj/EXECUTABLES/wpa_supplicant_intermediates/LINKED/wpa_supplicant] Error 1

make: *** Waiting for unfinished jobs....
[Android] incarnation95:
And do i have to fork it or what?
[Android] mg2195:
Just a guess...but try doing a "make clean" before building...that will clear out the old stuff for the new...or maybe "make clobber" that will completely wipe your out directory
[Android] onlychevys:
I've been building CM10 from source for a while now, but for the last week I keep getting this same error and can't figure out what to do to fix it.

Here is copy of terminal:

/home/mark/cm10/kernel/samsung/msm8660-common/arch/arm/boot/compressed/piggy.lzo.S:4: Error: file not found: arch/arm/boot/compressed/piggy.lzo

make[4]: *** [arch/arm/boot/compressed/piggy.lzo.o] Error 1

make[3]: *** [arch/arm/boot/compressed/vmlinux] Error 2

make[2]: *** [zImage] Error 2

make[1]: *** [sub-make] Error 2

make[1]: Leaving directory `/home/mark/cm10/kernel/samsung/msm8660-common'

make: *** [TARGET_KERNEL_BINARIES] Error 2

make: *** Waiting for unfinished jobs....

The file piggy.lzo.s is there? I have made clean, clobber and even deleted all folders in cm10 folder except for .repo and resinced etc.I have searched everywhere and tried to fix this my self, so any help would be great!!!!!!
[Android] dastin1015:
Something is probably wrong in the kernel repo

私のEVO 3Dから送信される。
[Android] dastin1015:
My tree is a mess right now trying to get it inline with CM without hacks so I can push commits to CM

私のEVO 3Dから送信される。
[Android] jd3107:
keep getting errors

I keep getting errors when compiling.

build/core/product_config.mk:62: *** Unknown sed version. Stop.
[Android] kevin130:
Alright. Ill try later.
[Android] DragunKorr:
hey guys its been awhile since i compiled aokp and i cant remember the fix for this error any help would surely be appreciated!
[Android] dastin1015:
Bottom of OP. change line to point to frameworks/native
[Android] DragunKorr:
Thanks bro been awhile since I had that error forgot the fix:D
[Android] kevin130:
would it make differnce if i chose htc_shooter-debug or cm_shooter-debug ? Both of these options are available when i do lunch.
[Android] dastin1015:
On my tree cm is recommended. 4G currently broken in the kernel of my tree. WIP being fixed right now
[Android] kevin130:
whats teh diference between them?
[Android] dastin1015:
CM will properly call all the needed settings.
[Android] kevin130:
But will it compile? or will i receive error?
[Android] dastin1015:
It should. I have a ton of uncommitted changes in on my local machine so can't test until I sanitize.
[Android] kevin130:
Alright. Iim compiling now. Ill let you know if it successfully compiles. It took 4 hours to compile yestarday so this is gonna be a long wait.
[Android] mg2195:
I know your pain...working on an old dual core CPU
[Android] b.huss2:
Finally got something looking like its gonna build! Turns out I needed ie32-libs package. Apearantly the SDK is built for 32bit? We'll see what I end up with when it's done.
[Android] kevin130:
Successfully compiled.
[Android] dastin1015:
Awesome :) Just so you know 4G is broken in the kernel and is being worked on.
[Android] kevin130:
Alright. 4G doesn't really make a difference to me since I use the VM network.
[Android] dany547:
device/samsung/msm7x27-common/libcamera/QualcommCameraHardware.h:34:24: fatal error: ui/Overlay.h: No such file or directory
compilation terminated.
make: *** [out/target/product/tass/obj/SHARED_LIBRARIES/libcamera_intermediates/QualcommCameraHardware.o] Error 1
make: *** Waiting for unfinished jobs....

the problem is that i cannot find a gitgub from where i can clone that specific file...
[Android] napster113:
could someone help me with this please I'm a comptete idiot it would seem with linux but I am trying;-

You're building on Linux

Lunch menu... pick a combo:

1. full-eng

2. full_x86-eng

3. vbox_x86-eng

4. full_grouper-userdebug

5. mini_armv7a_neon-userdebug

6. mini_armv7a-userdebug

7. full_wingray-userdebug

8. full_crespo-userdebug

9. full_maguro-userdebug

10. full_panda-userdebug

Which would you like? [full-eng] 4

build/core/product_config.mk:195: *** device/asus/grouper/full_grouper.mk: PRODUCT_NAME must be unique; "full_grouper" already used by device/asus/android_device_asus_grouper/full_grouper.mk device/asus/grouper/full_grouper.mk device/grouper/full_grouper.mk . Stop.

** Don't have a product spec for: 'full_grouper'

** Do you have the right repo manifest?

craig@craig-Inspiron-1545:~/WORKING_DIRECTORY$

thankyou

Edit ;- I think I got It
[Android] napster113:
Can someone tell me what to do with this please : -
[Android] dany547:
it finished the building process ? :) before you run otapackage?
[Android] napster113:
Sorry to be a pain, but could you tell me then what i need to do.:)
[Android] dany547:
first you must lunch the build for the device, after it finished run otapackage
[Android] mg2195:
How to compile or how to fix that .txt you posted?

For the compile error...just as it says, there is already a file calling for grouper...navigate to the one (location provided in error) you did not sync and delete it

For the .txt, that should not be here...looks like an app error...like is file explorer isn't opening...has nothing to do with compiling aosp
[Android] napster113:
I type in lunch and I get this:-

You're building on Linux

Lunch menu... pick a combo:

1. full-eng

2. full_x86-eng

3. vbox_x86-eng

4. full_grouper-userdebug

5. mini_armv7a_neon-userdebug

6. mini_armv7a-userdebug

7. full_wingray-userdebug

8. full_crespo-userdebug

9. full_maguro-userdebug

10. full_panda-userdebug

Which would you like? [full-eng] 4

as you can see I pick option 4 and then this comes up:-

============================================

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.1.1

TARGET_PRODUCT=full_grouper

TARGET_BUILD_VARIANT=userdebug

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a-neon

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.2.0-30-generic-x86_64-with-Ubuntu-12.04-precise

HOST_BUILD_TYPE=release

BUILD_ID=JRO03L

OUT_DIR=out

============================================

craig@craig-Inspiron-1545:~/WORKING_DIRECTORY$

So then I type make -j# otapackage and i get this :-

craig@craig-Inspiron-1545:~/WORKING_DIRECTORY$ make -j# otapackage

make: the `-j' option requires a positive integral argument

Usage: make [options] [target] ...

Options:

-b, -m Ignored for compatibility.

-B, --always-make Unconditionally make all targets.

-C DIRECTORY, --directory=DIRECTORY

Change to DIRECTORY before doing anything.

-d Print lots of debugging information.

--debug[=FLAGS] Print various types of debugging information.

-e, --environment-overrides

Environment variables override makefiles.

--eval=STRING Evaluate STRING as a makefile statement.

-f FILE, --file=FILE, --makefile=FILE

Read FILE as a makefile.

-h, --help Print this message and exit.

-i, --ignore-errors Ignore errors from recipes.

-I DIRECTORY, --include-dir=DIRECTORY

Search DIRECTORY for included makefiles.

-j [N], --jobs[=N] Allow N jobs at once; infinite jobs with no arg.

-k, --keep-going Keep going when some targets can't be made.

-l [N], --load-average[=N], --max-load[=N]

Don't start multiple jobs unless load is below N.

-L, --check-symlink-times Use the latest mtime between symlinks and target.

-n, --just-print, --dry-run, --recon

Don't actually run any recipe; just print them.

-o FILE, --old-file=FILE, --assume-old=FILE

Consider FILE to be very old and don't remake it.

-p, --print-data-base Print make's internal database.

-q, --question Run no recipe; exit status says if up to date.

-r, --no-builtin-rules Disable the built-in implicit rules.

-R, --no-builtin-variables Disable the built-in variable settings.

-s, --silent, --quiet Don't echo recipes.

-S, --no-keep-going, --stop

Turns off -k.

-t, --touch Touch targets instead of remaking them.

-v, --version Print the version number of make and exit.

-w, --print-directory Print the current directory.

--no-print-directory Turn off -w, even if it was turned on implicitly.

-W FILE, --what-if=FILE, --new-file=FILE, --assume-new=FILE

Consider FILE to be infinitely new.

--warn-undefined-variables Warn when an undefined variable is referenced.

This program built for x86_64-unknown-linux-gnu

Report bugs to <bug-make@gnu.org>

craig@craig-Inspiron-1545:~/WORKING_DIRECTORY$
[Android] Gecko225:
Make -j# otapackage :

"#" is a value (eg:4, 1 or 16) it is the number of active threads when you are compiling. so "make -j# otapackage" could be "make -j16 otapackage"
[Android] napster113:
Thanks thats what I was missing lol, replacing # with the number of connections lol.:)

I had the java error but sorted that, its building now.
[Android] Gecko225:
Welcome !!!
[Android] napster113:
Dont go to far lol.:D:D

Edit:- Told you, got errors right at the bottom:-
[Android] blazingwolf:
A good thing to try is copy and paste the error in to google or in a search of this thread. It can lead to wondrous stuff. ;)

http://xdaforums.com/showpost.php?p=28567186&postcount=39
[Android] napster113:
Thank you patch applied, building. :fingers-crossed:
[Android] cpwshf:
Samsung Galaxy S3

Hello,

Currently I have been trying to compile using this guide for my Samsung Galaxy S3 and my build stops with this message:

make: *** No rule to make target `out/target/product/d2vzw/kernel', needed by `out/target/product/d2vzw/boot.img'. Stop.

From what I understand from reading through this thread, I need to get a prebuilt kernel? I assume that since I am building for JB, I also need to make sure I have a JB kernel for my phone? I am just not sure which kernel I should get, and where should I be placing it?

I'd really appreciate any help.

Thanks
[Android] dany547:
hmm, i got i similar error, and i had to clone the JB kernel for my device, and put it in the system folder.
[Android] cpwshf:
Thank you for the info. The problem is I am not good at working with kernels, well not yet anyways. I think I found the right git for the source JB kernel I need (android_kernel_samsung_d2), however this one says "Galaxy S III kernel with kexec functionality." Since the bootloader for the S3 was already un-locked, I think I need to find a kernel without kexec, unless I am mistaken.
[Android] triptosyll:
So then u had system/kernel? I'm cloning a kernel repo, and need to know where to clone it to so that its built with the ROM..

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] seby_guritza:
Nice tutorial! thanks a lot!:good:
[Android] mg2195:
alright...so ive discovered the problem with my imei on aosp was due to the fact that it was missing samsung ril files in frameworks/base/telephony

in the process of adding in the neccessary files (took a few hours to locate them all and add them in and edit existing files) i am now getting this error

trouble writing output: Too many methods: 65738; max is 65536. By package:

full error output here: http://pastebin.com/iDYQQ6iM

anyways...its obvious by the error that there is too many files for whatever its trying to create...and it lists the number of stuff for each thing included...so i guess my question is, whats safe to remove? or should i do something else? or even better is there a way to increase the max methods?
[Android] dastin1015:
https://github.com/CyanogenMod/andr...mmit/854f6f736b90d33b59b5a85bcecf72a416c43b7d

Be sure to add framework2.jar to your BOOTCLASSPATH in your init.{yourDevice}.rc after your framework.jar line.
[Android] Roladriz:
Dastin, you are kind of like a mobile version of stackoverflow for ROM building. You are a resource full of information man. Thanks again.
[Android] dastin1015:
Haha that's quite a compliment. You're welcome.
[Android] DragunKorr:
need help getting past this

never had this error before!

and i'm about 98% into my build!:(
[Android] bieltv3:
KERNEL

Excuseme for the question, but I can't found the answer, if I wnat to add a custom kernel that is on github, but I don't create this kernel. How can I add to the sources of the rom? Where I have to place it, or get it and How?

btw, exellent tutorial :)
[Android] Roladriz:
Create a file and name it local_manifest.XML. Add the name, directory, and branch of whatever you want to build for. Navigate to the root of your source tree, show hidden files, (ctrl +h) and drop the XML in the folder named .repo and re-sync. Here is an example for building cm on pyramid. https://github.com/RoLa/local_manifest/blob/master/local_manifest.xml
[Android] Toisan:
build/core/product_config.mk:205: *** No matches for product "htc_bravo". Schluss.

** Don't have a product spec for: 'htc_bravo'
** Do you have the right repo manifest?

Dudes, Im so sorry, but i still dont got it ... -.-

anyone can explain it realy noob proof? maybe in which directorys the files are.. dunno... :'(

this is my vendorsetup in my /device/htc/bravo folder:

#
# Copyright (C) 2008 The Android Open Source Project
#
# Licensed under the Apache License, Version 2.0 (the "License");
# you may not use this file except in compliance with the License.
# You may obtain a copy of the License at
#
# http://www.apache.org/licenses/LICENSE-2.0
#
# Unless required by applicable law or agreed to in writing, software
# distributed under the License is distributed on an "AS IS" BASIS,
# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
# See the License for the specific language governing permissions and
# limitations under the License.
#

# This file is executed by build/envsetup.sh, and can use anything
# defined in envsetup.sh.
#
# In particular, you can add lunch options with the add_lunch_combo
# function: add_lunch_combo generic-eng

add_lunch_combo htc_bravo-eng
add_lunch_combo htc_bravo-userdebug

and if i look at the file is see in the error (build/core/product_config.mk:205) line 205 say's:

INTERNAL_PRODUCT := $(call resolve-short-product-name, $(TARGET_PRODUCT))

Btw, sorry for getting on ur nerves... :(
[Android] triptosyll:
Hey roladriz, thanks for that! I'm also wondering, what if I already have the source for the kernel I want built inline with my ROM? Its all in one folder on my desktop. Where would I put that folder so that its built with the ROM?

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] Roladriz:
No problem. It'll go in kernel/{manufacturer}/{device}. If you look at the path in the manifest I'm using, you'll see the example. Just make sure the prebuilt is commented out in your mk file and the path to the inline is added.
[Android] triptosyll:
OK. Everything is in the right place. Everything is set to build the kernel inline with ROM. But I get this error:

make: *** No rule to make target 'out/target/product/fascinatemtd/kernel', needed by 'out/target/product/fascinatemtd/boot.img'. Stop.

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] mg2195:
Don't worry about build/core/product_config

Your vendor setup (add lunch combos) are not matching the device names in your device .mk files located in your device tree which is in working/device/pathto/device
[Android] Toisan:
And this is my "bravo.mk" is this the correct?

Pastebin Link for bravo.mk -> because i dont see what i have to change...

Thanks :)
[Android] triptosyll:
Hey guys, I have my kernel set up to build with the ROM, and I get this error:

make: *** No rule to make target 'out/target/product/fascinatemtd/kernel', needed by 'out/target/product/fascinatemtd/boot.img'. Stop.

Any ideas?

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] mg2195:
AOSP does not support inline kernel building...you need prebuilts
[Android] triptosyll:
I'm pretty sure mine is gonna b all cm. Its a cm device tree, and a cm kernel tree, with cm common files for the device. U CAN compile it all together, u just gotta have the files all pointing to the right places. Cm IS set up to build the kernel inline, and it LOOKS like they're all pointing to the right places, but still that error. Same error if I try and build JUST the kernel.

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] mg2195:
But kernel building is performed by working/build...trust me

Look in a cm working directory working/build/core/tasks then compare that to an aosp working/build/core/task...notice any difference?

The cm10 has a file called kernel.mk aosp does not have that file...there also some other files...I posted here quite a fe pages back (about a week ago) on how i almost added inline kernel building

Cm isn't made by kernel and device trees...its made by everyhing else..it use a differnt source...a different repo init...it doesn't matter what device tree or kernel or vendor trees your using...if you repo init aosp your gonna get aosp device repos don't determine the build
[Android] triptosyll:
I'm not gna argue with u, cuz I'm only going by what I've been told:

http://xdaforums.com/showthread.php?t=1871819

If u read that whole thing, ull get the gist of what I've been fighting through. The last post is what I'm trying to do now. Let me know if u think its a waste of time, or if it sounds like its possible.

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] mg2195:
Looking at the last page that's what I'm talking about...your missing stuff from the build directory

And like I said I almost got it going...but just kinda stopped...got busy with other stuff...I had it so it would almost compile everything except a few files...don't remwmber what they were but once I added them to my out directory it would compile the kernel and boot.IMG

So yes its possible, I did what I did with out looking at cms commits...I just personally compared the two working folders of cm and aosp...so just look at all the commits regarding kernels and add them in

Adding the patches is as simple as opening the file in your working directory and adding in everything green and removing everything red...don't add the "+" signs though...that just let's you know they added it in
[Android] triptosyll:
Awesome! I'll get to work! Keep an eye out for my success or failure!

And since I'm attempting something that u've also attempted, do u mind if I pm u if I'm completely stumped?

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] mg2195:
If you want...again I never got it fully going, but feel free to pm I'll help where I can
[Android] cpwshf:
@mg2195 @triptosyll

Hi!

I've been basically trying to do basically the same thing that you have both been talking about, except I am trying to do this with a vzw Galaxy S3, and so far it's been very "educational". Before this I have been making my own custom roms for the vzw Galaxy Nexus and have fun doing it. Little hitch with the Galaxy S3 though, from what I have read on other forums so far is that there is no official JB kernel source released for it. Just to see the difference between AOSP and AOKP builds I can tell you after downloading the kernel source AOKP builds perfectly, but as triptosyll has run into, I cannot get AOSP to compile (aka no support for inline kernel building).

If I want to go with AOSP on the S3, than am I basically SOL for the time being, or is there another approach I should be reading into?

Thanks
[Android] dastin1015:
Unpack the boot.img from AOKP, CM, etc. Place that zImage wherever your prebuilt kernel needs to be. Extract the modules from system/lib/modules and make sure to use PRODUCT_COPY_FILES to copy the modules over.
[Android] Roladriz:
Sorry guys ..I got caught up at work. Hope everything goes good and you are able to get it working.
[Android] cpwshf:
dastin you are awesome!!

I had to make a few other changes, and it compiled and completed. Course in all the searching and re-building, I forgot one little detail, I never ran the extract-files.sh scripts in the d2vzw directory... I'm going to guess that I don't have any proprietary drivers at this point.

I guess I could load a cm build onto my S3, and then run that script and then compile again...

Thanks again!
[Android] triptosyll:
Just wanted u guys to know, I almost have inline kernel building working with aosp. I'll get back here when I have it working.

________________________________

Bacon in my coffee, please? You don't have bacon?! Unacceptable!!
[Android] cpwshf:
I have all the proprietary files extracted and was able to build. Flashed my phone, rebooted and now my phone just shows the "samsung" name really quick, vibrates and then reboots, have to go back and figure out what I messed up...
[Android] gangstaboy13:
Where to put the prebuilt kernel? And does it needs to be a boot.img or flashable zip
[Android] cpwshf:
Still having the same problem, I can build, however when I flash it to the phone it get's stuck in a bootloop. I did find that samsung has posted kernel source, however they state that it's for ICS. I have no way to logcat or get any kind of logs from the phone while it's bootlooping.

Is there something else I can try?
[Android] cpwshf:
So far the only thing I can find is that the rom I built has a recovery folder, how do I get rid of that or can I??
[Android] dastin1015:
Run it through dsixda's kitchen to remove it and resign.