Issam E. Maghni

So, if I understand and want a native x86_64 compiler, you firstly build a cross compiler with `TARGET = x86_64-linux-musl`, then build a native compiler with: `TARGET = x86_64-linux-musl`, `NATIVE...

I want to make a musl-based light distro. So for that, I need a compiler for this distro. Building directly like you said will generate a compiler linked with my...

I think that I resolved the issue. I installed with `make install`, which generated `output-x86_64-linux-musl/`. Then I compiled statically [dash](//git.kernel.org/pub/scm/utils/dash/dash.git) and copied it into `output-x86_64-linux-musl/bin/` as `sh`. Then I chrooted...

From https://gcc.gnu.org/install/configure.html: > If you specify the --with-native-system-header-dir=dirname option then the compiler will search that directory within dirname for native system headers rather than the default /usr/include.

Is there a reason why it’s not yet merged?

I second this. https://github.com/microsoft/TypeScript/blob/master/lib/lib.dom.d.ts#L4133

I find semver-c as project name is way too generic and not enough to pinpoint this project. semver.c is even more problematic. semver-c may also refer to https://github.com/deoxxa/semver-c. Finally, AFAIK,...

Up.

Why not simply add `set(CMAKE_C_STANDARD 99)`, independently of the compiler used ?

Or a simple patch: ```diff diff --git a/Parser/grammar.c b/Parser/grammar.c index 75fd5b9cde..1a4d585026 100644 --- a/Parser/grammar.c +++ b/Parser/grammar.c @@ -33,8 +33,9 @@ freegrammar(grammar *g) { int i; for (i = 0; i...