Does Android Studio need multilib?

moisespedro · 09-17-2014, 10:30 PM

Hi, I am setting up an Android development environment. I've installed jdk (using the official java Slackbuild) and I am running Slackware64 14.1.

While creating my first project I noticed an error. The terminal output gives me this:

Code:

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:mergeDebugResources'.
> Error: Failed to run command:
        /home/pedro/android-studio/sdk/build-tools/android-4.4W/aapt s -i /home/pedro/AndroidStudioProjects/SimMoto/app/build/intermediates/exploded-aar/com.android.support/appcompat-v7/20.0.0/res/drawable-xxhdpi/abc_menu_dropdown_panel_holo_light.9.png -o /home/pedro/AndroidStudioProjects/SimMoto/app/build/intermediates/res/debug/drawable-xxhdpi-v4/abc_menu_dropdown_panel_holo_light.9.png
  Error Code:
        127
  Output:
        /home/pedro/android-studio/sdk/build-tools/android-4.4W/aapt: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory

I searched for "librt.so.1" and was reported as being part of glibc. Does that mean I need multilib? I've seen some people saying that, but they were just talking about android development in general, didn't see they mentioning Android Studio.

Another unrelated question: does anyone else here use it? Did you notice it being really sluggish?

EDIT: Same error while running adb

Code:

/home/pedro/android-studio/sdk/platform-tools/adb: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory
12:31:29 E/adb: Failed to parse the output of 'adb version':
Standard Output was:

Error Output was:
/home/pedro/android-studio/sdk/platform-tools/adb: error while loading shared libraries: librt.so.1: cannot open shared object file: No such file or directory

aaditya · 09-17-2014, 11:50 PM

adb does require multilib I think (as android is x86).

Code:

$ file -L adb
adb: ELF 32-bit LSB  executable, Intel 80386, version 1 (SYSV), dynamically linked (uses shared libs), not stripped

What I did was add Alien Bob's multilib repo to slackpkg+, and then installed a very limited set of packages, such that adb works (no wine or games would work with this setup though).

Code:

$ slackpkg search multilib | grep -w installed
   installed           multilib                     gcc-4.8.2_multilib-x86_64-1alien          
   installed           multilib                     gcc-g++-4.8.2_multilib-x86_64-1alien      
   installed           multilib                     glibc-2.17_multilib-x86_64-7alien         
   installed           multilib                     glibc-i18n-2.17_multilib-x86_64-7alien    
   installed           multilib                     glibc-profile-2.17_multilib-x86_64-7alien  
   installed           multilib                     glibc-solibs-2.17_multilib-x86_64-7alien  
   installed           multilib                     glibc-zoneinfo-2013d_multilib-noarch-7alien

Code:

$ ./adb 
Android Debug Bridge version 1.0.31

 -a                            - directs adb to listen on all interfaces for a connection
 -d                            - directs command to the only connected USB device
                                 returns an error if more than one USB device is present.
 -e                            - directs command to the only running emulator.
...
...

Multilib link: http://docs.slackware.com/slackware:multilib