Re: cannot locate symbol "utext_setup_67"

2020-05-02 Thread Ivan Vučica
> On 2 May 2020, at 18:58, Frederik Seiffert wrote: > > Hi Stefan, > I rebuilt the Android Toolchain with the current state of master today and updated the cmake arguments with "-DANDROID_STL=c++_shared“ according to the examples, but now I’m getting a crash with

Re: cannot locate symbol "utext_setup_67"

2020-05-02 Thread Frederik Seiffert
Hi Stefan, >>> I rebuilt the Android Toolchain with the current state of master today and >>> updated the cmake arguments with "-DANDROID_STL=c++_shared“ according to >>> the examples, but now I’m getting a crash with >>> >>> java.lang.UnsatisfiedLinkError: dlopen failed: cannot locate symbol

Re: cannot locate symbol "utext_setup_67"

2020-05-02 Thread Stefan Pauwels
The README says 'The toolchain automatically downloads and installs the NDK and prebuilt Clang release (via install-ndk.sh)‘. I don’t think it did that when I run ./build.sh (I don’t remember if it did when I initially installed built GNUstep in January. When I try to run ./install-ndk.sh -r

Re: cannot locate symbol "utext_setup_67"

2020-05-02 Thread ste...@pauwels.ch
I run the build.sh script from tools-android, shouldn‘t that have built Gnustep from scratch? It at least compiled for quite a while… > Am 02.05.2020 um 09:38 schrieb Fred Kiefer : > > i am no expert in this area, but my first idea would be that GNUstep base > was build with ICU 67 installed

Re: cannot locate symbol "utext_setup_67"

2020-05-02 Thread Fred Kiefer
i am no expert in this area, but my first idea would be that GNUstep base was build with ICU 67 installed and so this function got used (in the code we just reference text_setup) and now this version cannot be found during linking. On a normal Linux system I would suggest to use ldd on