/opt/android-sdk/android-sdk-linux_x86-1.6_r1/platform-tools/aapt: /lib32/libz.so.1: no version information available (required by /opt/android-sdk/android-sdk-linux_x86-1.6_r1/platform-tools/aapt) Apparently libz should have VERDEF set. Details are in the link. Please take over the following patch: --- configure.old 2011-02-25 03:03:37.739491008 +0100 +++ configure 2011-02-25 03:03:51.760491008 +0100 @@ -105,8 +105,8 @@ if test "$gcc" -eq 1 && ($cc -c $cflags $test.c) 2>/dev/null; then CC="$cc" - SFLAGS="${CFLAGS--O3} -fPIC" - CFLAGS="${CFLAGS--O3}" + SFLAGS="${CFLAGS--O3} -fPIC -m32" + CFLAGS="${CFLAGS--O3} -m32" if test $build64 -eq 1; then CFLAGS="${CFLAGS} -m64" SFLAGS="${SFLAGS} -m64" Reproducible: Always Steps to Reproduce:
Please attach your emerge --info as a comment to this bug report. How are you trying to build the android-sdk?
Created attachment 264193 [details] emerge --info
So ok, maybe I should explain a bit even though it's just a matter of adding the version info to the lib. The Android SDK you just install via tarballs and then update via the Android manager (i.e. this bug is not about installing). If you then use Eclipse SDK (portage) along with it, then sometimes you'll be getting this error message in the console (Android language console). It's basically a warning because it only is being displayed if you've made some coding errors of your own in the xml files (the aapt tool is like a compiler for the xml files). At that point the whole error log of the aapt tool is printed, including this message. Please check the URL above: http://stackoverflow.com/questions/4567972/error-executing-aapt-all-of-the-sudden/5112927#5112927. This bug is not about the main question, only about this little warning, which apparently can be solved with a patch like stated above. I see no reason why not to solve it. The Android toolset seems to rely on it in some way. Thanks.
The android SDK doesn't contain a configure file - it is a binary distribution. What is this a patch for?
The patch should go on top of sys-libs/zlib-1.2.5. Has nothing to do with Android except that is how I came across this deficiency.
Is this for zlib, or for app-emulation/emul-linux-x86-baselibs ? The libz in question is in /lib32, so unless you're building it yourself you're actually using the 32-bit binary baselibs package.
Okay right, the latter I guess then.
Sorry about the delay. Ok, I've done a little more digging. It seems the issue is that zlib-1.2.3 is stable (and in the 32-bit binary package), and has this issue. zlib-1.2.5 builds with the VERDEF info you want. So, this problem will solve itself when that version of the library goes stable and gets repackaged. Since the 32-bit libs are in a big package, I'm not sure how quickly I'll be able to get that one library updated. I'll go ahead and leave this bug open until we have a fix of some kind, and see what can be done. If it were just a regular library I'd fix this by updating the dependencies accordingly.
Great, that's all I need!
I note that app-emulation/emul-linux-x86-baselibs is now stable and this issue should no longer exist.
Super
