yashsingh1/xdaforums huggingface dataset:
[Android] yosterwp:
Alright, so I guess I need help now too. After building for 40 minutes on my 'monster' machine (a typical laptop), I run across these errors that I have absolutely no idea how to combat.

Does anyone have any idea?

/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function close_lights:device/samsung/d2-common/liblights/lights.c:145: error: undefined reference to 'LOGV'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function write_rgb:device/samsung/d2-common/liblights/lights.c:84: error: undefined reference to 'LOGV'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function write_rgb:device/samsung/d2-common/liblights/lights.c:95: error: undefined reference to 'LOGE'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function set_light_leds:device/samsung/d2-common/liblights/lights.c:156: error: undefined reference to 'LOGV'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function set_light_leds:device/samsung/d2-common/liblights/lights.c:167: error: undefined reference to 'LOGV'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function set_light_leds:device/samsung/d2-common/liblights/lights.c:174: error: undefined reference to 'LOGE'
/home/yosterwp/eos/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/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/lights.o: in function write_int:device/samsung/d2-common/liblights/lights.c:67: error: undefined reference to 'LOGE'
collect2: ld returned 1 exit status
make: *** [out/target/product/d2vzw/obj/SHARED_LIBRARIES/lights.msm8960_intermediates/LINKED/lights.msm8960.so] Error 1
make: *** Waiting for unfinished jobs....
Install: out/target/product/d2vzw/system/lib/libclcore.bc

There was way more output than this, I just posted the errors that stopped the building process.

Thanks!

BTW: My working directory is /home/yosterwp/eos
[Android] dastin1015:
Change any reference of LOGx (x being any letter) to LOGx in the files the error is outputting.
[Android] oo3:
So I was getting the Java version error, which I fixed, but now I am receiving the following error:

============================================
PLATFORM_VERSION_CODENAME=REL
PLATFORM_VERSION=4.0.1
TARGET_PRODUCT=full
TARGET_BUILD_VARIANT=eng
TARGET_BUILD_TYPE=release
TARGET_BUILD_APPS=
TARGET_ARCH=arm
TARGET_ARCH_VARIANT=armv7-a
HOST_ARCH=x86
HOST_OS=linux
HOST_BUILD_TYPE=release
BUILD_ID=ITL41D
============================================
build/core/base_rules.mk:166: *** frameworks/native/cmds/dumpstate: MODULE.TARGET.EXECUTABLES.dumpstate already defined by frameworks/base/cmds/dumpstate. Stop.

Any ideas?
[Android] fabzbear:
Um unless I did something wrong and I know I didn't I created an stock source build of ics
[Android] CallMeVentus:
I said no for ICS , not never .

Never is for JB

"Friends forever." - Ventus
[Android] yosterwp:
Sorry, I think I am misunderstanding you here.. When I open up /device/samsung/d2-common/liblights/lights.c , I am not sure what to change..

Like

Line 156 has 'LOGV' and in the error, 'LOGV' is written..

So do I actually change the instances with LOG(a) a being some letter, with LOGx?

Thanks, and while I didn't really use your guide (I followed the one on the rom I am using's site), I really appreciate your dedication and commitment to helping us on your thread like this.
[Android] blazingwolf:
Change LOGV to read ALOGV. LOGE should be ALOGE, etc.
[Android] CallMeVentus:
You didn't sync everything didn't you ?

"Friends forever." - Ventus
[Android] possessed1913:
i followed the steps on page 1 to a t. when i did the repo sync it took a few hours and about 10'ish GB's. should i just dump the repo and do it again?
[Android] dastin1015:
Why are you going to dump it? That would mean another few hours of downloading.
[Android] possessed1913:
believe me, i don't want to dump everything either. just cant figure out why i'm getting those files not found!
[Android] dastin1015:
Do a repo sync again.

私のEVO 3Dから送信される。
[Android] yosterwp:
Thank you very much! I will try that shortly!
[Android] jacobmacek:
Can somebody give me a hand?

i get this error when compiling, i have tried several fixes to get rid of other errors but with the other errors out of the way, i still get this one!

build/core/base_rules.mk:171: *** device/inc/liblights: MODULE.TARGET.SHARED_LIBRARIES.lights.inc already defined by device/htc/inc/liblights. Stop.

thank you in advance for any help
[Android] yosterwp:
Have you tried updating your device tree?
[Android] mg2195:
any one care to help?

make: *** No rule to make target `vendor/samsung/infuse4g/proprietary/libGLES_android.so', needed by `out/target/product/infuse4g/system/lib/egl/libGLES_android.so'. Stop.

thanks in advance

think i got past that error...but just realized i never did this

and am getting errors with frameworks/base

how do i change all the refernces...like which file is it located in that i make the change...im looking in my working/device/samsung/infuse4g/ but not sure which file it is...

think i fixed it...gonna compile to see...just renamed the base folder to native
[Android] jacobmacek:
i dont think so?

i already did a git clone for my inc and common folder but i dont think i have updated it, how do i do that?
[Android] whiskerz:
Question

First off I would like to say, Thank you for this wonderful guide! I have compiled a JB rom for the Gnex with no errors, except when you go to flash and boot up for the first time. I get the google logo, followed by a black screen. I saw a response when searching through the thread that stated, this had something to do with the ramdisk. Being a complete beginner I have no idea how to edit the ramdisk in a way so I can get the rom to boot up. If someone could please assist me and tell me the exact files I need to edit to make this work, I would be very gratetful.
[Android] yosterwp:
I finally got the rom to build, thanks a bunch to dustin!

However, when I flash my AOSP rom on my d2vzw, I get:

set_perm: some changes fail

E: Error <path to the rom>

(Status 7)

while flashing in recovery. I have tried multiple recoveries with no luck.

Is there a way to have clockworkmod elaborate on what status 7 means, or what the error is?
[Android] blazingwolf:
In your device tree you should find the device make file that will have lines that begin with frameworks/base. Just change the lines to frameworks/native.
[Android] CosmoDroid:
Remove include $(BUILD_SHARED_LIBRARY) from the device/htc/inc/liblights/android.mk file. This should solve your error. :)

Do go through the pages of this thread. You'll get most of the errors sorted out.

Press thanks if helped.
[Android] mg2195:
not quite positive what the device make file is...but i think its "infuse4g.mk" i looked at that and all the frameworks were alredy frameworks/native...
[Android] blazingwolf:
Have you looked at any of the other make files to make sure you got all of the lines?
[Android] jacobmacek:
silly me

i made a noob mistake :p, it looks like i have been making the wrong lunch menu item, i was selecting full_inc userdebug instead of full-eng

i used th correct lunch menu selection and i noticed something, after entering in "make otapackage" this list popped up

*****************************************************

PLATFORM_VERSION_CODENAME=REL

PLATFORM_VERSION=4.1.1

TARGET_PRODUCT=full

TARGET_BUILD_VARIANT=eng

TARGET_BUILD_TYPE=release

TARGET_BUILD_APPS=

TARGET_ARCH=arm

TARGET_ARCH_VARIANT=armv7-a

HOST_ARCH=x86

HOST_OS=linux

HOST_OS_EXTRA=Linux-3.0.0-12-generic-x86_64-with-Ubuntu-11.10-oneiric

HOST_BUILD_TYPE=release

BUILD_ID=JRO03H

OUT_DIR=out

***************************************************************

what I noticed is that every line has something listed after the = except for TARGET_BUILD_APPS=:rolleyes:

in result, when i enter make otapackage in to compile a flashable zip, the first 2 error lines i get are

/bin/bash: xsltproc: command not found

/bin/bash: xsltproc: command not found

then a bunch of lines ignoring .oggs (the ringtones)

and finally it says

make: *** No rule to make target `otapackage'. Stop

I searched the thread for all of the above errors and didnt find anything :confused: , to me, what appears to be happening is the computer doesnt have the apps needed to fully compile the rom, it starts to attempt to compile by moving the ogg's then stops because it doesnt have what it needs
[Android] CallMeVentus:
Run on another terminal

sudo apt-get install xsltproc

"Friends forever." - Ventus
[Android] mg2195:
checked all the mk files...anything that refrences frameworks was already frameworks/native

i am currently getting this: http://pastebin.com/9jUXEHVh
[Android] jacobmacek:
***********************

i ran the command and it got rid of the "/bin/bash: xsltproc: command not found" error, but now when i try to compile, i get, "find: `src': No such file or directory", then the same nonsense about the ringtones and then the same final error, make: *** No rule to make target `otapackage'. Stop.

please and thank you for the help, if you can help me get my rom to compile, ill donate a few bucks to you and dastin1015!

EDIT: and theres still a blank space after TARGET_BUILD_APPS=
[Android] CallMeVentus:
full-eng builds don't have an otapackage

"Friends forever." - Ventus
[Android] dastin1015:
You have overlays in your device repo that AOSP doesn't support. Easiest thing to do is just delete the overlay folder in your device repo.

Ignore the blank space after TARGET_BUILD_APPS= because you're building an entire ROM, not just apps. Also you can ignore the not finding src and the copy ignore stuff. That's just usual output clutter.

You're getting the "No rule to make target `otapackage'" error because you're trying to build a generic build, not one for your device, and the generic build isn't a device so an otapackage can't be created.
[Android] Thatgrass:
Repo synch takes more than 1 day in virtual box, for all virtual box users: just dual boot with current OS, because otherwise you have to wait forever ;)
[Android] CdTDroiD:
LOL don't know what PC you are using but when I rarely use virtual box it takes me about 2 hours to sync
[Android] mg2195:
Ok, after deleting the overlays it finally finished compiling...however it would only flash if I went to mounts and storage and formatted system, cache and data...wiping didn't work

Once it booted up touch screen was a mess...very unresponsive...its like it never detects my fingers leaving-I find this strange because there is a working cm10, I used the same device tree and same kernel...so you would think it would be just as functional...I'm guessing the overlay had some fixes in it...
[Android] halsafar:
Following these instructions exactly on a near fresh Ubuntu 12.04 install I'm hitting this error. It appears for whatever reason webrtc cannot find STL headers as it compiles.

target arm C++: libwebrtc_system_wrappers <= external/webrtc/src/system_wrappers/source/map.cc
In file included from external/webrtc/src/system_wrappers/source/map.cc:11:0:external/webrtc/src/system_wrappers/source/../interface/map_wrapper.h:14:15: fatal error: map: No such file or directory compilation terminated.
make: *** [out/target/product/generic/obj/STATIC_LIBRARIES/libwebrtc_system_wrappers_intermediates/map.o] Error 1
make: *** Waiting for unfinished jobs....
[Android] dastin1015:
Now that you've got a complete and booting build you can re-add the overlays folder and see which one's conflict during the build and remove as needed.
[Android] yosterwp:
Hey guys, I have gotten AOSP to build for my VZW SIII, yet when I flash the zip in recovery, I get:

set_perm some changes failed

E: <path to zip>

(Status 7)

Immediately after flashing.

After some digging though, I noticed that the trouble begins at "set_perm(0, 0, 0777, "/tmp/backuptool.sh");".

Any ideas?

If it helps, I used make -j2 otapackage to build. And while this flashing error occurs on my S3, it does not occur on my xoom.
[Android] mg2195:
Had that happen to me...I got it to flash by doing normal wipes then going under mounts and storage and formating system, cache, and data...then the flash went through

I looked at my recovery log and the fail you described was caused by running out of space...so I guess the usuall wipes didn't get everything but formating did
[Android] yosterwp:
Thanks for the reply! I had tried your steps by normally wiping everything, then formatting system, cache, and then data. However, my fail is a weird fail (still a fail however). Even after following your steps, I still can't get my zip to flash... I am not sure what is making this so difficult...
[Android] jacobmacek:
same here

virtual box ubuntu network can be epically slow so i just dual boot now and it works like a charm

---------- Post added at 01:41 AM ---------- Previous post was at 01:38 AM ----------

so what lunch menu/compile option combo should i use?
[Android] CallMeVentus:
What device are you building for ?

"Friends forever." - Ventus
[Android] dastin1015:
Earlier you mentioned the HTC Incredible so that is the device you should pick in your lunch menu. full_inc-userdebug
[Android] jacobmacek:
***********************

okay, ill try full-inc userdebug and make otapackage and let you know what i get
[Android] graffitiwriter:
OK well last night I finally got to the point of compiling. About 4hrs in my screen would no longer wake up but I could definitely tell it was still building so I left it alone. This morning the screen was still stuck but the CPU was quiet. so I rebooted, looked and no .zip file. Is there anyway to be able to look back and see what happened? I thought I was actually gonna win this time..lol.
[Android] dastin1015:
Did you make sure to look in out/target/product/{yourDevice}

私のEVO 3Dから送信される。
[Android] yosterwp:
Also make sure that you add "otapackage" at the end of your make command when building
[Android] graffitiwriter:
yes i looked there

The command i used was". build/envsetup.sh && brunch toro". should i use "otapackage" or "make otapackage"on the end ?.I dont know if i had an error or what but i was atleast 6 hrs in when i feel asleep. I plan on trying again tonight. Should i delete all files and resync or just run the build command? Sorry for all the questions just been fighting this biooootch for a while..lol.. thanks for your help, very much appreciated.
[Android] yosterwp:
Don't apologize, I got things to build for my device, but when I flash the zip created in recovery, my phone wont boot into the rom. If you are familiar with the S3, my phone will show the Samsung logo, but never the Samsung Galaxy SIII logo after...

Anyways, I am not an experienced developer, and I do not know if the method for building is different for your ROM, but when I build the source I am building, I use these commands:

. build/envsetup.sh

lunch full_d2vzw-userdebug

^ What comes after "lunch" may be different for your device. What is equally effective is running "lunch" with no parameters, and then manually selecting your device...

make -j2 otapackage

^ I use "-j2" because I only have 2 cores on my machine. Substitute the 2 for the amount of cores you have on your machine. The "make" at the beginning is the command for well, "making" the ROM. The "otapackage" at the end is important, as it will tell the builder (or compiler) to make a flashable zip in addition to fastboot images. If you plan to have the ROM be installed by a recovery on the phone/tablet, this is important.

Again, I have no idea if it will work for the source you are working with. But what's building without a little risk?:laugh:
[Android] dastin1015:
Actually the number is the number of cores of your processor +1.
[Android] yosterwp:
Are you serious? Big derp on my part! I could of used j3 this whole time?!

Cool, thanks for the heads up dastin1015! Why aren't you a recognized contributor? You've ought to be one by now!:D
[Android] dastin1015:
And number of cores * 2 for hyperthreading.

Haha that's because I'm a Recognized Developer. Idk if I can hold multiple titles.

私のEVO 3Dから送信される。
[Android] CallMeVentus:
Oh yes , has CM10 sources supported ARMv6 bionic yet ?

And yes it's possible to be RC/RD at the same time

"Friends forever." - Ventus
[Android] CdTDroiD:
You can use -j8 or something if you want to on a dual core or whatever it will just stress it out more.
[Android] dastin1015:
Not yet. I saw a commit in the gerrit review though.

Oh that's cool. Is it an applied for position like RD?

Yup. I'm just not liable for anybodies computer dying out cause of it.

私のEVO 3Dから送信される。
[Android] CdTDroiD:
Haha +1 on that
[Android] fabzbear:
if I was to use this tutorial to compile ics what would I need to change in the steps? I tried doing the jb but it didn't work.
[Android] CallMeVentus:
I'm currently not very good with Gerrit yet , can you please show me the commit ?

You could either:

- Apply as an RC

OR

- Have someone nominate you as an RC if you meet the criteria specified

I don't know if it's still open , but I'll check for you and nominate you ;)

"Friends forever." - Ventus
[Android] CdTDroiD:
Simply change the "-b android-4.1.1_r3" command to 4.0.3_r1 or whatever the latest ICS is. Check the site for the actual revision
[Android] dastin1015:
Not quite complete yet, but here it is: http://r.cyanogenmod.com/#/c/21092/

Other uncommited bionic commits: http://r.cyanogenmod.com/#/q/status:open+project:CyanogenMod/android_bionic+branch:jellybean,n,z

Thanks! Appreciate that! :D
[Android] NineInchNails:
Going to nominate you myself :)
[Android] toxicthunder:
Could someone please help me out with this -

My device (GT-N7000) is just stuck on the bootanimation. Tried all wipes and battery pulls to no success.

I am fairly new to linux, so do not quite understand the terminologies (but I sure do know that logcats are essential for anyone to be able to help me out :))

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/system

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/system

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/cache

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/cache

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/data

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): tune2fs 1.41.11 (14-Mar-2010)

I/run-parts( 1900): tune2fs: No such file or directory while trying to open /block/path/to/data

I/run-parts( 1900): Couldn't find valid filesystem superblock.

I/run-parts( 1900): run-parts: /system/etc/init.d/04journal exited with code 1
[Android] onlychevys:
I have a stupid question, I got my box all set up and starting to build my own CM nightlies. By following this tutorial would I be building the same thing or more AOSP and only using part of CM's work? I'm having fun now that I'm set up and want to start playing with straight android for more of a challenge. All I'm doing now is compiling CM's hard work. I think by playing with nothing but JB and trying to get it stable on my phone will be a fun challenge. I used a combination of this tutorial and one on CM to get this far and have learned enough to really want to learn more!
[Android] NineInchNails:
Yup this will repo pure AOSP JB. Welcome to the challenge
[Android] onlychevys:
LOL thanks for the reply. You helped me a lot a while back, I promise not to bug ya'll to death with to many questions! But I'm sure I will have some hehe
[Android] cj360:
I get the same error building for xperia play, it might be something with our device tree's but I don't know.
[Android] headcheese:
do i need to run make clean and/or make clobber between builds for different devices?

i want to build for both the grouper and d2vzw.
[Android] yosterwp:
I don't think so, I build for my wingray right after my d2vzw. You should be fine.

By the way, if you are not building CyanogenMod, and you have gotten AOSP (or an AOSP based ROM) to build for d2vzw, does the built rom boot on your d2vzw? Mine doesn't boot. If yours does, can you let me know how you did it?
[Android] headcheese:
Cool thanks. I am building cyanogen mod.
[Android] yosterwp:
Darn... But you are very welcome! Happy building!
[Android] CallMeVentus:
Your HDD space is too little . That's why this error pops up

"Friends forever." - Ventus
[Android] dastin1015:
Yup. I'm not even a third of the way complete with a build and already at 4GB.
[Android] mingolianbeef:
I need a full ubuntu workspace
[Android] mingolianbeef:
Sorry, didn't realize I posted without finishing my sentence, I meant to say I need a full ubuntu workspace so I can use this tutorial.!
[Android] dastin1015:
I dual boot Windows 7 and Ubuntu 12.04 on my laptop.

私のEVO 3Dから送信される。
[Android] mingolianbeef:
ubuntu won't let me install it with over 30 GB of space for the ubuntu environment via wubi, I am running the same setup
[Android] dastin1015:
You can't build from source if you're using Wubi because not enough space. You're going to have to partition your hard drive and with the second partition make it free space. Then install Ubuntu via USB or LiveCD and create a swap partition and root partition with the free space and install.

私のEVO 3Dから送信される。
[Android] cj360:
But my Ubuntu partition has 350gb and I'm only 80~90 gb. Taken up before building.
[Android] CallMeVentus:
Hey there guys , been having problems with otapackage for my Galaxy R....I wonder if you guys can help with Python code , because I know absolutely nothing about it . I don't even know where to look so I can debug it....

Traceback (most recent call last):
File "./device/samsung/galaxyr/releasetools/galaxyr_ota_from_target_files", line 115, in <module>
main(sys.argv[1:])
File "/root/CM9/build/tools/releasetools/ota_from_target_files", line 837, in main
WriteFullOTAPackage(input_zip, output_zip)
File "./device/samsung/galaxyr/releasetools/galaxyr_ota_from_target_files", line 78, in WriteFullOTAPackage
script.MakeSymlinks(symlinks)
File "/root/CM9/build/tools/releasetools/edify_generator.py", line 252, in MakeSymlinks
for d, l in symlink_list:
ValueError: too many values to unpack
[Android] mingolianbeef:
I'm gonna have to wipe my pc data to partition right.?
[Android] dastin1015:
No
[Android] csking33:
Here, one of the best tools I've found for partitioning in windows. Just download the free version. Be patient though, it can take a couple hours, let it do its thing.

http://www.partition-tool.com/download.htm