← Back to context Comment by Retr0id 5 hours ago Looks like these users are just missing glibc-devel or equivalent? 8 comments Retr0id Reply delusional 5 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 5 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! u8080 5 hours ago Seems this non-artificial intelligence model just too limited to understand concept of include path. 1 reply → zamadatix 5 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. Retr0id 5 hours ago Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded. 1 reply →
delusional 5 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 5 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! u8080 5 hours ago Seems this non-artificial intelligence model just too limited to understand concept of include path. 1 reply → zamadatix 5 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. Retr0id 5 hours ago Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded. 1 reply →
Retr0id 5 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! u8080 5 hours ago Seems this non-artificial intelligence model just too limited to understand concept of include path. 1 reply →
u8080 5 hours ago Seems this non-artificial intelligence model just too limited to understand concept of include path. 1 reply →
zamadatix 5 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. Retr0id 5 hours ago Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded. 1 reply →
Retr0id 5 hours ago Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded. 1 reply →
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)
Seems this non-artificial intelligence model just too limited to understand concept of include path.
1 reply →
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.
Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded.
1 reply →