I set up an Ubuntu 14.04 environment. I was able to build Swift, but building the stdlib for Android failed, producing the exact same errors as in the log above.

What could be the difference between 14.04 and 15.10 that's causing this error...? And is the problem in Swift itself, or in our libicu dependency? I'll need to investigate further.

Comment by Adrian Blakij (JIRA)

I have the same issue on a last openSUSE Tumbleweed.

/Applications/Android/SDK/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/arm-linux-androideabi/bin/ld: error: cannot find -licuuc
/Applications/Android/SDK/ndk-bundle/toolchains/arm-linux-androideabi-4.9/prebuilt/linux-x86_64/arm-linux-androideabi/bin/ld: error: cannot find -licui18n

This is the call to the build script in the logs associated to this ticket:

./swift/utils/build-script \
-R \
--android \
--android-ndk /vagrant/android-sdk-linux/ndk-bundle \
--android-api-level 21 \
--android-icu-uc /vagrant/libiconv-libicu-android/armeabi-v7a/libicuuc.so \
--android-icu-uc-include /vagrant/libiconv-libicu-android/armeabi-v7a/icu/source/common \
--android-icu-i18n /vagrant/libiconv-libicu-android/armeabi-v7a/libicui18n.so \
--android-icu-i18n-include /vagrant/libiconv-libicu-android/armeabi-v7a/icu/source/i18n/ \
--android-ndk-gcc-version 4.9

for both icu-uc and icu-i18n the path to the so file instead of the directory location is being passed. That is causing this two library search paths being added to the compilation call:

-L/vagrant/libiconv-libicu-android/armeabi-v7a/libicuuc.so -L/vagrant/libiconv-libicu-android/armeabi-v7a/libicui18n.so

Replacing the path of the file for the directory containing the files should fix this issue. Could you please confirm?

Thanks!

@drodriguez, this can be closed now?

Yes, at some point maybe --android-icu-uc was used as a search path incorrectly, but this days it seems to correctly be used as a full path, or extracting the directory path to use as a library search path.

If anyone is still experiencing this, please reopen or create a new bug with updated reproduction steps and logs.