Related
I have spent the last to days trying to solve my error setting up sdk on linux mint12. I keep getting this error.
[Qoute]
scott-Presario-CQ62-Notebook-PC scott # apt-get -f installReading package lists... Done
Building dependency tree
Reading state information... Done
Correcting dependencies... Done
The following extra packages will be installed:
libc-bin libc6
Suggested packages:
glibc-doc
The following NEW packages will be installed:
libc-bin
The following packages will be upgraded:
libc6
1 upgraded, 1 newly installed, 0 to remove and 376 not upgraded.
3 not fully installed or removed.
Need to get 0 B/5,143 kB of archives.
After this operation, 3,432 kB of additional disk space will be used.
Do you want to continue [Y/n]? y
Can't exec "locale": No such file or directory at /usr/share/perl5/Debconf/Encoding.pm line 16.
Use of uninitialized value $Debconf::Encoding::charmap in scalar chomp at /usr/share/perl5/Debconf/Encoding.pm line 17.
Preconfiguring packages ...
dpkg: warning: 'ldconfig' not found in PATH or not executable.
dpkg: error: 1 expected program not found in PATH or not executable.
Note: root's PATH should usually contain /usr/local/sbin, /usr/sbin and /sbin.
E: Sub-process /usr/bin/dpkg returned an error code (2)
[Qoute]
I have tried every fix I have found online and all return this exact error. I tried changing the permisons on etc/sudoers to make sure they were right. I also added a these paths.
export PATH={PATH}:/usr/local/sbin:/usr/sbin:/sbin
export PATH={PATH}:/usr/local/bin:/usr/bin:/bin
I have even placed a permission file inside sudoers.d to try to add the path but I just ended up ruining my root access and have to do a complicated fix through my bootloader.but just cant seem to get it to work I am newer to linux and know basic commands but have no idea why I keep getting the same error or how to fix it any help would be deeply appreciated.
Are you running 64 bit? You need to dl the 32 bit lib's
Now it may be cheating, but try Tommytommatoe's android utility it sets up SDK for you and adds everything to your path... It's my go to for stubborn SDK
Sent from my PC36100 using xda premium
Yea it 64bit and I added the 32 bit libs for java but it gives the error when I try that to. I guess I will try that tanks man
Sent from my ADR6425LVW using XDA
Are you using an installer script or something like that?
RoberGalarga said:
Are you using an installer script or something like that?
Click to expand...
Click to collapse
No just piece by piece did java then unpacked SDK in my root dir and update it installed the API and all that then when I try to use adb it says their is no command and all the fixes make the error I described at first.
Sent from my ADR6425LVW using XDA
Ok... you don't need any fixes... you can simply move to platform-tools directory (using command cd /path/to/platform-tools) to can run ./adb command (note: ./adb, not adb).
RoberGalarga said:
Ok... you don't need any fixes... you can simply move to platform-tools directory (using command cd /path/to/platform-tools) to can run ./adb command (note: ./adb, not adb).
Click to expand...
Click to collapse
Really now I feel dumb lol. Guess I'm to used to windows been developing on it for a while. Thanks a lot.
Sent from my ADR6425LVW using XDA
Well thanks for all your help guys I guess I had a bad download of linux so I did a new clean install and setup SDK and apktool and dsixdas kitchen. Now everything works fine. No sudo errors or nothing the good news is with all the trying to fix what was wrong I got used to root being / instead of c:/ so that's a bonus
Sent from my ADR6425LVW using XDA
Good morning from Germany!
I would like to recompile my kernel on the gt-s 5300 device, so that i could install / setup some application and modules.
Basically i would like to enable the usb gadget on this android device, as far as i am informed, a kernel recompile is needed.
i have done a few kernel recompiles for linux systems, but never for a android smartphone.
maybe someone could point me to the right path ?
thanks all for your help!
kind regards
no help ?
no help ?
thanks a lot ...
Self-plug.
http://forum.xda-developers.com/showthread.php?t=1748297
thewadegeek said:
Self-plug.
http://forum.xda-developers.com/showthread.php?t=1748297
Click to expand...
Click to collapse
Hello,
Yes I have read your post - and everything worked fine.
My question now is how to get my own module to be compiled?
I have my sourcecode but not sure where to place the module and what references in which Makefile have to be done ..?
Thanks for your help.
Kind regards
Stock GT-5300 kernel built, but won't boot
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
ric105 said:
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
Click to expand...
Click to collapse
Thanks for bashing my thread...
Might be better to create your own ?
Will do.
samsungkid said:
Thanks for bashing my thread...
Might be better to create your own ?
Click to expand...
Click to collapse
Hadn't seen much traffic on S5300, saw you 'everything worked fine' comment, and thought I might find some tips here.
I will post a separate thread.
Regards
ric105 said:
Hadn't seen much traffic on S5300, saw you 'everything worked fine' comment, and thought I might find some tips here.
I will post a separate thread.
Regards
Click to expand...
Click to collapse
yes please - coz this thread is still open...
waiting for someone to reply for my last questions...
ric105 said:
I've been able to create a zImage from the GT-S5300 open source kernel code, using the bcm21553_cori_04_defconfig as indicated by the accompanying readme file.
However, when I use this kernel to create a boot.img and download using Odin, I get a quick S5300 startup screen, then nothing.
At this point, I'm just trying to build a stock kernel, no modifications. I'm looking for helpful hints on where to find any debug or error messages that will help indicate what is going wrong. I can use Odin to put the prebuilt stock kernel back, and it boots ok once again.
I've compared my boot.img with a stock boot.img (samfirmware sourced), and they are similar in terms of addresses and pagesizes. The ramfs file is also stock, taken from that same stock boot.img. The built kernel is a bit larger than the stock and I'm not sure if I should expect my built kernel to be exactly the same size, or if it's ok for it to be a few KBs different.
Any other parameters or configurations that I might be missing or should check? (And to samsungkid, were there any special steps that you took?)
Thank You!
Click to expand...
Click to collapse
have you checked command line?
Resolved by switching toolchains. OP query remains...
mr.harsh said:
have you checked command line?
Click to expand...
Click to collapse
No errors reported anywhere that I could find, but thanks for the response.
UPDATE: I resolved my original issue: toolchain was wrong. The readme from samsung tried to tell me, but I refused to listen... Once I changed to the Code Sourcery toolchain, the zImage loaded fine.
But back to samsungkid's issue....
I believe he is still trying to get his own custom module compiled into the kernel. I know that building a module separately as an LKM would work technically, but I don't know if that makes sense for the use case.
Regards
cleudde thetical
ric105 said:
No errors reported anywhere that I could find, but thanks for the response.
UPDATE: I resolved my original issue: toolchain was wrong. The readme from samsung tried to tell me, but I refused to listen... Once I changed to the Code Sourcery toolchain, the zImage loaded fine.
But back to samsungkid's issue....
I believe he is still trying to get his own custom module compiled into the kernel. I know that building a module separately as an LKM would work technically, but I don't know if that makes sense for the use case.
Regards
Click to expand...
Click to collapse
Yes, I would be glad if someone could help me with this...
still working on it
Thanks for every information you can give me !
Maybe I need to give you more details, so:
I downloaded the corresponding kernel for my samsung device.
Then I unpacked the file and opened the readme file, which states:
HOW TO BUILD KERNEL 2.6.35 FOR GT-S5300
1. How to Build
- get Toolchain
Visit http://www.codesourcery.com/, download and install Sourcery G++ Lite 2009q3-68 toolchain for ARM EABI.
Extract kernel source and move into the top directory.
$ cd common/
$ make bcm21553_cori_04_defconfig
$ make
2. Output files
- Kernel : kernel/common/arch/arm/boot/zImage
3. How to make .tar binary for downloading into target.
- change current directory to kernel/common/arch/arm/boot
- type following command
$ tar cvf GT-S5300_Kernel_Gingerbread.tar zImage
Click to expand...
Click to collapse
So I downloaded the appropriate toolchain and created my directories under /root/projects/android
[email protected]:~/projects/android# ls
infofiles kernel tarballs toolchain
Click to expand...
Click to collapse
In the directory infofiles are only the readme files from Samsung.
Kernel contains the extracted files from the archives, downloaded from Samsung.
tarballs contain all the tarballs meaning the kernel.tar.gz and the toolchain.tar.gz
toolchain contains the extracted files from toolchain
I then do all the thinks written in the readme file:
[email protected]:~/projects/android# cd kernel/common/
[email protected]:~/projects/android/kernel/common# make bcm21553_cori_04_defconfig
#
# configuration written to .config
#
Click to expand...
Click to collapse
and then I run into an error:
[email protected]:~/projects/android/kernel/common# make
scripts/kconfig/conf -s arch/arm/Kconfig
CHK include/linux/version.h
CHK include/generated/utsrelease.h
make[1]: `include/generated/mach-types.h' is up to date.
CC kernel/bounds.s
arm-eabi-gcc: error trying to exec 'cc1': execvp: No such file or directory
make[1]: *** [kernel/bounds.s] Error 1
make: *** [prepare0] Error 2
Click to expand...
Click to collapse
So could please, anybody help me with me issue?
Thank you !
no one ?
Have you EXPORTed variables to point to the compiler directory?
A guess, but is the error message saying it cannot find the cross compile toolchain? Generally, you need to either export a couple of variables, or add them to the make command line. Something like:
ARCH=arm SUBARCH=arm CROSS_COMPILE= /home/yourhome/toolchains/.../arm-none-eabi- make
Hope it helps.
ric105 said:
A guess, but is the error message saying it cannot find the cross compile toolchain? Generally, you need to either export a couple of variables, or add them to the make command line. Something like:
ARCH=arm SUBARCH=arm CROSS_COMPILE= /home/yourhome/toolchains/.../arm-none-eabi- make
Hope it helps.
Click to expand...
Click to collapse
Thanks.
I added the path to the toolchain directly into the $PATH variable...
Even tried your above statement - the same error again
Maybe need this...
You may need to edit the Makefile:
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?=arm
#this is original ---> CROSS_COMPILE ?=/home/aniruddh/sgy/arm-eabi-4.4.3/bin/arm-eabi-
CROSS_COMPILE ?=/home/your_user_name_here/arm-2009q3/bin/arm-none-eabi-
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
Then you will run 'make' without export any variables.
Regards
tokomotxo said:
You may need to edit the Makefile:
export KBUILD_BUILDHOST := $(SUBARCH)
ARCH ?=arm
#this is original ---> CROSS_COMPILE ?=/home/aniruddh/sgy/arm-eabi-4.4.3/bin/arm-eabi-
CROSS_COMPILE ?=/home/your_user_name_here/arm-2009q3/bin/arm-none-eabi-
CROSS_COMPILE ?= $(CONFIG_CROSS_COMPILE:"%"=%)
Then you will run 'make' without export any variables.
Regards
Click to expand...
Click to collapse
THAT, did the trick!
Thanks a lot for this awesome hint !
I own you
samsungkid said:
THAT, did the trick!
Thanks a lot for this awesome hint !
I own you
Click to expand...
Click to collapse
Thanks to you :good:
tokomotxo said:
Thanks to you :good:
Click to expand...
Click to collapse
Maybe you could answer me another question?
When I want to compile a normal .c program (like a Hello World Program) for my Samsung phone, how would I proceed?
Do I have to write a Makefile for this?
Thanks
Hi all,
I want to port MIUI v5 to the Desire X using patchrom based on deodexed stock ROM. I'm following https://github.com/MiCode/patchrom but am stuck at the ota_target_from_phone because I think packages.xml is missing (the apkcerts.txt is in place, checked that already). I'm getting this in terminal while running the script:
Code:
Run getfilesysteminfo to build filesystem_config.txt
131 KB/s (5572 bytes in 0.041s)
Run getfilesysteminfo and recoverylink.py to recover symlink
File "/home/daniel/patchrom/tools/releasetools/recoverylink.py", line 27
print r"%s isn't exist" % linkfile_path
^
SyntaxError: invalid syntax
Build apkcerts.txt
1704 KB/s (189866 bytes in 0.108s)
File "/home/daniel/patchrom/tools/apkcerts.py", line 16
print "Usage: python ./apkcerts.py path-to-packages.xml path-to-apkcerts.txt"
^
SyntaxError: invalid syntax
Generate metadata used to build target files...
Compress the target_files dir into zip file
/home/daniel/patchrom/desirex
Build full ota package: /home/daniel/patchrom/desirex/stockrom.zip
File "/home/daniel/patchrom/tools/releasetools/ota_from_target_files", line 103
return (info.external_attr >> 16) == 0120777
^
SyntaxError: invalid token
For your info, I didn't use repo to download the files but did a zip download of all needed directories, unpacked and renamed them. Also, I am using Arch Linux, and before you ask, python is installed and android sdk along with platform tools is installed too and added to path. I hope it doesn't matter that I use zsh shell, does it? I modified .zshrc for path. Any ideas / suggestions where to find packages.xml?
Can you work if i give ICS stockrom??/ for miui v4?
Maybe, but I think the problem will still be the same, and I definitely want to do a JB ROM with MIUI v5... What I found now: The ota_target_from_phone script pulls packages.xml from /data/system, so it should be generated by android at some point... I'll have to check and see if it is there. I'll definitely give it a go again tonight...
EDIT: When trying for the first time, I was on hboot 1.25 using Philz Touch recovery for JB hboot compiled by him (the one with incorrect fstab), so maybe that could have been the problem as well...
EDIT 2: Will try with the one fixed by atis112 now...
Tried again now with fixed recovery, didn't make any difference.
But found something: The first error appearing comes from the script "apkcerts.py" which is to be found in the miui patchrom tools directory. The relevant part of the script (the point where it crashes) is:
Code:
if len(sys.argv) != 3:
usage()
sys.exit(1)
And it is called from ota_target_from_phone like this:
Code:
python $TOOL_DIR/apkcerts.py $TARGET_FILES_DIR/packages.xml $META_DIR/apkcerts.txt
The variables are pointing to valid directories. The full scripts can be accessed here:
https://github.com/MiCode/patchrom_tools/blob/ics/apkcerts.py for apkcerts.py and
https://github.com/MiCode/patchrom_tools/blob/ics/releasetools/ota_target_from_phone for the other one.
Ideas?
Bump.
Sent from my HTC Desire X using xda premium
No one really?
So I will have to go for the MIUI forums for help, right?
Sent from my HTC Desire X using xda premium
dansou901 said:
So I will have to go for the MIUI forums for help, right?
Sent from my HTC Desire X using xda premium
Click to expand...
Click to collapse
Yup pretty much MIUI is not supported or respected around here.
So, I've opened a thread in MIUI Germany forum now, can be found here:
http://miui-germany.de/forum2/index.php?page=Thread&threadID=6565
If you still have ideas, you can post them here, too.
Does this MIUI completely work?
It's not even close to finish yet. It will work, but it needs time.
Sent from my HTC Desire X using xda premium
To be continued
Sounds promising =D
Sorry I am unable to find working stock kernel source code, one from http://dl-developer.sonymobile.com/code/copylefts/6.2.A.1.100.tar.bz2 fail to compile at start, so I can not continue, no want to waste my time fixing it since I need excatly the same kernel source which will produce excatly the same binary - stock kernel, probably that will not be happen since sony public source is broken so I can not produce the same binary + later: new modules needed for kexec, sorry guys I stopping now. Our soc going to iritate me a lot
I can just compile it.
Using doomlords prebuilt toolchain
Sent from my C2 using xda app-developers app
nickholtus said:
I can just compile it.
Using doomlords prebuilt toolchain
Sent from my C2 using xda app-developers app
Click to expand...
Click to collapse
Did you tried latest Sony archive? I dont know why but when I "make defconfig" and than do "make" compilation asking me for a lot of defconfig related things - chooses, seems archive from Sony is corupted? Tried riogrande**defconfig, tried allso defconfig which I using, no one working. There asking me for x86 things which is ...no logic
If some one have locked bootloader and have "unlock allowed - no", please give me TA backup! To get TA backup simple install http://www.flashtool.net/download.php and do:
1. install it
2. run it
3. click file menu -> switch to pro
4. click to adwance menu -> trim area -> s1 -> backup
5. post your dump here
Thanks!
You can find many TA backups here.
Gesendet von meinem Xperia S mit Tapatalk
djolivier said:
You can find many TA backups here.
Gesendet von meinem Xperia S mit Tapatalk
Click to expand...
Click to collapse
Missin inposible with ta http://forum.xda-developers.com/showpost.php?p=49958520&postcount=687 only maybe kexec can do a job
Maybe hashcode could help for kexec on locked bootloader. He seems to make it work on several locked device(motorola,latest samsung).
munjeni said:
Sorry I am unable to find working stock kernel source code, one from http://dl-developer.sonymobile.com/code/copylefts/6.2.A.1.100.tar.bz2 fail to compile at start, so I can not continue, no want to waste my time fixing it since I need excatly the same kernel source which will produce excatly the same binary - stock kernel, probably that will not be happen since sony public source is broken so I can not produce the same binary + later: new modules needed for kexec, sorry guys I stopping now. Our soc going to iritate me a lot
Click to expand...
Click to collapse
Sir, I can confirm that its compiling. [TOOLCHAIN- arm-eabi-4.4.3 ] without any changes made in Makefile for now. Which toolchain are you using?
Cheers,
AJ
@munjeni as of now,Xperia U tree and P tree are using ARM-EABI-4.4.3
You can git clone it from here --> www.github.com/Abhinav1997/arm-eabi-4.4-3 and push it over to prebuilts/gcc/linux-x86/arm
So,if you still get errors,modify the toolchain line to : "arm-eabi-4.4.3/bin/arm-eabi-"
Hope it helps
Abhinav2 said:
Sir, I can confirm that its compiling. [TOOLCHAIN- arm-eabi-4.4.3 ] without any changes made in Makefile for now. Which toolchain are you using?
Cheers,
AJ
Click to expand...
Click to collapse
Sorry my wrong :laugh: I executed by this way:
make ARCH=arm CROSS_COMPILE=/root/gitstvari/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- riogrande_lotus_defconfig
make
instead of
make ARCH=arm CROSS_COMPILE=/root/gitstvari/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi- riogrande_lotus_defconfig
make ARCH=arm CROSS_COMPILE=/root/gitstvari/android_prebuilt/linux-x86/toolchain/arm-eabi-4.4.3/bin/arm-eabi-
Ok will continue.
Here is git https://github.com/munjeni/stock_jb_kexec_kernel_for_locked_bootloader/commits/master
lsmod
kexec_load 28179 0 - Live 0x00000000
procfs_rw 2435 0 - Live 0x00000000
Click to expand...
Click to collapse
status
[email protected]:/data/local/tmp # grep kexec_driver /dev/devices
grep kexec_driver /dev/devices
grep: /dev/devices: No such file or directory
2|[email protected]:/data/local/tmp # kexec --load zImage --initrd=initrd.gz --mem-m
in=0x3000000 --command-line="$(cat /proc/cmdline)"
initrd=initrd.gz --mem-min=0x3000000 --command-line="$(cat /proc/cmdline)" <
kernel: 0x401c7008 kernel_size: 35f1f8
kexec_load: entry = 0x3008000 flags = 280000
nr_segments = 3
segment[0].buf = 0xe75090
segment[0].bufsz = 210
segment[0].mem = 0x3001000
segment[0].memsz = 1000
segment[1].buf = 0x401c7008
segment[1].bufsz = 35f1f8
segment[1].mem = 0x3008000
segment[1].memsz = 360000
segment[2].buf = 0x40529008
segment[2].bufsz = 47e538
segment[2].mem = 0x3d7d000
segment[2].memsz = 47f000
kexec_load failed: Function not implemented
entry = 0x3008000 flags = 280000
nr_segments = 3
segment[0].buf = 0xe75090
segment[0].bufsz = 210
segment[0].mem = 0x3001000
segment[0].memsz = 1000
segment[1].buf = 0x401c7008
segment[1].bufsz = 35f1f8
segment[1].mem = 0x3008000
segment[1].memsz = 360000
segment[2].buf = 0x40529008
segment[2].bufsz = 47e538
segment[2].mem = 0x3d7d000
segment[2].memsz = 47f000
255|[email protected]:/data/local/tmp # cat /dev/kexec_driver
Click to expand...
Click to collapse
Progress:
[72371.535949] Kexec: KDS_entry : '3008000'
[72371.535980] Kexec: KDS_nr_segments : '3'
[72371.535980] Kexec: KDS_segment : '1afe8a8'
[72371.535980] Kexec: KDS_kexec_flags : '280004'
[72371.536010] Kexec: - Starting kexec_load...
[72371.599609] Kexec: - ---- kexec_load - result : '0'
[72392.445739] Kexec:-----------------------------------------------------
[72392.445800] Kexec: REBOOT DEVICE !!!
[72392.445953] Starting new kernel
[72392.446044] Bye!
Click to expand...
Click to collapse
Remaining thing is - need to reserve memory for storing hardboot atags, hope I can store them in the same memory like used on my kernel, if not than will investigate something
I wouldn't want to disturb devs working, but I think it would be interesting to follow this.
And btw, if you are still wondering about RCK_H, it's encrypted with unsalted SHA-256 hash
wan5xp said:
Maybe hashcode could help for kexec on locked bootloader. He seems to make it work on several locked device(motorola,latest samsung).
Click to expand...
Click to collapse
Who? Where?
mirhl said:
I wouldn't want to disturb devs working, but I think it would be interesting to follow this.
And btw, if you are still wondering about RCK_H, it's encrypted with unsalted SHA-256 hash
Click to expand...
Click to collapse
Probably some one found something and posted them, but post is deleted http://forum.xda-developers.com/show....php?t=1196932 why?
munjeni said:
Probably some one found something and posted them, but post is deleted http://forum.xda-developers.com/show....php?t=1196932 why?
Click to expand...
Click to collapse
your link was bad
but what posts should have been deleted? Can't see anything wrong
mirhl said:
your link was bad
but what posts should have been deleted? Can't see anything wrong
Click to expand...
Click to collapse
These is copy paste link, so I can not open broken link, tried to append 1196932 to the http://forum.xda-developers.com/newreply.php?do=newreply&p= but thats not link which pointing to the post related to the "arcievied unlock thing"... some one say that there is thread where some guys found unlock procedure for "unlock allowed = no", so I can not see these thread
Hi there,
I have Samsung Galaxy Core Prime LTE and I could not find any custom ROMs so I decided that I will try to compile it myself. I downloaded the LineageOS source code from git (cm 14.1), the device trees and kernel from here: github/MSM8916-Samsung, and the samsung vendor files from the extraxt-files.sh script. The qcom-common files from here: github/CyanogenMod/android_device_samsung_qcom-common. Then I set up the environment (source build/envsetup.sh), ran breakfast and everything went fine. And then came brunch... It's running for about 40-50 minutes, and then stopes because "ninja: build stopped: subcommand failed". Here's the output from my terminal: https:/ /drive.google.com/fi le/d/0Bzbi _UspTWqac3ZkV2RhRjJGeW8/view?usp=drivesdk (remove spaces - sorry for that, but I cannot add links yet)
If the ninja log is needed I will post it.
Can someone help me to understand the code and find out why it is failing?
(I am new to developing stuff, but I have already compiled programs back in the days, and I am familiar with Linux, which is my daily driver)
what version of linux are you using at the moment?
Ubuntu 17.04, but I have also tried it on 16.10 last week, and openjdk-8
wasowski02 said:
Ubuntu 17.04, but I have also tried it on 16.10 last week, and openjdk-8
Click to expand...
Click to collapse
I can't speak for others but I have not had success building anything android on 15.10,16.04,16.10... I always end up on a wild goose chase with all the compiling errors. I have consistently compiled without errors using 14.04 with oracle java 8 as that is what many of the manufacturers are using to make their own builds. If or oracle spits errors with 14.04 i try to use the rule of thumb and thats openjdk-6 and jre for LP, openjdk-7 and jre for MM and openjdk-8 for nougat builds but im only working on MM builds at the moment so your results may vary. Hope this helps a bit, just remember you can use sudo update-alternatives --display java to switch versions on the fly if needed and make sure you incorporate Google prebuilts as well. good luck ?
Sent from my LGLS676 using Tapatalk
Sands207 said:
I can't speak for others but I have not had success building anything android on 15.10,16.04,16.10... I always end up on a wild goose chase with all the compiling errors. I have consistently compiled without errors using 14.04 with oracle java 8 as that is what many of the manufacturers are using to make their own builds. If or oracle spits errors with 14.04 i try to use the rule of thumb and thats openjdk-6 and jre for LP, openjdk-7 and jre for MM and openjdk-8 for nougat builds but im only working on MM builds at the moment so your results may vary. Hope this helps a bit, just remember you can use sudo update-alternatives --display java to switch versions on the fly if needed and make sure you incorporate Google prebuilts as well. good luck ?
Click to expand...
Click to collapse
Then I will try 14.04 and see what happens. Thanks for help
@Sands207 Is there by any chance a site where you can learn to do this? Tutorial for noobs of sort.
Sent from my SM-N920P using Tapatalk
ninja_unmatched said:
@Sands207 Is there by any chance a site where you can learn to do this? Tutorial for noobs of sort.
Click to expand...
Click to collapse
Yes, luckily for us xda members we have our own Android college built right into xda https://forum.xda-developers.com/general/xda-university its a great starting point and rom compiling guide is also there. Its all aimed to help new folks find their way ? jump right in ?
If you need TWRP for it I have it. It was built by blaz3r64, but since AA51 is down I can upload it for you. I can confirm that it works on both the ST Galaxy Core Prime and the Boost Prevail LTE.
Sent from my XT1609 using Tapatalk
RealWelder said:
If you need TWRP for it I have it. It was built by blaz3r64, but since AA51 is down I can upload it for you. I can confirm that it works on both the ST Galaxy Core Prime and the Boost Prevail LTE.
Click to expand...
Click to collapse
So I have already downloaded the official TWRP, but thanks for your interest.
I have tried to compile using ubuntu 14.04 (with openjdk-8) as @Sands207, but I get this error:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d --defines=/home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.h -o /home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.cpp system/tools/aidl/aidl_language_y.yy"
/bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
wasowski02 said:
So I have already downloaded the official TWRP, but thanks for your interest.
I have tried to compile using ubuntu 14.04 (with openjdk-8) as @Sands207, but I get this error:
Code:
FAILED: /bin/bash -c "prebuilts/misc/linux-x86/bison/bison -d --defines=/home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.h -o /home/karol/android/system/out/host/linux-x86/obj/STATIC_LIBRARIES/libaidl-common_intermediates/aidl_language_y.cpp system/tools/aidl/aidl_language_y.yy"
/bin/bash: prebuilts/misc/linux-x86/bison/bison: No such file or directory
Click to expand...
Click to collapse
I recommend trying this keychain as it has full support for what you are attempting https://forum.xda-developers.com/showthread.php?t=3606941 I have tried it myself but Id recommend cleaning your build folder before incorporating them, maybe even a reboot as well. i had forgotten about this but it has far more tools than the normal keychain.
Sent from my LGLS676 using Tapatalk
---------- Post added at 04:29 PM ---------- Previous post was at 04:22 PM ----------
remember to select the right architecture ??
Sent from my LGLS676 using Tapatalk
Sands207 said:
I recommend trying this keychain as it has full support for what you are attempting https://forum.xda-developers.com/showthread.php?t=3606941 I have tried it myself but Id recommend cleaning your build folder before incorporating them, maybe even a reboot as well. i had forgotten about this but it has far more tools than the normal keychain.
Sent from my LGLS676 using Tapatalk
---------- Post added at 04:29 PM ---------- Previous post was at 04:22 PM ----------
remember to select the right architecture ?
Click to expand...
Click to collapse
So I downloaded the new toolchain/keychain/cross compiler (just to make sure - this is the same, yes?), but I cannot find how to choose it to compile android. The official post says:
Code:
# for arm64
export CROSS_COMPILE=$(pwd)/bin/aarch64-linux-gnu-
but as I'm not compiling the kernel I assume it is not what I need (I think) and
Code:
echo $CROSS_COMPILE
does not return anything by default. If I should have used the export function then which file should I choose, because there are many (-strip, -strings, -size, -run, etc.).
There is a directory called toolchain (it contains only binutils) in the folder containing the source code. Should I add a folder called gcc and put the files there? Or maybe I have to run brunch with some options or change an entry in a configuration/make file?
I use the aarch64 version, but not the newest (20170515 not 20170520).
wasowski02 said:
So I downloaded the new toolchain/keychain/cross compiler (just to make sure - this is the same, yes?), but I cannot find how to choose it to compile android. The official post says:
but as I'm not compiling the kernel I assume it is not what I need (I think) and
does not return anything by default. If I should have used the export function then which file should I choose, because there are many (-strip, -strings, -size, -run, etc.).
There is a directory called toolchain (it contains only binutils) in the folder containing the source code. Should I add a folder called gcc and put the files there? Or maybe I have to run brunch with some options or change an entry in a configuration/make file?
I use the aarch64 version, but not the newest (20170515 not 20170520).
Click to expand...
Click to collapse
I do think as you said you will need to run brunch but resetting up your build & source environment to use the new keychain as you attempted to switch from one keychain to the other as well may help if this doesn't work as well take a look at your build configuration. rc file and make sure you don't have double entries or the new keychain missing i usually import the prebuilts i need as I am using arm architecture at the moment but i either download the individual keychain i need and place it in my source folder when i setup my build environment to be added to the build along with my sources before i run lunch because my source folder is untouched by me besides that at that point. I'll be home in an hour or so I'm going to see if i can track down some info to help you get untangled but i do recommend downloading the folder and making a gcc folder with the toolchain folder for arm64 as you said and and adding it to your build ensuring it is clean besides what you need and adding it then attempt to compile again.
I'm not sure if I should use aarch64. I have an armv7-a-neon (so 64-bit) and the internet says that aarch64 and arm64 is pretty much the same, but maybe I am wrong and I should use arm instead. But I think that does not matter until I put the new toolchain both to the aarch64 and arm directory (I guess the compilation process will choose the right one automatically). So I've put the compilers into prebuilts/gcc/linux-x86/... folders, but should I delete the old compilers? And then run the environment setup again (all this stuff starts to make sense to me ?)
Sent from my SM-G360F using Tapatalk
wasowski02 said:
I'm not sure if I should use aarch64. I have an armv7-a-neon (so 64-bit) and the internet says that aarch64 and arm64 is pretty much the same, but maybe I am wrong and I should use arm instead. But I think that does not matter until I put the new toolchain both to the aarch64 and arm directory (I guess the compilation process will choose the right one automatically). So I've put the compilers into prebuilts/gcc/linux-x86/... folders, but should I delete the old compilers? And then run the environment setup again (all this stuff starts to make sense to me )
Sent from my SM-G360F using Tapatalk
Click to expand...
Click to collapse
Yes you should delete the old ones and set up your enviroment again and it should include them. Also yes the compile proccess should pick the correct one in your case as long as you include them and you have, you are heading in the right direction for sure. :good:
Sands207 said:
Yes you should delete the old ones and set up your enviroment again and it should include them. Also yes the compile proccess should pick the correct one in your case as long as you include them and you have, you are heading in the right direction for sure. :good:
Click to expand...
Click to collapse
So I deleted the old ones and I get this error:
Code:
ninja: error: 'prebuilts/gcc/linux-x86/arm/arm-linux-androideabi-4.9/bin/arm-linux-androideabi-strip', needed by '/home/karol/android/system/out/target/product/coreprimeltexx/obj/lib/libdl.so', missing and no known rule to make it
I guess it's because somewhere in a configuration file there is an entry for the old compiler. I have deleted the out directory and played with the envsetup.sh file (about line 210 there is something about compilers),
Code:
# defined in core/config.mk
targetgccversion=
targetgccversion2=
export TARGET_GCC_VERSION=$targetgccversion
# The gcc toolchain does not exists for windows/cygwin. In this case, do not reference it.
export ANDROID_TOOLCHAIN=
export ANDROID_TOOLCHAIN_2ND_ARCH=
local ARCH=$(get_build_var TARGET_ARCH)
case $ARCH in
x86) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin
;;
x86_64) toolchaindir=x86/x86_64-linux-android-$targetgccversion/bin
;;
arm) toolchaindir=arm/arm-linux-androideabi-$targetgccversion/bin
;;
arm64) toolchaindir=aarch64/aarch64-linux-android-$targetgccversion/bin;
toolchaindir2=arm/arm-linux-androideabi-$targetgccversion2/bin
;;
mips|mips64) toolchaindir=mips/mips64el-linux-android-$targetgccversion/bin
;;
*)
echo "Can't find toolchain for unknown architecture: $ARCH"
toolchaindir=xxxxxxxxx
;;
esac
but this did not work either. The ninja files don't contain any gcc configuration. So where can I find the right configuration file? (I can't find the suggested configuration.rc file)
wasowski02 said:
So I deleted the old ones and I get this error:
I guess it's because somewhere in a configuration file there is an entry for the old compiler. I have deleted the out directory and played with the envsetup.sh file (about line 210 there is something about compilers),
but this did not work either. The ninja files don't contain any gcc configuration. So where can I find the right configuration file?
Click to expand...
Click to collapse
I usually compile using clang or maven as I only build AOSP atm https://ninja-build.org/manual.html this page includes directions that should assist you. Do you have maven or clang installed on your linux box?
Sands207 said:
I usually compile using clang or maven as I only build AOSP atm https://ninja-build.org/manual.html this page includes directions that should assist you. Do you have maven or clang installed on your linux box?
Click to expand...
Click to collapse
So it seems that nor klang nor maven is installed on my machine (but as my computer claims ninja is not installed either I guess that they may be installed somewhere in the build directories). Should I try them instead of ninja?
wasowski02 said:
So it seems that nor klang nor maven is installed on my machine (but as my computer claims ninja is not installed either I guess that they may be installed somewhere in the build directories). Should I try them instead of ninja?
Click to expand...
Click to collapse
yes absolutely
Sands207 said:
yes absolutely
Click to expand...
Click to collapse
So what I understand is:
(1) Install maven or clang (let's say clang because I found it in the official ubuntu repository)
(2) Configure brunch to use clang instead of ninja
So I checked the internet if there are any options I can use with brunch to run clang, but I didn't find any. Also looked through the envsetup.sh file, but there is nothing there, or I missed it.
wasowski02 said:
So what I understand is:
(1) Install maven or clang (let's say clang because I found it in the official ubuntu repository)
(2) Configure brunch to use clang instead of ninja
So I checked the internet if there are any options I can use with brunch to run clang, but I didn't find any. Also looked through the envsetup.sh file, but there is nothing there, or I missed it.
Click to expand...
Click to collapse
tonight i will try doing some digging to see if i can help you. im away from my computer right now but ill do what i can. i would try would maven. clang assists with aosp primarily but maven should work for you as far as using a custom command to run maven, log out or reboot after you install it and run brunch as you normally would also please read this https://clang.llvm.org/comparison.html