Well, the system is probably simply missing /etc/protocol and/or /etc/services since that's what GLibc does. Did you try copying a version from your Linux machine to a system image to see if this solves the issue ?
On Wed, Jan 20, 2010 at 7:35 AM, Kishor <krish2...@gmail.com> wrote: > Hi David, > > Thanks for your reply. > > I have compiled the client application statically with arm-linux-gcc tool > chain. The executable is linked to glibc statically. > So here when i run the application, glibc part should search the protocol > file in /etc folder? > Does the android not allowing this? Is there any alternative? > The reason behind compiling application statically is that bionic doesn't > support all required function/library. Also for accessing the NFS server the > required services(NFS UTILS, PORTMAP) are compiled statically and running > fine on target. > > > Thanks, > krish > > > > On Wed, Jan 20, 2010 at 5:34 AM, David Turner <di...@android.com> wrote: > >> And /etc/protocols is not supported either. See bionic/libc/bionic/stubs.c >> for the getprotobyname() implementation. >> >> >> On Tue, Jan 19, 2010 at 4:03 PM, David Turner <di...@android.com> wrote: >> >>> /etc/services is not supported in Android. Instead the C library provides >>> a hard-coded list. >>> See bionic/libc/netbsd/net/services.h for the current list, and >>> bionic/libc/tools/genserv.py for a Python script to update it. >>> >>> Hope this helps. >>> >>> On Tue, Jan 19, 2010 at 7:34 AM, krish24 <krish2...@gmail.com> wrote: >>> >>>> Hi All, >>>> >>>> I am running a client application in target which receives the read/ >>>> write request from Modem side. To serve the read/write request for >>>> files, application access the NFS file system(Local NFS). The client >>>> uses the RPC node to receive the Modem read/write request. It access >>>> the NFS file system on Host side through the SUNRPC. >>>> >>>> Issue: When we run the application on target , we receive “127.0.0.1: >>>> RPC: Unknown protocol”. >>>> Here the Client application is calling the “clnt_create” which gets >>>> the handle on a remote host where the local server is located. The >>>> one of the parameter of “clnt_create” is “protocol” and the value of >>>> which is “UDP”. >>>> >>>> I tested the same application at Kernel Level rootfs and it works >>>> fine. There is “protocol” file present in Kernel rootfs /etc folder. >>>> This protocol file contains the list of protocols and the protocol >>>> numbers understood by the IP layer. >>>> >>>> I copied the protocol file in Android rootfs /etc folder but >>>> application still gives the same warning. >>>> >>>> Where i should define the protocols in Android? >>>> Is that warning coming because of protocol file not recognized by >>>> Android or something else needs to be done for setting the NFS on >>>> Android? >>>> >>>> Will appreciate your reply and suggestions. >>>> >>>> Thanks, >>>> krish >>>> >>>> >>>> >>>> -- >>>> 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<android-porting%2bunsubscr...@googlegroups.com> >> website: http://groups.google.com/group/android-porting >> > > > > -- > > -- > 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
