Any way to fix it no rule to make target ?
I've placed toolchains in home folder so i edited makefile in this way ( CROSS_COMPILE ?= /home/gamersab/Toolchains/arm-eabi-4.4.3/bin/arm-eabi- )
Any help ?
P.S I am running 14.04
Kindy find the attached screenshot of terminal.
Thanks
Related
Hi,
when I compile android (using instructions from source.android.com/download) it does not compile some source files. For example there is external/bluetooth/bluez/sbc/sbc.c which is not compiled. There are also other such files.
It's possible those files need not to be compiled. Or it might be that I need some special configuration to compile them.
Either way, if it is possible, I'd like to compile them all. Is there some way to do it? Maybe some "compile_all" make target? Some additional options that need to be set?
(I believe the reason why I want to compile all source files is not important)
Hi ,
enter to the build directory and do
1) " . envsetup.sh " ( you can read this file to get informations about building )
2) after return to the top of directory and make just " m "
tell me what happened
regards
I am using the nightly build of CM for galaxy s2 I-9100. I can compile and install from recovery to my phone, but I need to compile the /driver/usb/serial/ftdi_sio.c driver file into a .ko file that I can insmod into the kernel.
I have tried compiling with make modules ARCH=arm CROSS_COMPILER=..../arm-eabi-
It compiles for the wrong kernel.
I want to use the mm() function from . build/envsetup.sh. However I don't know how to setup the Android.mk file.
Does anyone know how to alter the properties of the CM9 mod so that it compiles the ftdi_sio driver dynamically or statically for the kernel?
I am trying to connect a FTDI usb-to-serial chip to the S2 in order to control an arduino custom board.
All help will be greatly appreciated.
Edit: I have tryed the "make menuconfig" and set the ftdi-sio.c to be a module, but ". build/envsetup.sh" and "mm()" seem to ignore it. Are they using a different .config file that is located elsewhere?
sddimitrov said:
I am using the nightly build of CM for galaxy s2 I-9100. I can compile and install from recovery to my phone, but I need to compile the /driver/usb/serial/ftdi_sio.c driver file into a .ko file that I can insmod into the kernel.
I have tried compiling with make modules ARCH=arm CROSS_COMPILER=..../arm-eabi-
It compiles for the wrong kernel.
I want to use the mm() function from . build/envsetup.sh. However I don't know how to setup the Android.mk file.
Does anyone know how to alter the properties of the CM9 mod so that it compiles the ftdi_sio driver dynamically or statically for the kernel?
I am trying to connect a FTDI usb-to-serial chip to the S2 in order to control an arduino custom board.
All help will be greatly appreciated.
Click to expand...
Click to collapse
I build modules like this
Code:
cd ~/Android/Build/kernel-msm
ARCH=arm CROSS_COMPILE=~/Android/Build/prebuilt/linux-x86/toolchain/arm-eabi-4.4.0/bin/arm-eabi- make menuconfig
Then when menuconfig comes, search module and instead of Y or N, press M and then save. It will build .ko file.
Are you electronical engineer?. Nice to see some people like me here .
Btw, if you can get arduino any wireless communication between arduino and Android, it will be so cool (I did some time ago with BT).
Cyanogen uses different kernel
:Yes I am an EE at UCLA
I tried changing the menuconfig. When I set it in
Code:
~/android/system/kernel/samsung/smdk4210$ make menuconfig ARCH=arm CROSS_COMPILER=/opt/arm-eabi-
It changes the ftdi_sio to be a module, but then
Code:
. build/envsetup samsung kernel
it ignores that .config file
If I change the .config in
Code:
~/android/system/kernel/samsung/smdk4210/build/galaxys2/
and then run the cyanogenmod build command, it resets my config file.
Compiling using
Code:
~/android/system/kernel/samsung/smdk4210$ make SUBDIRS=drivers/usb/serial ARCH=arm CROSS_COMPILER=opt/toolchains/arm-eabi-4.4.3/bin/arm-eabi-
Compiles the modules, but when I try to
Code:
insmod ftdi_sio.ko
I get
Code:
ftdi_sio: version magic '3.0.15+ mod_unload modversions ARMv5 ' should be '3.0.15-CM-ge1bddfe-dirty SMP preempt mod_unload ARMv7 p2v8 '
I also get this warning when I compile them using make
Code:
WARNING: Symbol version dump /home/stoyan/android/system/kernel/samsung/smdk4210/Module.symvers
is missing; modules will have no dependencies and modversions.
How do I compile this module right? Any suggestions?
sddimitrov said:
Compiles the modules, but when I try to
Code:
insmod ftdi_sio.ko
I get
Code:
ftdi_sio: version magic '3.0.15+ mod_unload modversions ARMv5 ' should be '3.0.15-CM-ge1bddfe-dirty SMP preempt mod_unload ARMv7 p2v8 '
Click to expand...
Click to collapse
Edit scripts/setlocalversion
Find the following lines :
Code:
# running further git commands
if $short; then
echo "+"
return
fi
Change the line - echo "+" to echo ""
Now edit your .config file
Find CONFIG_LOCALVERSION
Change to CONFIG_LOCALVERSION="-CM-ge1bddfe-dirty"
ARMv5 ? Try with this toolchain https sourcery.mentor dot com/sgpp/lite/arm/portal/release2032 ( sorry i can't post link )
Hope this will help.
Hi my name is ashy and I need some help regarding building a kernel from source for an ongoing project called H1droid here: h**p://samsungi8320.freeforums.org/portal.php
Basically I am just getting into this kind of stuff and at best Iam a hacker and a modder not a developer, so Linux is pretty new to me. However I learn fast and have a good grasp on what's what.
I am trying to build the Kernel for this project from this source h**p://samsungi8320.freeforums.org/onenand-mtd-multiboot-recovery-cm7-2rc1-t765.html
These sources were created originally by R3D4 who doesn't come to our fourms any more, so I am here to ask for help.
In a nut shell I am trying to build the kernel from R3D4's sources. I have Ubuntu, the tool chains, cloned the source and have managed to build the kernel. The problem is that the kernel requires to be in uImage format with built in ramdisk, however for the life of me I can't figure out how to create the valid boot.img..
I have pulled the config file from the device to use as the default .config, and haven't changed anything in menuconfig when compiling.
I have tried flashing the resulting image to the device, but it doesn't boot at all. It seems that there is no ramdisk to boot a rootfs.
I notice in .config it expects an initramfs to be in a specified directory, however my problem is I have no idea how to create the initramfs to build into the kernel when compiling.
This is probably something easy, but I have searched and searched and can't figure it out, so I am asking here for someone who has the knowledge if they can guide me in the right direction as to how to build the initramfs into the kernel and then compile it as a boot.img to flash via recovery.
I appreciate any and all help.
Thanks, ashy
Please help!
Update: I have managed to compile the kernel with built in initramfs, however the phone still doesn't boot.
Can anybody help here I'm stumped. Iam using Ubuntu 11.10 in VMware and these are the steps I have taken:
1. Clone sources as in first post
2. copy initramfs files into directory specified in config file: CONFIG_INITRAMFS_SOURCE="../out/target/product/nowplus/root"
2. Open terminal in Kernel directory
3. use command: make ARCH=arm nowplus_defconfig (this is the config file from the phone)
4. start the build of the kernel: make ARCH=arm CROSS_COMPILE=/home/user/cm7/arm-2012.03/bin/arm-none-eabi- uImage
During the compile there are warnings regarding unused variables or something, but believe these are normal. However at the end of the build modpost reports: WARNING: modpost: Found 2 section mismatch(es).
Is this significant?
Could really do with some help here, I am new at this stuff and getting really frustrated as I've been at it for 2 weeks now. I have searched and searched the whole internet for an answer.
ashyx said:
Update: I have managed to compile the kernel with built in initramfs, however the phone still doesn't boot.
Can anybody help here I'm stumped. Iam using Ubuntu 11.10 in VMware and these are the steps I have taken:
1. Clone sources as in first post
2. copy initramfs files into directory specified in config file: CONFIG_INITRAMFS_SOURCE="../out/target/product/nowplus/root"
2. Open terminal in Kernel directory
3. use command: make ARCH=arm nowplus_defconfig (this is the config file from the phone)
4. start the build of the kernel: make ARCH=arm CROSS_COMPILE=/home/user/cm7/arm-2012.03/bin/arm-none-eabi- uImage
During the compile there are warnings regarding unused variables or something, but believe these are normal. However at the end of the build modpost reports: WARNING: modpost: Found 2 section mismatch(es).
Is this significant?
Could really do with some help here, I am new at this stuff and getting really frustrated as I've been at it for 2 weeks now. I have searched and searched the whole internet for an answer.
Click to expand...
Click to collapse
Ok have managed to make a little progress, it seems the rootfs is loading as it boots up to a screen with blue A N D R O I D text and then changes to a flashing cursor in the top left of the screen. I guess this means the kernel isn't booting.
Still looking for pointers out there on this, can nobody give me a hint or a way to debug this problem?
ashyx said:
Ok have managed to make a little progress, it seems the rootfs is loading as it boots up to a screen with blue A N D R O I D text and then changes to a flashing cursor in the top left of the screen. I guess this means the kernel isn't booting.
Still looking for pointers out there on this, can nobody give me a hint or a way to debug this problem?
Click to expand...
Click to collapse
Hey, like you i'm an user which enjoy to experiment stuff with linux, so, i want just thank you to share your experience, it helped me
Hi Folks
Here's a native Bonic GNU GCC ( 4.6.0 ) + BinUtils ( 2.22 ) compiled for armv7-a with c and c++ support!
Testing:
I used an HTC Sensation running CM9 for testing
[EDIT:] Using JB 4.2.1 on a Nexus 7 causes a segmentation fault when trying to compile...... Investigation Continues!
Installing:
Download and unpack this archive [ bionic_gcc_binutils.7z ]
copy the directories to the /system directory ,
adb push whilst in the directory you extracted the download to should do the trick
adb push . /system
Test the gcc
Code:
adb shell gcc /system/usr/src/hello.c -o /system/bin/hello
adb shell hello
HELLO OUTPUT: Hello Bionic
Check the Dynamic Linker
Code:
adb shell readelf -l /system/bin/hello | grep 'linker'
OUTPUT: [Requesting program interpreter: /system/bin/linker]
The GNU linker - ld
ld currently only has one search path by default, that is /system/lib, you must manually set links to other location ( i.e /vendor/lib )
Getting Help - RTFM ( Read The F***king Manual )
No seriously the man and info pages can be found in the share directory in the archive
Personal Thoughts
Although GCC is a very mature project, I'd still consider this as PRE-ALPHA R&D as I'm certainly not an expert when it comes to toolchains etc. I basically used a bruteforce attack to build this. which involves compile - test - tweak/fix - rinse - repeat and stop when it looks about right So I could have quite easily misconfigured a compiler flag or patch a file in an inappropriate manner which may manifest itself further down the line.
I suppose the acid test would be to try and compile the linux kernel using this toolchain.
I had a search around to see if this had already been covered, It looks like the C4Droid project has it covered, at a cost!! but I do see the question on native compilation come up every now and again so hopefully this should help some folks out at least.
I'm curious, although this is old by now, what CFLAGS (and other environment variable settings) and configure options did you use in order to get that to compile? I've messed around with gcc 4.9.1 and binutils 2.24 using the android toolchain from NDK version r9d, and haven't had any luck.
jdmanley87 said:
I'm curious, although this is old by now, what CFLAGS (and other environment variable settings) and configure options did you use in order to get that to compile? I've messed around with gcc 4.9.1 and binutils 2.24 using the android toolchain from NDK version r9d, and haven't had any luck.
Click to expand...
Click to collapse
Are you still curious about this? I did this just recently and it took quite a while to find the right configurations and flags.
I'd be happy to post the output of 'gcc -v' or show what config parameters I used
Surge1223 said:
Are you still curious about this? I did this just recently and it took quite a while to find the right configurations and flags.
I'd be happy to post the output of 'gcc -v' or show what config parameters I used
Click to expand...
Click to collapse
please share
Hi. I need your help.
Because I need to modify the cost of each instruction, I'm doing a compilation with linaro gcc source code.
Until now I use gcc-linaro-4.7-2013.04 which is in the linaro-toolchain-binaries 4.7 package(linaro hompage-Download-
Binaries-linaro-toolchain-binaries 4.7), and I didn't change anything yet.
I compiled with configure below.
Code:
./configure --prefix=/home/kynic0/workspace/linaro-gcc-built --target=arm-none-eabi
There is an error like this.
Code:
configure:3602: error: in `/home/kynic0/workspace/gcc-linaro-4.7-2013.04/arm-none-eabi/libgcc':
configure:3605: error: cannot compute suffix of object files: cannot compile
See `config.log' for more details.
It is the contents in config.log file.
I tried re-downloading the source file, compiling several times, cleaning prefixed directory, but I really don't know what is problem.
Some people said that GDB is problem, but I can't catch the right way to solve it.
Please help this n00b.
I attached the log file.