In e7da954 I removed the uint instances from ggml-metal.m. For the rest of the errors, the proposed fix seems invalid since the code does not use types such as u_int or u_char. So there should be some alternative fix for this.

In e7da954 I removed the uint instances from ggml-metal.m. For the rest of the errors, the proposed fix seems invalid since the code does not use types such as u_int or u_char. So there should be some alternative fix for this.

Forgive my PR title btw.. generated.. or edited.. no idea what happened there hah!

What do you mean invalid? sure the code does not use it.. but apple code does. This does not fix anything in this codebase, it fixes issues within Apple codebase sadly. As I explained here The visionOS SDK doesn't include several legacy Unix type definitions that are present in other Apple platforms.
The issue arises because llama.cpp includes some headers apple has forgot to update/fix.

The alternative is waiting apple to fix their own issues, which might take undefined amount of time vs few lines here.

The fix is quite ugly, so I am looking for ways to avoid this. Could you first demonstrate the issue by adding a CI workflow for visionOS that fails? We already have one for tvOS, so I suppose it would not be too difficult to add one for visionOS. After we reproduce the errors, we can reconsider how to fix those.

The fix is quite ugly, so I am looking for ways to avoid this. Could you first demonstrate the issue by adding a CI workflow for visionOS that fails? We already have one for tvOS, so I suppose it would not be too difficult to add one for visionOS. After we reproduce the errors, we can reconsider how to fix those.

Done: #11065

PS: Consider github CI has an ancient version of Vision SDK, but I think the errors will come up nevertheless