Solved! When I compile the rootfs, I did it with next parameters: make TARGET_ARCH=mips TARGET_ARCH_VERSION=mips32
and the right ones are make TARGET_ARCH=mips TARGET_ARCH_VERSION=mips32r2 Now I can boot in android. 2009/11/18 Carlos Piñeiro <carlosp...@gmail.com> > To built the rootfs, I´ve only downloaded the repo with git, and compiled > it with the toolchain. I´ve compiled if only with make -TARGET_ARCH=mips > > Maybe I need more parameters... Any idea? Could this problem be caused by > mounting the root file system via NFS (rw) ? > Bye, > > > 2009/11/17 Carlospg <carlosp...@gmail.com> > > Hello All, >> >> I´m trying to compile the SDK for mips, but I´m having next error >> while booting the board: >> >> bionic/linker/linker.c:883| ERROR: [ 1292 - failed to extend >> segment from 'libc.so' @ 0x7ef69000 (0x0000a9c0) ] >> bionic/linker/linker.c:1875| ERROR: 1292 could not load 'libc.so' >> bionic/linker/linker.c:1940| ERROR: failed to link /system/bin/sh >> bionic/linker/linker.c:2040| ERROR: CANNOT LINK EXECUTABLE '/system/ >> bin/sh' >> >> >> I´m using the same toolchain, but the ouput files are different in >> the kernel and in the android sdk. >> >> Android file: ELF 32-bit LSB executable, MIPS, version 1, statically >> linked, stripped >> kernel file: ELF 32-bit LSB relocatable, MIPS, MIPS64 version 1 >> (SYSV), not stripped >> >> How can I configure the toolchain to compile a valid root file system? >> >> -- >> unsubscribe: >> android-porting+unsubscr...@googlegroups.com<android-porting%2bunsubscr...@googlegroups.com> >> website: http://groups.google.com/group/android-porting > > > -- unsubscribe: android-porting+unsubscr...@googlegroups.com website: http://groups.google.com/group/android-porting
