The issue is that it's missing the include paths. The compiler itself is fine.
replyThank you. That was a long article that started with a claim that was backed up by no proof, dismissing it as not the most interesting thing they were talking about when in fact it's the baseline of the whole discussion.
replyLooks like these users are just missing glibc-devel or equivalent?
replyNaa, it looks like it's failing to include the standard system include directories. If you take then from gcc and pass them as -I, it'll compile.
replyCan confirm (on aarch64 host)
reply $ ./target/release/ccc-arm -I /usr/include/ -I /usr/local/include/ -I /usr/lib/gcc/aarch64-redhat-linux/15/include/ -o hello hello.c
$ ./hello
Hello from CCC!Seems this non-artificial intelligence model just too limited to understand concept of include path.
replyIt’s machine specific
replyHmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.png
reply
But yeah, either way it just needs to know where to find the stdlib.
Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded.
replyMakes sense for the behavior.
replydeleted
replyAI is the future.
replyThis is truly incredible.
replylol, lmao
reply