I have exactly the same issue on OpenSuSe 11.3 64 bit. I too don't want to replace or mess with zlib as it will break many other things which I need for work. Another post I read implied that Google were working on a fix. But I cannot say that for sure or when it would happen.
So cannot help but am also looking for a solution as I cannot develop. On Dec 14, 5:38 pm, jaybradley <[email protected]> wrote: > I have a problem with the platform-tools/aapt on fedora 13 64bit. I've > spent the day searching forums and trying to solve this myself but > couldn't. > > I'm developing in eclipse and using the android developer plugin. > Everything was working well as I worked my way through some tutorials > and then started developing my application. When I added an image > resource to res/layout/main.xml such as: > > <ImageView > android:id="@+id/test_image" > android:src="@drawable/test" > android:layout_width="wrap_content" > android:layout_height="wrap_content" /> > > I got the following error: > > ...../platform-tools/aapt: /lib/libz.so.1: no version information > available (required by ....../platform-tools/aapt) > > The error is also thrown if I run .../platform-tools/aapt from the > command-line. I guessed this was a problem with 64bit versus 32bit > libraries as I'd had to go through the steps of installing some 32bit > libraries when installing the SDK. I followed guides such as: > > https://fedoraproject.org/wiki/User:Hpejakle/Android > > although there are many other similar guides. I have the 32bit and > 64bit zlib libraries installed: > > zlib.i686 1.2.3-23.fc12 > zlib.x86_64 1.2.3-23.fc12 > zlib-devel.i686 > 1.2.3-23.fc12 > zlib-devel.x86_64 > 1.2.3-23.fc12 > > I have tried removing zlib.x86_64 but that has far too many > dependencies to remove. The file does exist: > > ls -l /lib/libz.so.1 > lrwxrwxrwx. 1 root root 13 Nov 2 15:41 /lib/libz.so.1 -> libz.so. > 1.2.3 > > In desperation I tried running the aapt executables I have in ..../ > platforms/android-7/tools/aapt and ..../platforms/android-8/tools/aapt > and they run fine from the command line. If I replace the aapt > executable in ..../platform-tools/aapt with either of the versions I > have in the platforms directory then a clean build in eclipse throws > many errors. > > I've now come to a dead-end after a day of searching and hope someone > has seen this problem before. > > Thank you, Jay -- You received this message because you are subscribed to the Google Groups "Android Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/android-developers?hl=en
