This is a thread for thoose who want's help with Building Android from source
(This thread will be updates as answer's and new info will be announced)
Currently i am still a noob on this and i may get some info from good AOSP builder's
Make sure to try to fix any problem before disturbing the dev's, this can cause that either you will get a mean answer, or you will get mod on you (often if you doesn't stop begging) (Currently SWEATTAIMI is a pro on that!)
This thread is for those who wants to build Android AOSP
AS
Andy
Bytecode
_Arjen_
luboprhrip
are making their rom's
Have setup the file's as code.google.com has told you to do.
You have agreed and accepted the license terms (yeah, yeah.)
You have, time to try to solve the problem that your facing before posting in any PM!
You Agree that this Topic is for everyone who wants to build from AOSP but need some info about what is what and what problem is caused by what, how to solve and how you can increase your building!
Question's
You're building on Darwin
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. generic_thunderg-eng
5. full_maguro-userdebug
6. full_tuna-userdebug
7. full_panda-eng
Which would you like? [full-eng] 4
build/core/product_config.mk:195: *** device/thunderg/device_thunderg.mk: PRODUCT_NAME must be unique; "thunderg" already used by device/lge/android_device_lge_thunderg/device_thunderg.mk device/thunderg/device_thunderg.mk . Stop.
** Don't have a product spec for: 'generic_thunderg'
** Do you have the right repo manifest?
Answer's
Currently None here ^^
dont u have 2 thunderg folders in device folder?
This is better SWEATTAIMI
Better start to explain how to get your buildingenvironment ready
I advise to use Ubuntu 10.10, because it's most compatible, compiling on Mac is also possible.
Info to setup is here, this is the most important.
Next you need to download the sources (AOSP)
You can also get sources for CyanogenMod or CodeAurora (often referred to as CAF)
Next you need the device and vendor files, for CM7 you can get them from Mik's github or ICS AOSP from Andy's github
Folders they reside in are vendor/lge/thunderg and device/lge/thunderg.
Before you start building you run
Code:
source build/envsetup.sh
or
Code:
. build/envsetup.sh
All device-configs are imported now.
Now you choose what you want to build, in our case it is thunderg, so you can start with
Code:
lunch thunderg-user
After that you start building
Code:
make -j4
This is just a very short guide and no garantuee for succesfull building,
you still need to do a little research yourself.
One tip, Google is your friend
---------- Post added at 09:55 PM ---------- Previous post was at 09:51 PM ----------
SWEATTAIMI said:
You're building on Darwin
Lunch menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. generic_thunderg-eng
5. full_maguro-userdebug
6. full_tuna-userdebug
7. full_panda-eng
Which would you like? [full-eng] 4
build/core/product_config.mk:195: *** device/thunderg/device_thunderg.mk: PRODUCT_NAME must be unique; "thunderg" already used by device/lge/android_device_lge_thunderg/device_thunderg.mk device/thunderg/device_thunderg.mk . Stop.
** Don't have a product spec for: 'generic_thunderg'
** Do you have the right repo manifest?
Click to expand...
Click to collapse
Try lunch-thunderg-user instead
Oh, and read prev. post for correct locations for the files
ciolnadu said:
dont u have 2 thunderg folders in device folder?
Click to expand...
Click to collapse
I have one also then it says not there are you using right repo? Don't get it i did as told still this folder stuff
Sent from my LG-P500 using xda premium
_Arjen_ said:
This is better SWEATTAIMI
Better start to explain how to get your buildingenvironment ready
I advise to use Ubuntu 10.10, because it's most compatible, compiling on Mac is also possible.
Info to setup is here, this is the most important.
Next you need to download the sources (AOSP)
You can also get sources for CyanogenMod or CodeAurora (often referred to as CAF)
Next you need the device and vendor files, for CM7 you can get them from Mik's github or ICS AOSP from Andy's github
Folders they reside in are vendor/lge/thunderg and device/lge/thunderg.
Before you start building you run
Code:
source build/envsetup.sh
or
Code:
. build/envsetup.sh
All device-configs are imported now.
Now you choose what you want to build, in our case it is thunderg, so you can start with
Code:
lunch thunderg-user
After that you start building
Code:
make -j4
This is just a very short guide and no garantuee for succesfull building,
you still need to do a little research yourself.
One tip, Google is your friend
---------- Post added at 09:55 PM ---------- Previous post was at 09:51 PM ----------
Try lunch-thunderg-user instead
Oh, and read prev. post for correct locations for the files
Click to expand...
Click to collapse
The thing is when i see the device in lunch i can't make anything either it says i got two files or asks if i got right repo
Sent from my LG-P500 using xda premium
SWEATTAIMI said:
The thing is when i see the device in lunch i can't make anything either it says i got two files or asks if i got right repo
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
paste here your error and we will try to solve it
BTW, i am building froyo 2.2.2 from aosp, and now i have this issue:
Code:
target asm: libdvm <= dalvik/vm/compiler/codegen/arm/armv6-vfp/CallingConvention.S
target asm: libdvm <= dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S: Assembler messages:
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:7572: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:7576: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8094: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8097: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8178: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8181: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8278: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8282: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8501: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8508: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8741: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8742: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8747: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9342: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9349: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9372: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9373: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9378: Error: cannot represent SHIFT_IMM relocation in this object file format
make: *** [out/target/product/thunderg/obj/SHARED_LIBRARIES/libdvm_intermediates/mterp/out/InterpAsm-armv6-vfp.o] Errore 1
make: *** Attesa per i processi non terminati....
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S: Assembler messages:
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S:367: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S:380: Error: internal_relocation (type: OFFSET_IMM) not fixed up
make: *** [out/target/product/thunderg/obj/SHARED_LIBRARIES/libdvm_intermediates/compiler/template/out/CompilerTemplateAsm-armv6-vfp.o] Errore 1
does someone know how to solve it?
It is because you have the android_device etc folder still in it.
move these files to correct location and remove folder.
also do not choose from within lunch, but enter what i mentioned above.
_Arjen_ said:
It is because you have the android_device etc folder still in it.
move these files to correct location and remove folder.
also do not choose from within lunch, but enter what i mentioned above.
Click to expand...
Click to collapse
question, im trying to build ICS for the lg Optimus M, thunderc board. i have the same dalvik error as above with the InterAsm_armv6-vfp.S. what do you mean by your above statement? android_device etc folder? i have an etc folder, looks something like this im my tree, device/lge/thunderc/files/etc/ however, everything int hat folder is being pointed to correctly. the make files are making the correct calls to the correct places. also, i took my InterAsm-armv6-vfp.S file from a cm7 gingerbread build. would that have an effect? Ive been working on this for a few weeks, worked through many errors, but this one has me at a loss on how to fix it. any help you can provide would be greatly appreciated.
What I meant for SWEATTAIMI is that he/she (still don know how to call it ) didn't extract files correctly and left some old unpacked folders.
In your case all seems fine.
You can take build, dalvik and core from Andy's github, this should solve build problems.
sorry didnt mean to jack the thread. thanx for the info though, i took a look at andys changes and applied the changes to my armv6-vfp.mk file to see if that helped. thanx again.
Related
Hi, can someone guide me how to build the kernel for I9100G? I downloaded the kernel source from Samsung and extracted. The instructions in the archive are as follows:
HOW TO BUILD KERNEL 2.6.35 FOR GT-I9100G
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2010q1 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ toolchain\arm-2010q1
$ cd kernel/
$ make t1_defconfig
$ make
2. Output files
- Kernel : kernel/arch/arm/boot/zImage
3. How to make .tar binary for downloading into target.
- change current directory to kernel/arch/arm/boot
- type following command
$ tar cvf GT-I9100G_Kernel_Gingerbread.tar zImage
Click to expand...
Click to collapse
Looks simple enough. So I downloaded the toolchain from CodeSourcery and installed. I don't quite understand the first line in step 1
$ toolchain\arm-2010q1
Click to expand...
Click to collapse
What does that mean, exactly? Typing it out just like that gives an error.
If I skip the first line, after "make t1_defconfig", I get the error message "make: *** No rule to make target `t1_defconfig'. Stop."
Help, please?
BTW, I'm using Kubuntu 11.10.
Got it finally. Turned out my dump of the kernel source code was bad and some files were corrupted. Plus, crappy instructions, make t1_defconfig doesn't work. Instead I did
make ARCH=arm CROSS_COMPILE=~/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi- t1_defconfig
make ARCH=arm CROSS_COMPILE=~/CodeSourcery/Sourcery_G++_Lite/bin/arm-none-eabi-
Compiling now. Hope for the best.
---
Doesn't work.
Got this error:
In file included from drivers/media/video/omapgfx/gfx_bc.c:17:
drivers/gpu/pvr/img_defs.h:89: error: #error ("define an OS")
In file included from drivers/media/video/omapgfx/gfx_bc.c:18:
drivers/gpu/pvr/servicesext.h:811: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'PVRSRVReadRegistryString'
drivers/gpu/pvr/servicesext.h:812: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'PVRSRVWriteRegistryString'
In file included from drivers/media/video/omapgfx/gfx_bc.c:19:
drivers/gpu/pvr/kernelbuffer.h:66: error: expected '=', ',', ';', 'asm' or '__attribute__' before 'IMG_BOOL'
drivers/media/video/omapgfx/gfx_bc.c: In function 'bc_init':
drivers/media/video/omapgfx/gfx_bc.c:381: error: implicit declaration of function 'PVRGetBufferClassJTable'
make[4]: *** [drivers/media/video/omapgfx/gfx_bc.o] Error 1
make[3]: *** [drivers/media/video/omapgfx] Error 2
make[2]: *** [drivers/media/video] Error 2
make[1]: *** [drivers/media] Error 2
make: *** [drivers] Error 2
Click to expand...
Click to collapse
Experienced devs, anyone, help please?
Hi
I too am trying to build the kernel and I am stuck at same error. Can you please let me know how did you resolve this error?
Thanks in advance
Just in case anyone is still looking for solution:
I had the same problem. But managed to compile it successfully, under Ubuntu, using the prebuilt toolchains inside Android's NDK. Simply download, extract and start compiling.
I was able to build kernel successfully using arm linux gnueabi toolchain. Thanks for the help guys. Now I am all set to create a custom kernel
---------- Post added at 10:52 PM ---------- Previous post was at 10:50 PM ----------
The error was coming because of undefined macro for __linux__.
Can be resolved by either replacing it with LINUX or using arm linux gnueabi toolchain instead of arm eabi.
any update ?
or can u share how to build/make a custom rom so i can also try to make a custom rom
thnx!
PROJECT SWITCHED TO GINGERBREAD 2.3.7
Why have i started this thread?
I started this thread to obtain help from XDA's community (especially from devs) because i am not a real dev so i need some help.
What is this thread about?
This thread is about building Gingerbread 2.3.7 from sources.
Why have i started this project?
I started this project because i want to learn something more about Android and because i think that a real rom should be make building it from sources.
At the moment i don't know if i will release a rom....this is a development thread so please don't ask for a rom.
Thanks to all people who helped me in the past and will help me now with this project.
First u should of put this thread in general
second u can look here
http://forum.xda-developers.com/showthread.php?t=915435
it will help u a lot.
and now the first building problem:
host Java: clearsilver (out/host/common/obj/JAVA_LIBRARIES/clearsilver_intermediates/classes)
make: *** No rules to make target "out/target/common/obj/JAVA_LIBRARIES/core_intermediates/javalib.jar", needed for "out/target/common/docs/api-stubs-timestamp". Stop.
does someone know how to fix this problem?
i have searched on google....but i have not found the solution.
re sync on clean repo - you miss something
mikegapinski said:
re sync on clean repo - you miss something
Click to expand...
Click to collapse
repo cleaned and re synced.....i have the same problem
problem solved
i have merged /vendor/lge/thunderg from mik's github and andy's github.....now i am building froyo
now i have this issue:
Code:
target asm: libdvm <= dalvik/vm/compiler/codegen/arm/armv6-vfp/CallingConvention.S
target asm: libdvm <= dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S: Assembler messages:
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:7572: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:7576: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8094: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8097: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8178: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8181: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8278: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8282: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8501: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8508: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8741: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8742: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:8747: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9342: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9349: Error: cannot represent SHIFT_IMM relocation in this object file format
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9372: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9373: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/mterp/out/InterpAsm-armv6-vfp.S:9378: Error: cannot represent SHIFT_IMM relocation in this object file format
make: *** [out/target/product/thunderg/obj/SHARED_LIBRARIES/libdvm_intermediates/mterp/out/InterpAsm-armv6-vfp.o] Errore 1
make: *** Attesa per i processi non terminati....
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S: Assembler messages:
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S:367: Error: internal_relocation (type: OFFSET_IMM) not fixed up
dalvik/vm/compiler/template/out/CompilerTemplateAsm-armv6-vfp.S:380: Error: internal_relocation (type: OFFSET_IMM) not fixed up
make: *** [out/target/product/thunderg/obj/SHARED_LIBRARIES/libdvm_intermediates/compiler/template/out/CompilerTemplateAsm-armv6-vfp.o] Errore 1
does someone know how to solve it?
i don't find anything on google....
at first:
you are trying to build froyo, right?
here you cant use device or vendor folders from a gingerbread or a ics build environment,
you need the folders for build froyo.
about dalvik error:
you need dalvik for froyo, not for gingerbread or ics.
make sure, you first download a complete repo from only ONE git/svn account.
andy572 said:
at first:
you are trying to build froyo, right?
here you cant use device or vendor folders from a gingerbread or a ics build environment,
you need the folders for build froyo.
about dalvik error:
you need dalvik for froyo, not for gingerbread or ics.
make sure, you first download a complete repo from only ONE git/svn account.
Click to expand...
Click to collapse
Thanks andy ....i will search for the correct froyo sources.
Inviato dal mio LG-P500 usando Tapatalk
If you want to build froyo from source with all LG-****, download sources from LG-website.
Inside there is a readme on how to build.
I know it isn't the same as how we are building Gingerbread/CM7 with the device and vendor files, but it is working.
_Arjen_ said:
If you want to build froyo from source with all LG-****, download sources from LG-website.
Inside there is a readme on how to build.
I know it isn't the same as how we are building Gingerbread/CM7 with the device and vendor files, but it is working.
Click to expand...
Click to collapse
I don‘t want to build with all lg ****...i only need the correct vendor and device folder.
Inviato dal mio LG-P500 usando Tapatalk
@Matt sorry for ot but could you look into this n say if it would work on your blackbird or any cm7 rom?
http://forum.xda-developers.com/showthread.php?t=1380006
Sent from my LG-P500 using xda premium
matteof93 said:
I don‘t want to build with all lg ****...i only need the correct vendor and device folder.
Inviato dal mio LG-P500 usando Tapatalk
Click to expand...
Click to collapse
Then you will need to make them,
you can use mik's or Andy's as guideline.
Replace all with froyo stuff (little changes are needed I guess).
Perhaps you can ask Bytecode, he is working on CM6 (also Froyo).
_Arjen_ said:
Then you will need to make them,
you can use mik's or Andy's as guideline.
Replace all with froyo stuff (little changes are needed I guess).
Perhaps you can ask Bytecode, he is working on CM6 (also Froyo).
Click to expand...
Click to collapse
mmm...so there aren't available sources of P500 to build froyo as i wish to do.
i think i should try to build CM7 with knzo's tutorial or a version of gingerbread to learn how to build a rom...and then i could try to build froyo.
androidusero1p500 said:
@Matt sorry for ot but could you look into this n say if it would work on your blackbird or any cm7 rom?
http://forum.xda-developers.com/showthread.php?t=1380006
Sent from my LG-P500 using xda premium
Click to expand...
Click to collapse
it could work....you have only to try it
i have switched to gingerbread 2.3.7 because i can use mik's or andy's P500 sources.
now the question is: which sources should i use? device and vendor sources from mik or from andy? which is the difference?
its only a very small difference:
mik's sources are for Gingerbread and its working, my sources are ICS and its not
working. before you ask every hour a new question: please read some tutorials about
how to build android, and ... read about how to solve basic things. you better shouldnt
build a rom without basic knowledge - its not meant sad, you need some experience
to do that all, and only copy sources and build a rom its senseless.
andy572 said:
its only a very small difference:
mik's sources are for Gingerbread and its working, my sources are ICS and its not
working. before you ask every hour a new question: please read some tutorials about
how to build android, and ... read about how to solve basic things. you better shouldnt
build a rom without basic knowledge - its not meant sad, you need some experience
to do that all, and only copy sources and build a rom its senseless.
Click to expand...
Click to collapse
you're right.
i have read some tutorials (official tutorials by google and some tutorials here on xda).
i know that mik's sources work, but i didn't know that your sources were only for ICS.
BTW, good luck with your amazing rom phoenix
ps: you are right saying that i should have at least a basic knowledge about building android, but i think that the better way to learn is to try and understand your errors
building android is most simple if you have almost working code,
but you have to ask your self some things:
what is the next step if i have build the rom and almost all is working?
release a rom that allready exists or make new things? do i have some ideas
to bring in there are in no other rom or features there arent in other roms?
can i optimize code other than in other roms? what can i support? do i have
enough experience about android to answer technical questions? you have to
think about "dumb" users (not meant sad here) there can ask difficult questions
like "he, this and that isnt working - can you solve that?" or users want to have
new things - what do you want to do than? you cant every time answer
"sorry, i only know about how to build a from - i'm not a developer".
i think, this are basic things to think about
if you think about to play with android only (why even not) do that and learn,
its a question of time until you get enough experience/knowledge the next months
to become a "real android developer"
andy572 said:
building android is most simple if you have almost working code,
but you have to ask your self some things:
what is the next step if i have build the rom and almost all is working?
release a rom that allready exists or make new things? do i have some ideas
to bring in there are in no other rom or features there arent in other roms?
can i optimize code other than in other roms? what can i support? do i have
enough experience about android to answer technical questions? you have to
think about "dumb" users (not meant sad here) there can ask difficult questions
like "he, this and that isnt working - can you solve that?" or users want to have
new things - what do you want to do than? you cant every time answer
"sorry, i only know about how to build a from - i'm not a developer".
i think, this are basic things to think about
if you think about to play with android only (why even not) do that and learn,
its a question of time until you get enough experience/knowledge the next months
to become a "real android developer"
Click to expand...
Click to collapse
Damn right. Matt,obviously you need a tutor (andy and Arjen taught me really lots of stuff so thanks to both) but in the end you will surely learn how to do builds alone. I now encounter various issues in OMFGB and CAF which sometimes I can solve myself,sometimes I use google.
It's only a matter of time
Hello,
I want build the kernel of Xperia S but I hava this error :
Code:
arch/arm/mach-msm/qdsp6v2/audio_acdb.c: In function 'store_vocvol_cal':
/home/cemal/Bureau/Sourceicsxs/kernel/arch/arm/include/asm/atomic.h:249: error: 'asm' operand requires impossible reload
Thank you !
Solved
Solved I write in the Makefile the flag --disable-werror. Nice
Edit : BUT i have a new error
Code:
arch/arm/mach-msm/qdsp6v2/audio_acdb.c: In function 'store_vocvol_cal':
/home/cemal/Bureau/Sourceicsxs/kernel/arch/arm/include/asm/atomic.h:249: error: 'asm' operand requires impossible reload
make[2]: *** [arch/arm/mach-msm/qdsp6v2/audio_acdb.o] Erreur 1
make[1]: *** [arch/arm/mach-msm/qdsp6v2] Erreur 2
make: *** [arch/arm/mach-msm] Erreur 2
Anything Ideas ?
c3ma138 said:
Solved I write in the Makefile the flag --disable-werror. Nice
Edit : BUT i have a new error
Code:
arch/arm/mach-msm/qdsp6v2/audio_acdb.c: In function 'store_vocvol_cal':
/home/cemal/Bureau/Sourceicsxs/kernel/arch/arm/include/asm/atomic.h:249: error: 'asm' operand requires impossible reload
make[2]: *** [arch/arm/mach-msm/qdsp6v2/audio_acdb.o] Erreur 1
make[1]: *** [arch/arm/mach-msm/qdsp6v2] Erreur 2
make: *** [arch/arm/mach-msm] Erreur 2
Anything Ideas ?
Click to expand...
Click to collapse
You shouldn't have to edit the Makefile. Are you using the tool chain recommended by Sony? Make sure your path selects them before anything else. Also I would reset locale to C before compiling ("Erreur"?!), it may play some tricks.
kuisma said:
You shouldn't have to edit the Makefile. Are you using the tool chain recommended by Sony? Make sure your path selects them before anything else. Also I would reset locale to C before compiling ("Erreur"?!), it may play some tricks.
Click to expand...
Click to collapse
I use the ndk toolchain, where can I find the Sony toolchain
Edit : arm-[...].4.6
c3ma138 said:
I use the ndk toolchain, where can I find the Sony toolchain
Edit : arm-[...].4.6
Click to expand...
Click to collapse
You find the specific instructions for the Xperia S at http://developer.sonymobile.com/wp/...-archive-released-with-building-instructions/ referring to the kernel building howto at http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ recommending you to use the tool chain at https://sourcery.mentor.com/sgpp/lite/arm/portal/[email protected]=lite
Follow those instructions before start tinkering with Makefiles, tools, build environment etc and I'm sure you'll succeed.
And reset locale to C! I.e. unset the LANG and LC_* environment variables in your shell before running the build scripts.
kuisma said:
You find the specific instructions for the Xperia S at http://developer.sonymobile.com/wp/...-archive-released-with-building-instructions/ referring to the kernel building howto at http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/ recommending you to use the tool chain at https://sourcery.mentor.com/sgpp/lite/arm/portal/[email protected]=lite
Follow those instructions before start tinkering with Makefiles, tools, build environment etc and I'm sure you'll succeed.
And reset locale to C! I.e. unset the LANG and LC_* environment variables in your shell before running the build scripts.
Click to expand...
Click to collapse
thank you,
But this does not work
I download: https://sourcery.mentor.com/sgpp/lite/arm/portal/release2188
then: http://developer.sonymobile.com/wportal/devworld/downloads/download/61a0452tarbz2
I unzipped all in my Desktop and in a terminal, I wrote:
- cd source/kernel
- ARCH=arm CROSS_COMPILE=/home/cemal/Bureau/arm-2012.03/bin/arm-none-eabi- make fuji_nozomi_defconfig
- ARCH=arm CROSS_COMPILE=/home/cemal/Bureau/arm-2012.03/bin/arm-none-eabi- make
c3ma138 said:
But this does not work
Click to expand...
Click to collapse
Sorry, but I'm no mind reader. "does not work" is not sufficient information for me to reply anything helpful to.
The basic is, if you don't know what you are doing, do it by the book. Still not working? Ask for help. Sony Xperia has presented quite a verbose instruction about how to compile their kernels. Try following this before choosing your own tool chain, edit Makefiles and so. When you get problems, read the instructions more carefully and/or ask the community (hi!) for help, with somewhat more detailed information about what you did and how it failed. The more verbose information you present, the more likely you are to get a useful reply.
Best of luck.
------------------
(edit)
A curious question, why do you want to compile a new kernel? I get the impression this is not your field of expertise, and maybe you are trying to achieve something somewhat more complicated than needed.
Hello,
I encounter the same kind of issue. Does anyone could help me ?
I work in an Ubuntu PC (10.04).
I have downloaded the toolchain for Linux from sourcery.mentor.com (arm-2012.03-57-arm-none-linux-gnueabi.bin)
Then the kernel source code 6.1.A.0.452 from developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-build-6-1-a-0-452-6-1-a-0-453-and-6-1-a-0-454
and I execute:
cd kernel
ARCH=arm CROSS_COMPILE=~/Toolchain/ARM_GNU_Linux/bin/arm-none-linux-gnueabi- make fuji_nozomi_defconfig
ARCH=arm CROSS_COMPILE=~/Toolchain/ARM_GNU_Linux/bin/arm-none-linux-gnueabi- make
Then I have the following error:
CC arch/arm/mm/proc-syms.o
CC arch/arm/mm/alignment.o
arch/arm/mm/alignment.c: In function 'do_alignment':
arch/arm/mm/alignment.c:298:15: warning: 'offset.un' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: alignment.c:298
make[1]: *** [arch/arm/mm/alignment.o] Error 1
make: *** [arch/arm/mm] Error 2
Many thanks in advance for your help
zongojim said:
Hello,
I encounter the same kind of issue. Does anyone could help me ?
I work in an Ubuntu PC (10.04).
I have downloaded the toolchain for Linux from sourcery.mentor.com (arm-2012.03-57-arm-none-linux-gnueabi.bin)
Then the kernel source code 6.1.A.0.452 from developer.sonymobile.com/downloads/xperia-open-source-archives/open-source-archive-for-build-6-1-a-0-452-6-1-a-0-453-and-6-1-a-0-454
and I execute:
cd kernel
ARCH=arm CROSS_COMPILE=~/Toolchain/ARM_GNU_Linux/bin/arm-none-linux-gnueabi- make fuji_nozomi_defconfig
ARCH=arm CROSS_COMPILE=~/Toolchain/ARM_GNU_Linux/bin/arm-none-linux-gnueabi- make
Then I have the following error:
CC arch/arm/mm/proc-syms.o
CC arch/arm/mm/alignment.o
arch/arm/mm/alignment.c: In function 'do_alignment':
arch/arm/mm/alignment.c:298:15: warning: 'offset.un' may be used uninitialized in this function [-Wuninitialized]
error, forbidden warning: alignment.c:298
make[1]: *** [arch/arm/mm/alignment.o] Error 1
make: *** [arch/arm/mm] Error 2
Many thanks in advance for your help
Click to expand...
Click to collapse
You need android-ndk-r5b to compile the Xperia kernel source. I.e. you can not use the latest NDK.
Thanks a lot for your answer
Unfortunately, I didn't find android-ndk-r5b for Linux.
Could you kindly indicate me where I can get it ?
thanks !
zongojim said:
Thanks a lot for your answer
Unfortunately, I didn't find android-ndk-r5b for Linux.
Could you kindly indicate me where I can get it ?
thanks !
Click to expand...
Click to collapse
http://dl.google.com/android/ndk/android-ndk-r5b-linux-x86.tar.bz2
Thanks again, I really apreciate your support !
I have downladed and extracted android-ndk-r5b to my Ubuntu station.
it seems that is is not a built version, right ?
I have tried to navigate in the documentation, but it does not look so trivial...
Would you know how to simply compile it ?
zongojim said:
Thanks again, I really apreciate your support !
I have downladed and extracted android-ndk-r5b to my Ubuntu station.
it seems that is is not a built version, right ?
I have tried to navigate in the documentation, but it does not look so trivial...
Would you know how to simply compile it ?
Click to expand...
Click to collapse
It's compiled ready to use.
Read the documentation at http://developer.sonymobile.com/wp/2011/05/06/how-to-build-a-linux-kernel/
Replace the toolchain path with e.g. "CROSS_COMPILE=/opt/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi-" and you are good to go.
ok nice.
Then I tried again and... I've got a different error !
Here is what I have done:
$ ARCH=arm CROSS_COMPILE=~/Toolchain/arm-2011.03-41-arm-none-linux-gnueabi/bin/arm-none-ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make fuji_nozomi_defconfig
arch/arm/mach-msm/Kconfig:2107:warning: defaults for choice values not supported
arch/arm/mach-msm/Kconfig:2113:warning: defaults for choice values not supported
#
# configuration written to .config
#
$ ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make clean
$ ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make
scripts/kconfig/conf --silentoldconfig Kconfig
arch/arm/mach-msm/Kconfig:2107:warning: defaults for choice values not supported
arch/arm/mach-msm/Kconfig:2113:warning: defaults for choice values not supported
make[1]: `include/generated/mach-types.h' is up to date.
arch/arm/kernel/return_address.c:62:2: warning: #warning "TODO: return_address should use unwind tables"
arch/arm/mach-msm/qdsp6v2/audio_acdb.c: In function 'store_vocvol_cal':
/prj/mms/smdswv/users/jmgrimaud/Xperia/6.1.A.0.452/kernel/arch/arm/include/asm/atomic.h:249: error: 'asm' operand requires impossible reload
make[2]: *** [arch/arm/mach-msm/qdsp6v2/audio_acdb.o] Error 1
make[1]: *** [arch/arm/mach-msm/qdsp6v2] Error 2
make: *** [arch/arm/mach-msm] Error 2
zongojim said:
ok nice.
Then I tried again and... I've got a different error !
Here is what I have done:
$ ARCH=arm CROSS_COMPILE=~/Toolchain/arm-2011.03-41-arm-none-linux-gnueabi/bin/arm-none-ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make fuji_nozomi_defconfig
arch/arm/mach-msm/Kconfig:2107:warning: defaults for choice values not supported
arch/arm/mach-msm/Kconfig:2113:warning: defaults for choice values not supported
#
# configuration written to .config
#
$ ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make clean
$ ARCH=arm CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-linux-androideabi-4.4.3/prebuilt/linux-x86/bin/arm-linux-androideabi- make
scripts/kconfig/conf --silentoldconfig Kconfig
arch/arm/mach-msm/Kconfig:2107:warning: defaults for choice values not supported
arch/arm/mach-msm/Kconfig:2113:warning: defaults for choice values not supported
make[1]: `include/generated/mach-types.h' is up to date.
arch/arm/kernel/return_address.c:62:2: warning: #warning "TODO: return_address should use unwind tables"
arch/arm/mach-msm/qdsp6v2/audio_acdb.c: In function 'store_vocvol_cal':
/prj/mms/smdswv/users/jmgrimaud/Xperia/6.1.A.0.452/kernel/arch/arm/include/asm/atomic.h:249: error: 'asm' operand requires impossible reload
make[2]: *** [arch/arm/mach-msm/qdsp6v2/audio_acdb.o] Error 1
make[1]: *** [arch/arm/mach-msm/qdsp6v2] Error 2
make: *** [arch/arm/mach-msm] Error 2
Click to expand...
Click to collapse
Only specify ONE toolchain ...
Also, I'm note quite sure if I used 4.4.0 or 4.4.3, since both are included in the same r5b distribution. You can also try;
CROSS_COMPILE=~/Toolchain//android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
Thank you kuisma.
Sorry it was a copy/paste error, I had for sure specified only one toolchain.
So I am making a new test with CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
I'll keep you informed
---------- Post added at 11:51 AM ---------- Previous post was at 11:15 AM ----------
It built, thanks again for your support, kuisma !
Not sure it is still in the scope of this topic, but continuing to execute the instructions found in developer.sonymobile.com/2011/05/06/how-to-build-a-linux-kernel/, I have some questions regarding Step C, absolutly not clear for me
What should I do exactly to prepare my boot.img ? What have I to do to create a ramdisk.img file, or where can I find it ? (in fact I do not know what it the ramdisk in the picture...is it required ?)
zongojim said:
Thank you kuisma.
Sorry it was a copy/paste error, I had for sure specified only one toolchain.
So I am making a new test with CROSS_COMPILE=~/Toolchain/android-ndk-r5b/toolchains/arm-eabi-4.4.0/prebuilt/linux-x86/bin/arm-eabi-
I'll keep you informed
---------- Post added at 11:51 AM ---------- Previous post was at 11:15 AM ----------
It built, thanks again for your support, kuisma !
Not sure it is still in the scope of this topic, but continuing to execute the instructions found in developer.sonymobile.com/2011/05/06/how-to-build-a-linux-kernel/, I have some questions regarding Step C, absolutly not clear for me
What should I do exactly to prepare my boot.img ? What have I to do to create a ramdisk.img file, or where can I find it ? (in fact I do not know what it the ramdisk in the picture...is it required ?)
Click to expand...
Click to collapse
Start with the original root filesystem from the standard boot.img you are already running.
You'll find my tool working with boot.img here: http://whiteboard.ping.se/Android/Unmkbootimg
Also, read the links on the page my signature links to, to get more information about how to build boot images, root file systems etc.
The ramdisk contains the root filesystem, and yes, it's very much needed.
Ok understood
last point: how to retrieve the boot.img from my Xperia S phone ? (that is already unlocked)
zongojim said:
Ok understood
last point: how to retrieve the boot.img from my Xperia S phone ? (that is already unlocked)
Click to expand...
Click to collapse
Last? Ok, I'll take your word for it.
http://www.youtube.com/watch?v=bB77gWRUI_A
Remember, Google is your friend.
help me somebody please
i'm trying to build custom kernel for my xperia M dual
got sources from sony's website, doing build by guide
here is an error:
Code:
In file included from drivers/usb/gadget/android.c:51:0:
drivers/usb/gadget/f_qdss.c: In function 'qdss_bind_config':
drivers/usb/gadget/f_qdss.c:586:38: warning: argument to 'sizeof' in 'strncmp' call is the same expression as the second source; did you mean to provide an explicit length? [-Wsizeof-pointer-memaccess]
error, forbidden warning: f_qdss.c:586
make[3]: *** [drivers/usb/gadget/android.o] Error 1
make[2]: *** [drivers/usb/gadget] Error 2
make[1]: *** [drivers/usb] Error 2
make: *** [drivers] Error 2
is it an NDK version issue?
I'm running:
Code:
make -j8 ARCH=arm CROSS_COMPILE=/home/dev/MentorGraphics/Sourcery_CodeBench_Lite_for_ARM_GNU_Linux/bin/arm-none-linux-gnueabi-
thanks
Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
InfinityFTW said:
Hi guys!
I hereby state that I am a github and source-building n00b, and i could need your help
The thing is, I want to build a PAC-man ROM for the HTC Sensation. The pacman source is on github: https://github.com/PAC-man
And here is the device specific files, which I forked form the Pyramid CM10 Repo (Just to explore github) : https://github.com/InfinityFTW/android_device_htc_pyramid
And I was wondering, how does one add these files into the ROM, in order to build it properly?
I have searched, but I could not find a solution. I have heard about merging it in with the sources, but i'm not sure what way to go
If someone is familiar with this, please let me know.
Thanks
Click to expand...
Click to collapse
You need to clone device tree
Code:
cd android
cd device
mkdir htc
cd htc
git clone git://github.com/InfinityFTW/android_device_htc_pyramid.git -b jellybean pyramid
Then you need extract propietary files
Code:
cd pyramid
./extract-files.sh
And finally type
Code:
. build/envsetup.sh
lunch "select your device"
make -j4
Enviado desde mi X10i
Building error?
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
hey im trying to work my way thru the same thing...there is a lot of info out there, it takes forever to sort your way thru it..
so...first off, it helps us figure out problems with its output..do what it says.
sudo apt-get install schedtool
start there, then try again and see what comes up next
InfinityFTW said:
I got to the build part, and when i run the commands i got from a tutorial about compiling cm10 for the pyramid, and here is the entire log:
Code:
[email protected]:~/android/system$ . build/envsetup.sh; lunch cm_pyramid-userdebug; mka bacon
including device/generic/armv7-a-neon/vendorsetup.sh
including device/generic/armv7-a/vendorsetup.sh
including device/ti/panda/vendorsetup.sh
including vendor/cm/vendorsetup.sh
including vendor/pa/vendorsetup.sh
including sdk/bash_completion/adb.bash
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
Device pyramid not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_htc_pyramid
Adding dependency: CyanogenMod/android_device_htc_pyramid -> device/htc/pyramid
Syncing repository to retrieve project.
error: .repo/manifests/: contains uncommitted changes
Repository synced!
Looking for dependencies
Adding dependencies to manifest
Adding dependency: CyanogenMod/android_device_htc_msm8660-common -> device/htc/msm8660-common
Syncing dependencies
error: .repo/manifests/: contains uncommitted changes
Done
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
** Don't have a product spec for: 'cm_pyramid'
** Do you have the right repo manifest?
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
What to do?
Click to expand...
Click to collapse
first of all
HTML:
The program 'schedtool' is currently not installed. You can install it by typing:
sudo apt-get install schedtool
there is a software missing install it next...
HTML:
build/core/product_config.mk:189: *** _nic.PRODUCTS.[[device/*/pyramid/cm.mk]]: "device/htc/msm8660-common/msm8660.mk" does not exist. Stop.
it has found pyramid/cm.mk required for building but your device is configured to use the common config of msm8660 cpu so its looking for
msm8660-common
in device folder
htc
therefore find the common config download it via zip rename the folder containing the files to
msm8660-common
copy and paste it in htc folder then follow the previuos commands... i will subscribe to this thread if you get any more errors post on this thread i will be happy to help
Thanks for everything, guys, and i have now attempted to build
i used otapackage, and it seems to have stopped. Here is the latest output:
Code:
/home/martin/android/system/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: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1956: error: undefined reference to 'msm_get_voc_session'
/home/martin/android/system/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: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1961: error: undefined reference to 'msm_start_voice_ext'
/home/martin/android/system/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: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1962: error: undefined reference to 'msm_set_voice_tx_mute_ext'
/home/martin/android/system/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: /home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/AudioHardware.o: in function android_audio_legacy::AudioHardware::doAudioRouteOrMute(unsigned int):hardware/qcom/audio/msm8660/AudioHardware.cpp:1982: error: undefined reference to 'msm_end_voice_ext'
collect2: ld returned 1 exit status
make: *** [/home/martin/android/system/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so] Error 1
[email protected]:~/android/system$
just the last few lines wont help post more of what happened before the breaking of the build
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
Well, on pacmans git, there are instructions on how to build Pac-man, which includes a build-pac.sh script, and it says command not found when i run it. And i forked the htc pyramid device repo into pacmans gerrit, so i will try to do everything again, maybe something went wrong during cloning or syncing
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
speed_bot said:
dont use the pac script is the normal way of lunch or brunch...btw have u extracted the vendors?
Click to expand...
Click to collapse
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
you dont need to delete and resync again instead do
PHP:
make clean
and
HTML:
make clobber
to delete all compiled files and if you have modified the source do
HTML:
git checkout
it will remove all local changes that was you can save time and bandwidth ...
---------- Post added at 07:11 AM ---------- Previous post was at 07:10 AM ----------
InfinityFTW said:
Do you mean propartiary-files.sh?
And btw, i had my local repo cluttered with previous attempts at building PA, so i deleted everything and init'd the repo and synced it again.
Click to expand...
Click to collapse
propeitary files and just vendors for the device they cant break the build process///
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Racing19969 said:
Did you figure it out? if not let me know and I can help you.. send me a P.M.
Click to expand...
Click to collapse
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
InfinityFTW said:
When I try to do make clean and make clobber, it says something like: Fatal, not a git repository, so I was unable to start over -.-
Sent from a muffin inside a muffin using muffintalk.
Click to expand...
Click to collapse
if thats the error your sources havent synced completely yet
It probably would not build, coz when it gives you to choose you will choose cm_* and it will build cm10.To buil PAC you need to choose pac_*
If I am not right please correct me.
Code:
Erachter system # lunch
You're building on Linux
Breakfast menu... pick a combo:
1. full-eng
2. full_x86-eng
3. vbox_x86-eng
4. mini_armv7a_neon-userdebug
5. mini_armv7a-userdebug
6. full_panda-userdebug
7. cm_a700-userdebug
8. cm_anzu-userdebug
9. cm_captivatemtd-userdebug
10. cm_crespo-userdebug
11. cm_crespo4g-userdebug
12. cm_coconut-userdebug
13. cm_d2att-userdebug
14. cm_d2mtr-userdebug
15. cm_d2spr-userdebug
16. cm_d2tmo-userdebug
17. cm_d2usc-userdebug
18. cm_d2vzw-userdebug
19. cm_encore-userdebug
20. cm_endeavoru-userdebug
21. cm_epicmtd-userdebug
22. cm_everest-userdebug
23. cm_evita-userdebug
24. cm_fascinatemtd-userdebug
25. cm_galaxysbmtd-userdebug
26. cm_galaxysmtd-userdebug
27. cm_grouper-userdebug
28. cm_haida-userdebug
29. cm_hallon-userdebug
30. cm_hercules-userdebug
31. cm_i777-userdebug
32. cm_i9100-userdebug
33. cm_i9100g-userdebug
34. cm_i9300-userdebug
35. cm_iyokan-userdebug
36. cm_jewel-userdebug
37. cm_maguro-userdebug
38. cm_mako-userdebug
39. mr1-staging
40. cm_mango-userdebug
41. cm_manta-userdebug
42. cm_mesmerizemtd-userdebug
43. cm_mint-userdebug
44. cm_n7000-userdebug
45. cm_n7100-userdebug
46. cm_n8000-userdebug
47. cm_n8013-userdebug
48. cm_p1c-userdebug
49. cm_p1l-userdebug
50. cm_p1n-userdebug
51. cm_p1-userdebug
52. cm_p3-userdebug
53. cm_p3100-userdebug
54. cm_p3110-userdebug
55. cm_p4-userdebug
56. cm_p4tmo-userdebug
57. cm_p4vzw-userdebug
58. cm_p4wifi-userdebug
59. cm_p5100-userdebug
60. cm_p5110-userdebug
61. cm_p930-userdebug
62. cm_p970-userdebug
63. cm_quincyatt-userdebug
64. cm_quincytmo-userdebug
65. cm_satsuma-userdebug
66. cm_skyrocket-userdebug
67. cm_smultron-userdebug
68. cm_stingray-userdebug
69. cm_su640-userdebug
70. cm_t769-userdebug
71. cm_tf101-userdebug
72. cm_tf201-userdebug
73. cm_tf300t-userdebug
74. cm_tf700t-userdebug
75. cm_toroplus-userdebug
76. cm_toro-userdebug
77. cm_urushi-userdebug
78. cm_vibrantmtd-userdebug
79. cm_ville-userdebug
80. cm_wingray-userdebug
81. pac_anzu-userdebug
82. pac_haida-userdebug
83. pac_mango-userdebug
84. pac_mint-userdebug
85. pac_smultron-userdebug
86. pac_urushi-userdebug
87. pac_zeus-userdebug
88. pac_zeusc-userdebug
89. pac_hercules-userdebug
90. pac_i9100-userdebug
91. pac_i9100g-userdebug
92. pac_quincyatt-userdebug
93. pac_skyrocket-userdebug
94. pac_cooper-userdebug
95. pac_grouper-userdebug
96. pa_crespo-userdebug
97. pa_grouper-userdebug
98. pa_maguro-userdebug
99. pa_toro-userdebug
100. pa_toroplus-userdebug
That shouldn't be a prob coz its just configuring hardware to software and pac is based on cm and aokp and aokp is inturn based on cm so I doubt this part causing problems in the future
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
InfinityFTW said:
I got the pac sources synced an all, and i run envsetup, and I breakfast it, and then i rum make -j4, and it seems to build correctly for some thime, until:
Code:
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.a2dp.default_intermediates/import_includes
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: initialization from incompatible pointer type [enabled by default]
system/core/libpixelflinger/codeflinger/disassem.c:710:1: warning: (near initialization for 'disassemble_di.di_printf') [enabled by default]
target thumb C: libpower <= hardware/libhardware_legacy/power/power.c
target thumb C: audio.primary.default <= hardware/libhardware/modules/audio/audio_hw.c
make: *** No rule to make target `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/lib/libaudioalsa.so', needed by `/home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/LINKED/audio.primary.msm8660.so'. Stop.
make: *** Waiting for unfinished jobs....
Import includes file: /home/android/WORKING_DIRECTORY/out/target/product/pyramid/obj/SHARED_LIBRARIES/audio.primary.msm8660_intermediates/import_includes
Click to expand...
Click to collapse
ok see if the libhardware is working or not means like they patch the hardware to make the rom boot see if anybody has patched it
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
szl.kiev said:
https://github.com/TheMuppets/proprietary_vendor_htc/tree/jellybean
Click to expand...
Click to collapse
Do I curl it into my device repo?
Sent from my GT-P3113 using Tapatalk 2
hey, I followed the tutorial about "Compiling JB on Ubuntu" and I stuck on this error:
Code:
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
Device jlo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Traceback (most recent call last):
File "build/tools/roomservice.py", line 59, in <module>
result = json.loads(urllib2.urlopen(githubreq).read())
File "/usr/lib/python2.7/urllib2.py", line 126, in urlopen
return _opener.open(url, data, timeout)
File "/usr/lib/python2.7/urllib2.py", line 400, in open
response = meth(req, response)
File "/usr/lib/python2.7/urllib2.py", line 513, in http_response
'http', request, response, code, msg, hdrs)
File "/usr/lib/python2.7/urllib2.py", line 438, in error
return self._call_chain(*args)
File "/usr/lib/python2.7/urllib2.py", line 372, in _call_chain
result = func(*args)
File "/usr/lib/python2.7/urllib2.py", line 521, in http_error_default
raise HTTPError(req.get_full_url(), code, msg, hdrs, fp)
urllib2.HTTPError: HTTP Error 403: Forbidden
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
** Don't have a product spec for: 'cm_jlo'
** Do you have the right repo manifest?
I have device tree and proprietary files and admint that I have read whole tutorial 10x times but tip at the and didn't help.
I tried making many changes in files but no result.
I spend hours on doing all those things and like always nothing work, please show me the way I should follow.
lozohcum said:
I have device tree and proprietary files and admint that I have read whole tutorial 10x times but tip at the and didn't help.
I tried making many changes in files but no result.
I spend hours on doing all those things and like always nothing work, please show me the way I should follow.
Click to expand...
Click to collapse
From what I can tell it seems you have an error related to python make sure you have the correct version of python installed for building (Version 2.6.x-2.7.x). If that doesn't work I would suggest reinstalling python and see if they fixes the error. You can also ask about your build error here http://forum.xda-developers.com/showthread.php?t=2059939.
Sent from my SCH-I535 using xda premium
Odp: Stuck on building CM10 for jlo - need tip
Okay I'll reinstall python and write here if it works
now this error:
Code:
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
Device jlo not found. Attempting to retrieve device repository from CyanogenMod Github (http://github.com/CyanogenMod).
Found repository: android_device_sony_jlo
Default revision: cm-10.1
Checking branch info
Default revision cm-10.1 not found in android_device_sony_jlo. Bailing.
Branches found:
jellybean
Use the ROOMSERVICE_BRANCHES environment variable to specify a list of fallback branches.
build/core/product_config.mk:253: *** No matches for product "cm_jlo". Stop.
** Don't have a product spec for: 'cm_jlo'
** Do you have the right repo manifest?
Use jellybean as your branch.
Sent from my SCH-R950 using Tapatalk 2
How to do this? can you explain? I don't know what you mean exacly.
can you give me proper command?
lozohcum said:
How to do this? can you explain? I don't know what you mean exacly.
can you give me proper command?
Click to expand...
Click to collapse
for cm10 repo init -u git://github.com/CyanogenMod/android.git -b jellybean
you had cm10.1 in the error which is still a work in progress
ah I understand, I have downloaded CM10.1 against CM10, so if I download CM10 will it work?
lozohcum said:
ah I understand, I have downloaded CM10.1 against CM10, so if I download CM10 will it work?
Click to expand...
Click to collapse
Yes this should solve your compile error allowing the build to compile successfully unless it runs into another unexpected build error.