Hi,

Userland binaries are linked to Android libc - bionic.
Those are not runnable on standard glibc environemnt.

bionic libraries can be found;
out/target/product/eee_701/system/lib

If you have already installed Android to EeePC or
VMWare, try [ALT]-[F1]. You will be able to play
with a console. [ALT]-[F7] gets you back on Android
GUI.

I got folowing message by executing dalvikvm;
>> # /system/bin/dalvikvm
>> Dalvik VM requires a class name

"no such file" error could happen when a glibc binary
is executed on Android userland.

Hope this help a bit.

On Jan 7, 8:37 pm, Midhun <[email protected]> wrote:
> Hi All,
>
> Following the instructions 
> athttp://groups.google.com/group/android-porting/browse_thread/thread/6...,
> I have built Android for eee_701 successfully on Ubuntu 8.04.
>
> I was trying to run only the Dalvik VM. But I get a strange error from
> bash as follows:
>
> /home/midhun/mydroid > ./out/target/product/eee_701/system/bin/
> dalvikvm
> bash: ./out/target/product/eee_701/system/bin/dalvikvm: No such file
> or directory
>
> The file is present at the specified path.
>
> /home/midhun/mydroid > file ./out/target/product/eee_701/system/bin/
> dalvikvm
> ./out/target/product/eee_701/system/bin/dalvikvm: ELF 32-bit LSB
> executable, Intel 80386, version 1 (SYSV), dynamically linked (uses
> shared libs), not stripped
>
> I expected errors like the one fadden had posted 
> athttp://groups.google.com/group/android-porting/browse_thread/thread/a....
> But rather Ubuntu gives me this strange error. I have tried "exec
> dalvikvm" too - it also gives me the same error.
>
> Any ideas as to how make the dalvikvm run on x86 ? Has anybody tried
> this ?
--~--~---------~--~----~------------~-------~--~----~
unsubscribe: [email protected]
website: http://groups.google.com/group/android-porting
-~----------~----~----~----~------~----~------~--~---

Reply via email to