Vlad Gorlov

Usually you need to **prepend** custom location into PATH variable. Thus, the variant `export PATH=$ANDROID_TOOLCHAIN:$PATH` in most cases is a correct one.

Seems you got this case: > One can engage clang by adjusting PATH to cover same NDK's clang. Just keep in mind that if you miss it, **Configure will try...

btw. Similar issue: https://github.com/openssl/openssl/issues/11192 Maybe you have environment variable "CC" set somewhere?

btw: Another similar issue: https://github.com/openssl/openssl/issues/8941

OK. What command `perl configdata.pm --dump` returns? ```sh cd ToolChain/Sources/ssl/ perl configdata.pm --dump ```

Hm. The file `configdata.pm` even was not generated. Super strange. Well. If the commands below not working, then it is an issue of SSL. Seems would be more effective to...

Interesting. Thank you for the figuring out this issue! The whole idea of NDK symbolic link – is to have "similar path on user side" in "umbrella header" when setting...

Maybe the issue is solved in release https://github.com/vgorloff/swift-everywhere-toolchain/releases/tag/1.0.68. In this release the non-symlinked (absolute paths) to NDK tools were used.

I wasn't used "new concurrency" on Android yet. For example, in this project - https://github.com/vgorloff/swift-everywhere-samples. I conducted few examples on macOS 12 / Xcode 13.1, but not yet used "new...

Building Concurrency example (https://github.com/vgorloff/swift-everywhere-toolchain/commit/645e75d91bcb423a6b349678820bf3cf756a6ebb) gives me the following error: ``` {0}vova@MacBook-Pro:sample-package$ swift-build-arm-linux-androideabi :0: warning: unable to perform implicit import of "_Concurrency" module: no such module found :0: warning: unable to...