Hi everyone,
I built again the Android source code using make ARCH=arm
CROSS_COMPILE=arm-crosstool-linux-gnueabi- and 2 hours later it was
completed.
Then i used the directory : mydroid/out/target/product/generic/root as
filesystem for the board (still using NFS)
Then when i boot the board :
I don't think it is going to work that way. You have a different
linker/loader and all that which has to be in specific directories from
root. I think you'll have to do a chroot. That is what I do:
chroot /root /sbin/init
(I've moved init to the more appropriate /sbin directory).
Either
Thanks for your reply. I am not sure I got what you mean.
I have a basic davinci filesystem in which i pasted the Android
filesystem ( davinci filesystem is / and Android fs is in /
filesystem/ ). I did that because if i directly boot the board with
the Android filesystem, I don't come up with
You could try to kick android off in the background by appending an
to the chroot command. Then you could check for messages with dmesg.
Sounds like you may be having linker issues. The compiler should be OK,
but I suspect you aren't compiling for the right architecture. Was this
an s3c2410?
On Thu, 2008-12-11 at 02:23 -0800, FrancoisM wrote:
Oh did I miss something?
[EMAIL PROTECTED]:/filesys# chroot /filesys /sbin/init
chroot /filesys /sbin/init
[2] 993
-bash: /filesys: is a directory
[1] Exit 1 chroot
chroot: too few arguments
Try `chroot
Ok I could chroot successfuly.
[1]+ Segmentation fault chroot /filesys /sbin/init
The result is the same as when I init ed with the run.sh script.
Any suggestion?
On Dec 11, 7:26 pm, Manav Gautama [EMAIL PROTECTED] wrote:
On Thu, 2008-12-11 at 02:23 -0800, FrancoisM wrote:
Oh
It looks like you have a bad binary. Either your compiling for the wrong
architecture or your toolset is using improper instructions.
FrancoisM wrote:
Ok I could chroot successfuly.
[1]+ Segmentation fault chroot /filesys /sbin/init
The result is the same as when I init ed with the
Poke around in bionic/linker. There are some #defines you can use to get
some trace output that might narrow down where it is failing. Another
common failure is TLS when the kernel is compiled to store the TLS in a
register vs. high mem.
FrancoisM wrote:
Oh did I miss something?
I think I used the init file resulting from building the source code
of Android. Of course I built it with the same toolchain (arm-
crosstool-linux-gnueabi). Shall I get it from the emulator instead?
On Dec 11, 8:37 pm, Sean McNeil [EMAIL PROTECTED] wrote:
It looks like you have a bad binary.
Alright, I got some progress.
My previous error comes from my ... wild patching. Later I did it
again smoothly using Meld which is a software I recommend to all of
you guys.
So I got a kernel which boots and is supposed to work with my Android
filesystem, I work with NFS.
I could boot with a
10 matches
Mail list logo
