It works! thanks.
On 01/26/2011 06:00 PM, Xavier Ducrohet wrote:
> Download tools r9.
>
> Xav
>
> On Wed, Jan 26, 2011 at 6:56 PM, jam wrote:
>> BUMP
>>
>> glibc 2.10 here also.. I suppose I can create a chroot with new glibc.. :/
>>
>> --
>> You received this message because you are subscribed
because you build with 32bit system, you can delete the
prebuilt/linux-x86/toolchain/arm-eabi-4.4.3 directory,and create a link
named arm-eabi-4.4.3 link to arm-eabi-4.4.0
2011/1/27 Xavier Ducrohet
> Download tools r9.
>
> Xav
>
> On Wed, Jan 26, 2011 at 6:56 PM, jam wrote:
> > BUMP
> >
> > gli
Download tools r9.
Xav
On Wed, Jan 26, 2011 at 6:56 PM, jam wrote:
> BUMP
>
> glibc 2.10 here also.. I suppose I can create a chroot with new glibc.. :/
>
> --
> You received this message because you are subscribed to the Google
> Groups "Android Developers" group.
> To post to this group, send
BUMP
glibc 2.10 here also.. I suppose I can create a chroot with new glibc.. :/
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group, send email to android-developers@googlegroups.com
To unsubscribe from this group, send e
Can we please get this re-released linked against libc6 <= 2.10? Many
folks may be working off systems they can't upgrade or don't want to
risk upgrading.
Regards,
Ben
--
You received this message because you are subscribed to the Google
Groups "Android Developers" group.
To post to this group,
The work around may work for some folks, but certainly there are
people who can't, or don't want to risk, upgrade their machines. Can
we get this re-released linked against glibc6 <= 2.10 please?
-Ben
On Dec 7 2010, 11:20 pm, DrBrain wrote:
> Just found a work-around solution:
> 1. Add this repo
I have the same issue on OpenSuse 11.2 32-bit. There is a similar
issue with aapt, although it manages to run just fine despite the
alarming error message.
~/android/sdk> rpm -q glibc zlib
glibc-2.10.1-10.9.1.i686
zlib-1.2.3-140.2.i586
~/android/sdk> ldd tools/emulator platform-tools/aapt
tools/e
I am also getting same errorany solution please
On Dec 6, 4:27 pm, elpix1 wrote:
> Hi,
>
> I updated the SDK for the Android 2.3 and the emulator is not
> running anymore because it needs GLIBC 2.11 and my
> system has 2.10 !
> It seems that the emulator is the only tool from the new
> SDK th
I am also getting same error...any solution?? please
On Dec 6, 4:27 pm, elpix1 wrote:
> Hi,
>
> I updated the SDK for the Android 2.3 and the emulator is not
> running anymore because it needs GLIBC 2.11 and my
> system has 2.10 !
> It seems that the emulator is the only tool from the new
> S
Hi DrBrain ,
Thanks, its working fine for me.
Appreciate you reply.
Now Eclipse able to launch emulator.
--
Atul Raut, Yavatmal, MH, India
Android Telephony Engineer
ht
Just found a work-around solution:
1. Add this repository: "deb http://security.ubuntu.com/ubuntu lucid-
security main" to software sources (/etc/apt/sources.list)
2. Start update aptitude: sudo apt-get update
3. Start update libc6: sudo apt-get install libc6
Best Regards.
On Dec 8, 11:07 am, jto
Found out the QA machines at Android were upgraded to Lucid so they
didn't catch the glibc thing. They are hoping to issue a fix.
On Dec 7, 2:22 pm, jtoolsdev wrote:
> Same here on Ubuntu 9.10. Hoses any development until there is a
> solution. Looking at reported 2.3 errors popping developers
Same here on Ubuntu 9.10. Hoses any development until there is a
solution. Looking at reported 2.3 errors popping developers may want
to wait to update.
On Dec 7, 6:56 am, Fred J wrote:
> Same error on (Mandriva release 2010)
>
> On 6 déc, 22:27, elpix1 wrote:
>
> > Hi,
>
> > I updated the SDK
Same error on (Mandriva release 2010)
On 6 déc, 22:27, elpix1 wrote:
> Hi,
>
> I updated the SDK for the Android 2.3 and the emulator is not
> running anymore because it needs GLIBC 2.11 and my
> system has 2.10 !
> It seems that the emulator is the only tool from the new
> SDK that requires 2.11
14 matches
Mail list logo
