Khyber Sen

Could you attach the generated C file it failed on?

My guess is that `csmith.h` is not being resolved correctly. What commands did you use to transpile, were there any warnings, and what `compile_commands.json` did you use (could you paste...

> I just used the online c2rust transpiler. with the default settings Oh, well then it has no way of knowing where and what `csmith.h` is. The online `c2rust transpile`...

Closing this now as it's likely it just couldn't find the `csmith.h` header since it was transpile in the playground. @NobinPegasus, if it's still mis-transpiled locally, you can re-open this...

That C code doesn't compile either, as it declares `void main()` instead of `int main()`. Also, the reason `libc` is not resolved is because you're using `rustc` directly and not...

`c2rust` still generating `#[main]` is a bug, so I'll file an issue for that. It was removed in https://github.com/rust-lang/rust/issues/29634 in 2017.

We should also stop emitting the `#[no_mangle]`s, so I'll file an issue for that, too.

It seems what `c2rust` is generating doesn't even need `#[main]`, so we don't need to do anything else besides remove that feature being used to fix this. That being said,...

I filed issues for the two bugs here: * #678 * #679

> It would not be valid C++, but in C main is allowed to have an implementation defined signature that returns void. So it's merely non-portable C. Ah, I didn't...