← Back to context Comment by 201984 2 hours ago https://github.com/anthropics/claudes-c-compiler/issues/1 14 comments 201984 Reply Philpax 2 hours ago The issue is that it's missing the include paths. The compiler itself is fine. krupan 2 hours ago Thank 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. Retr0id 2 hours ago Looks like these users are just missing glibc-devel or equivalent? delusional 2 hours ago Naa, 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. Retr0id 2 hours ago Can confirm (on aarch64 host) $ ./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! 2 replies → zamadatix 2 hours ago Hmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.pngBut yeah, either way it just needs to know where to find the stdlib. 2 replies → worldsavior 2 hours ago AI is the future. suddenlybananas 2 hours ago This is truly incredible. ZeWaka 2 hours ago lol, lmao
krupan 2 hours ago Thank 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.
Retr0id 2 hours ago Looks like these users are just missing glibc-devel or equivalent? delusional 2 hours ago Naa, 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. Retr0id 2 hours ago Can confirm (on aarch64 host) $ ./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! 2 replies → zamadatix 2 hours ago Hmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.pngBut yeah, either way it just needs to know where to find the stdlib. 2 replies →
delusional 2 hours ago Naa, 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. Retr0id 2 hours ago Can confirm (on aarch64 host) $ ./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! 2 replies → zamadatix 2 hours ago Hmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.pngBut yeah, either way it just needs to know where to find the stdlib. 2 replies →
Retr0id 2 hours ago Can confirm (on aarch64 host) $ ./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! 2 replies →
zamadatix 2 hours ago Hmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.pngBut yeah, either way it just needs to know where to find the stdlib. 2 replies →
The issue is that it's missing the include paths. The compiler itself is fine.
Thank 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.
Looks like these users are just missing glibc-devel or equivalent?
Naa, 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.
Can confirm (on aarch64 host)
2 replies →
Hmm, I didn't have to do that. https://i.imgur.com/OAEtgvr.png
But yeah, either way it just needs to know where to find the stdlib.
2 replies →
AI is the future.
This is truly incredible.
lol, lmao