klib | Python library containing a collection of functions | Data Manipulation library

The latter error suggests you to synchronize the Kotlin version you're using and the Ktor version. Check the Recommended kotlinx library versions for details. Probably, you will need to change the Kotlin to 1.5.30, or downgrade the Ktor 1.5.4.

Please comment below with the result. I'll update this answer if something will be still wrong.

This looks like a bug.

Thank you for reporting it to the Kotlin issue tracker. If anyone else encountered this bug, please let us know here: https://youtrack.jetbrains.com/issue/KT-45511. As soon as the ticket is resolved, I'll post an update on this answer.

EDIT: this is a comment from the ticket.

Adding Objective-C super types to a Kotlin object declaration is not supported at the moment. The compiler should, of course, clearly indicate that instead of crashing.
As a workaround, please declare PlatformSpecific as class.

This is a known limitation, described in the Kotlin issue tracker some time ago: KT-39562. Long story short, the cinterop tool does not provide an option to work with source files out-of-the-box. The easiest way here will be to create a framework from your Objective-C code. After that, you'll be able to work with it in a simple way, described in the documentation.

So after some playing around I found the answer.

The dependency was set for a module of iosArm64 which is not available to the iosMain.

I created another folder src/iosArm64Main and placed the source file there. At that point it was able to resolve the library.

Yes, up to len bytes are written to buf.

Normally you'd define this as a function and let the compiler figure out the rest, but if you're implementing it as a macro you need to consider the context.

Remember macros get expanded in the source, so they need to be syntactically valid in the context they appear. Within a function call you can't use ;, so , is used instead as a substitute.

Like this function might be called:

The first __KAVL_INSERT macro is used to declare functions which all start with the same prefix (kavl_insert_) and end with the specified suffix (parameter suf).

So, when you see this:

Could your try following code? The value of i may give you some idea for which file there is a problem.

Unfortunately, you will not be able to compile this code at the moment. It seems like the Javalin framework is not targeting Kotlin/Native, it publishes only for Kotlin/JVM. The only libraries published with K/N in mind will be available to use.
In fact, the problem is that Kotlin flavors are not equivalent internally. They can share pure Kotlin code via common... source sets, but one cannot take a Kotlin/JVM project and just change the target. Kotlin/Native differs from the Kotlin/JVM, both of them are not the same as the Kotlin/JS. To make them work together, an approach named Kotlin/Multiplatform is recommended, see this article.
If you are interested in adapting this code to become multiplatform, consider looking at the Ktor. It provides support of the Kotlin/Native, and you'll be able to partially share code between platforms.