You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm trying to compile my Julia library with CBinding. However, I cannot get it to compile:
Example:
c`-Wall
c"""
#include <stdlib.h>
"""
It errors with: "fatal error: 'stdlib.h' no such file or directory".
When I compile with verbose output, I notice it's looking for directories belonging to clang 14.0.6, but I only have clang 14.0.4 installed as my default MacOS clang. I installed clang 16 with brew, can I somehow link that?
Thanks in advance.
M1 Mac.
MacOS Ventura 13.4.1
The text was updated successfully, but these errors were encountered:
I'm trying to compile my Julia library with CBinding. However, I cannot get it to compile:
Example:
c`-Wall
c"""
#include <stdlib.h>
"""
It errors with: "fatal error: 'stdlib.h' no such file or directory".
When I compile with verbose output, I notice it's looking for directories belonging to clang 14.0.6, but I only have clang 14.0.4 installed as my default MacOS clang. I installed clang 16 with brew, can I somehow link that?
I am not familiar with how MacOS handles compiler and system resources, but my best guess is that it should be possible to use the -isystem compiler flag when creating your compiler context to provide another location for the compiler infrastructure to find system resources, something like c`-isystem $(systemResourcesIncludeDir) -Wall` in your case. An example of where CBinding is already using the flag is here:
I'm trying to compile my Julia library with CBinding. However, I cannot get it to compile:
Example:
It errors with: "fatal error: 'stdlib.h' no such file or directory".
When I compile with verbose output, I notice it's looking for directories belonging to clang 14.0.6, but I only have clang 14.0.4 installed as my default MacOS clang. I installed clang 16 with brew, can I somehow link that?
Thanks in advance.
M1 Mac.
MacOS Ventura 13.4.1
The text was updated successfully, but these errors were encountered: