it is in libgcc.a, provided by the toolchain. I guess you are not building the binary with the Android toolchain. If this is the case, don't expect your code to run except by pure luck (unless you statically link to GLibc)
On Fri, Jan 23, 2009 at 1:15 AM, pavan savoy <[email protected]> wrote: > Yeah, > > I got a __fswab undefined reference error I suppose, which is basically > byte shifiting operator in bionic, but somehow was unable to refer it, > probably in libc_common, > > How did you resolve that ? > > regards, > Pavan > > > On Fri, Jan 23, 2009 at 2:31 PM, pavan savoy <[email protected]>wrote: > >> try doing a stop media >> and stop mediaserver. >> >> and by the way, how did you get aplay working ? >> I got some undefined errors .... got the speaker-test working but not >> aplay .... >> >> regards, >> Pavan >> >> >> On Fri, Jan 23, 2009 at 2:06 PM, AJAY <[email protected]> wrote: >> >>> >>> Hi All, >>> >>> I have integrated ALSA lib , alsa_sound and Alsa utils for my ARM 9 >>> Target board. However after booting Android on the target I am unable >>> to use aplay as it give the following error. >>> >>> aplay: main:566: audio open error: Device or resource busy >>> >>> It seems like the ALSA is being used currently by Audio Flinger. >>> Can I disable it somehow ? >>> >>> >>> Can any one suggest me a work around to test sound on ALSA Android >>> framework . >>> >>> >>> Thanks, >>> Ajay >>> >>> >>> >> > > > > --~--~---------~--~----~------------~-------~--~----~ unsubscribe: [email protected] website: http://groups.google.com/group/android-porting -~----------~----~----~----~------~----~------~--~---
