|
From: | Roumen Petrov |
Subject: | Re: [bug-gnu-libiconv] Error cross-compiling to Android as shared library |
Date: | Thu, 2 Jul 2020 21:36:22 +0300 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Firefox/60.0 SeaMonkey/2.53.2 |
Bruno Haible wrote:
Hi, Frederik Seiffert wrote:I’m trying to build libiconv as a shared library for Android, but it fails while building libcharset with the following error:/bin/sh ../libtool --mode=install /usr/bin/install -c libcharset.la lib/libcharset.la libtool: install: /usr/bin/install -c .libs/libcharset.so lib/libcharset.so install: .libs/libcharset.so: No such file or directoryBuilding just the static library with --disable-shared works fine, and it looks like the object files are also built fine:$ ls libcharset/lib/.libs/ libcharset.la libcharset.lai localcharset.o relocatable-stub.oDoes anyone know why this might be happening or how to debug this further? I’ve attached the full configure and build log.I haven't been able to create shared libraries even in a native compilation on Android (with libtool).
Interesting. There is no issue to use libtool either with gcc or with clang to build shared library or executable for Android. I don't think that in particular libiconv uses something specific. Never tested such build.
Does the Android NDK mention such a restriction?
We cannot expect such information to be added to Android NDK. Build model is different.
Or is libtool not customized for supporting Android? Does a web search reveal possible adaptations for libtool on Android?
There is no need to change libtool.
Bruno
Roumen
[Prev in Thread] | Current Thread | [Next in Thread] |