Steffen

This doesn't happen when you do a shallow clone with `git clone --depth 1 ...`, then the version is 7.0.0.0 again instead of 2.8.0.37 (and the configure output states that...

I had the same error when I tested the CI file for the cmake build. I don't remember exactly what thw issue was, but from the top of my head...

@barracuda156 Mmh yeah,I didn't look close enough. I reproduces a similar report with another `std::__1::__libcpp...` symbol, it happens when omitting the `-stdlib=libc++` flag. It is likely that the `ld` command...

And for the first issue, I'd be interested if the error is reproducible with cmake aswell, because in comparison to the make build cmake adds some macOS sdk paths by...

You can have a look [here](https://github.com/imwints/btop-ci/actions/runs/7077283819/job/19261459925) for LLVM I still would try to be verbose about some options, probably ``` LDFLAGS="-stdlib=libc++ -v" ``` and have a look if properly linked...

> for some reason using mismatching SDK That is good to know, I have no experience with macOS at all, I just played around in CI with it and got...

These warnings are really verbose and can be ignored safely. If it still bugs you, you can disable them with `-Wno-unused-command-line-argument`. The same thing happens on FreeBSD and macOS as...

> It was confusing since make asked for gcc 10.1.0 when I used some older version of gcc, so I expected gcc 10.5.0 would be sufficient. The commit introducing ``...

> I did not touch cmake Not tested, but from a quick look over the commit this seems to be the necessary change ```diff diff --git a/CMakeLists.txt b/CMakeLists.txt index 3f8c546..c887149...

@crestfallnatwork What version are you on?