On Sat, 3 Nov 2018 at 14:09, Bruno Haible <br...@clisp.org> wrote: > Reuben Thomas wrote: > > I'm compiling with clang natively in Termux. All the options are set by > > Termux. __ANDROID_API__ in particular is set by a Termux header that is > > included by most of the system headers, in this case string.h. The -L > > options again are all default. > > And the -L options apparently point to a library that contains mempcpy, > which means an Android API >= 23, although said Termux header defines > __ANDROID_API__ to a value < 23 ? That's an inconsistent setup that would > cause us an inordinate amount of effort to support. >
Thanks. I dug around but neither searching online or in the Termux packaging code reveals how Termux's version of the NDK selects the API level of the libc. (Unless the situation is that there's only one? In which case the solution would be to set `__ANDROID_API__` to match it, as per this issue: https://github.com/termux/termux-packages/issues/2469 ) If you have any knowledge about this it would be good to know! For the moment my workaround is to configure projects with `CPPFLAGS=-D__ANDROID_API__=<MAX-API-SUPPORTED-BY-DEVICE>`. -- https://rrt.sc3d.org
