I was getting the same error. Specifying the full path to emulator64-x86 solved it. But 'emulator' command with LD_LIBRARY_PATH is also working when my avd is using intel system image. I suspect 'emulator' automatically selects appropriate architecture depending on the avd's architecture?
On Tuesday, February 19, 2013 2:49:41 PM UTC+5:45, Randy Sugianto wrote: > > Hi Xav, > > I tried to run it using -verbose and I found this difference: > > For emulator: > QEMU options list: > emulator: argv[00] = "/Developer/android-sdk-mac_86/tools/emulator64-x86" > emulator: argv[01] = "-android-hw" > > For emulator-x86: > QEMU options list: > emulator: argv[00] = "emulator-x86" > emulator: argv[01] = "-android-hw" > > > So the solution is apparently just to specify the full path, so instead of > running > emulator-x86 -avd android-16-x86 > I need to run: > /Developer/android-sdk-mac_86/tools/emulator-x86 -avd android-16-x86 > > Thanks for your help! > > I noticed there was also this error: > emulator: ERROR: Could not load OpenGLES emulation library: > dlopen(libOpenglRender.dylib, 1): image not found > emulator: WARNING: Could not initialize OpenglES emulation, using software > renderer. > > > So I need to set the dynlib path, by running it as follows: > LD_LIBRARY_PATH=/Developer/android-sdk-mac_86/tools/lib > /Developer/android-sdk-mac_86/tools/emulator-x86 -verbose -avd > android-16-x86 > > Then it's perfect! Finally we can get a fast emulation in OSX 10.8.2 =) > > > > > > On 19 February 2013 06:41, Xavier Ducrohet <[email protected] <javascript:> > > wrote: > >> Hmm I'm not sure what's going on. >> >> I would try to run both "emulator" and "emulator-x86" with -verbose >> and see the config they both use and how they differ. >> >> On Mon, Feb 11, 2013 at 10:16 PM, Yuku Sugianto <[email protected] >> <javascript:>> wrote: >> > Hi Xavier, >> > >> > Thanks for responding. If I run the emulator with this command: >> > >> > emulator -avd android-16-x86 >> > >> > it works but soon OSX will crash because of HAXM bug. So as you >> suggested, >> > I ran >> > >> > emulator-x86 -avd android-16-x86 >> > >> > but I got an error: >> > >> > qemu: could not load PC BIOS 'bios.bin' >> > >> > Why is it so, is there anything I'm missing? >> > >> > Thanks >> > Yuku >> > >> > >> > On Friday, 8 February 2013, Xavier Ducrohet wrote: >> >> >> >> Instead of running "emulator" just run "emulator-x86" from the command >> >> line. >> >> >> >> "emulator" is just a front end that looks for the ABI of the AVD and >> >> whether the host can do 64 or 32 bit and then calls out >> >> emulator[64]-<ABI> >> >> >> >> On Wed, Feb 6, 2013 at 8:53 PM, yuku <[email protected] <javascript:>> >> wrote: >> >> > The fix appears to be for 32bit emulator only. They said the problems >> >> > when >> >> > running emulator64-x86 is not fixed. How can I force running >> >> > emulator-x86 >> >> > instead of emulator64-x86? (Using macosx 10.8.2) >> >> > >> >> > On Thursday, January 10, 2013 11:21:33 PM UTC+8, Michael Wolfson >> wrote: >> >> >> >> >> >> There is a patch available for running HAXM on 10.8.2 here: >> >> >> >> >> >> >> http://software.intel.com/en-us/articles/intel-hardware-accelerated-execution-manager >> >> >> >> >> >> >> >> >> >> >> >> On Saturday, September 22, 2012 1:24:42 PM UTC-7, Alec Plumb wrote: >> >> >>> >> >> >>> I updated my Mac to 10.8.2 yesterday, and now my Mac immediately >> >> >>> reboots >> >> >>> when I try to launch an x86 emulator with the Intel Hardware >> >> >>> Accelleration >> >> >>> tool installed. If I uninstall the acceleration the emulator runs, >> but >> >> >>> I am >> >> >>> left with a painfully slow emulator. Has anybody else experienced >> this >> >> >>> with >> >> >>> MacOS 10.8.2? >> >> > >> >> > -- >> >> > You received this message because you are subscribed to the Google >> >> > Groups >> >> > "adt-dev" group. >> >> > To unsubscribe from this group and stop receiving emails from it, >> send >> >> > an >> >> > email to [email protected] <javascript:>. >> >> > For more options, visit https://groups.google.com/groups/opt_out. >> >> > >> >> > >> >> >> >> >> >> >> >> -- >> >> Xavier Ducrohet >> >> Android SDK Tech Lead >> >> Google Inc. >> >> http://developer.android.com | http://tools.android.com >> >> >> >> Please do not send me questions directly. Thanks! >> >> >> >> -- >> >> You received this message because you are subscribed to the Google >> Groups >> >> "adt-dev" group. >> >> To unsubscribe from this group and stop receiving emails from it, send >> an >> >> email to [email protected] <javascript:>. >> >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> >> >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "adt-dev" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected] <javascript:>. >> > For more options, visit https://groups.google.com/groups/opt_out. >> > >> > >> >> >> >> -- >> Xavier Ducrohet >> Android SDK Tech Lead >> Google Inc. >> http://developer.android.com | http://tools.android.com >> >> Please do not send me questions directly. Thanks! >> >> -- >> You received this message because you are subscribed to the Google Groups >> "adt-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected] <javascript:>. >> For more options, visit https://groups.google.com/groups/opt_out. >> >> >> > -- You received this message because you are subscribed to the Google Groups "adt-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
