Thomas Pöchtrager

> It does link an executable though. I'll try 1400 next. That's good enough. It seems they don't care about x86_64h anymore. Maybe we shouldn't either... I mean the only...

> Happens with both ld64 and the new ld. 16.3 updated the LLVM stuff to 1700 so it would be incompatible with tapi 1600. I could try 16.0 (the first...

>FYI you can go here to see the versions, though it doesn't show the ld64 version for Xcode versions after 15.0 (when the new linker was introduced) https://en.wikipedia.org/wiki/Xcode#Toolchain_versions Thanks. Good...

> It does not affect 1600 (back to ~80 ms), so that's good news for the eventual 1700 open sourcing. Great! > Also I believe x86_64h was never really meant...

> For now I'll see if I can maybe fix the bug causing x86_64h issues in 1600 myself That would be great if you could figure out what's causing it....

I think you might have a broken `libdispatch` installation in your system. Can you try what happens when you build the `testing` branch?

Now it seems there is something wrong with your LLVM installation, or the used SDK is broken. Can't say for sure. I'd suggest to reinstall your WSL image. Should be...

It's very likely your `gcc` (`libstdc++`) installation is too old.

It's still using the 6.3.x installation when Clang is searching for the libstdc++ headers as can be seen in the log: > /usr/bin/../lib/gcc/x86_64-linux-gnu/6.3.0/../../../../include/c++/6.3.0/algorithm:62: On Wed, Sep 18, 2024 at 6:40 ...

``` $ wget -O- https://raw.githubusercontent.com/tpoechtrager/cctools-port/refs/heads/lipo-1010.6/lipo/configure 2>/dev/null | head -1 | od -c 0000000 # ! / b i n / s h \n 0000013 ``` For me it says `\n`....