▲ Philpax an hour ago | parent | next [-]

The issue is that it's missing the include paths. The compiler itself is fine.

▲ krupan 2 hours ago | parent | prev | next [-]

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 an hour ago | parent | prev | next [-]

Looks like these users are just missing glibc-devel or equivalent?

▲ delusional an hour ago | parent | next [-]

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 an hour ago | parent | next [-]

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 an hour ago | parent [-]

Seems this non-artificial intelligence model just too limited to understand concept of include path.

	▲	dyauspitr an hour ago \| parent [-]
		It’s machine specific

▲ zamadatix an hour ago | parent | prev [-]

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.

▲

Retr0id an hour ago | parent [-]

Probably depends on where your distro puts stuff by default, I think it has a few of the common include paths hardcoded.

	▲	zamadatix an hour ago \| parent [-]
		Makes sense for the behavior.

▲ an hour ago | parent | prev [-]

[deleted]

▲ worldsavior 2 hours ago | parent | prev | next [-]

AI is the future.

▲ suddenlybananas an hour ago | parent | prev | next [-]

This is truly incredible.

▲ ZeWaka an hour ago | parent | prev [-]

lol, lmao