Peter Munch-Ellingsen

The problem here is actually that the right hand side should get checked if it is a C-type and turned into a `c` prefixed type (in this case `clong`).

You have `futharkRebuild` and `opirRebuild` to rebuild the cached files. But looking for `forceBuild` would definitely be a good idea. I think I didn't do it because I couldn't figure...

Hmm, this is a bit weird. So the `uint128t` and `uint128t` should be the same size as what Futhark spits out for those, 16 bytes. I believe the issue might...

That does indeed seem to be the issue. The following test C code: ```c #include #include typedef struct { int64_t a; int64_t b; } fake; typedef struct { __int128 f1;...

Oh, that section is indeed a bit poorly worded. When installing on Linux through your package manager you shouldn't need to give that `passL` flag at all. Simply install libclang...

You could've also done `LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/llvm-10/lib/ nimble install futhark` I believe. This would essentially tell the C compiler that it should also search in that folder for dynamic libraries to load....

Yes the documentation is a bit light for now, the project was released in an early state and I wanted to get some feedback to see if there where anything...

Here is an example of how to wrap libLAS, this is a port of the `apps/bigtest.c` from their repository: ```nim import futhark import terminal, strutils importc: absPath "/usr/lib/clang/12.0.1/include" absPath "/usr/include/liblas/capi/"...

Yes, Futhark only supports C at the moment

> From your example, I do not exactly understand though how it knows that those functions exist. That is the magic of Futhark, you don't have to care how it...