Markus Pilman

I run into a similar issue (on macOS). I don't think there's a permission issue. If I run the following command in my project folder, it works just fine: ```rg...

@hlissner this works!! Perfect, thank you so much :)

Using `ld` will increase link times significantly, so I don't like the idea of using that. When using clang and `libc++`, RocksDB and its C++ dependencies also has to be...

The main difference is that we disable RocksDB. Here's our default cmake (it's pretty long mostly because it is generated, not everything here will have an effect): ``` cmake -GNinja...

a relatively simple way of testing my hypothesis would be to add `-DUSE_LIBCXX=OFF`. If you do this everything should use libstdc++ (though this configuration hasn't been used for a long...

The clang build uses libc++ by default. However, the RocksDB build also needs to be told to use this. So basically the logic that compiles RocksDB needs to change so...

RocksDB is built using cmake. I would suggest to use [FetchContent](http://cmake.org/cmake/help/v3.24/module/FetchContent.html) to get the RocksDB source (I think this can be done in a way so it only is downloaded...

yes -- though I think that's what we want. The cleanest solution would be to only set compiler, `stdlib` flags etc in `ConfigureCompiler` and add all other flags to the...

We don't need to. However, we need to use the same `stdlib` for rocks and for fdb. Otherwise we get in trouble. The easiest short-term solution is to compile rocks...

This is what caches are for... So the first time it will take a very long time, but we only need to build these dependencies once (or once per configuration...