copilot-c99: support other C compilers than gcc in test suite

[sternenseemann]

Would probably nice to use whatever $CC is set to in the environment (if it is set) and fall back to gcc otherwise. Currently, it is not possible to execute the test suite on darwin at the moment where the Compiler would be clang.

[ivanperez-keera]

Thanks, @sternenseemann .

I moved this to a discussion until we have a clearer plan of action wrt to what we need to change.

It looks like the offending lines are:

copilot/copilot-c99/tests/Test/Copilot/Compile/C99.hs

Line 777 in 7a379d0

result <- catch (do callProcess "gcc" [ "-c", baseName ++ ".c" ]

copilot/copilot-c99/tests/Test/Copilot/Compile/C99.hs

Line 796 in 7a379d0

result <- catch (do callProcess "gcc" $ [ baseName ++ ".c" ]

Would the right thing to do be to check the env var CC first, use whatever it points to and, if empty, use gcc?

[sternenseemann]

I believe so. Is the result ever executed?

[sternenseemann]

Though -lm is tricky. This is not required for all libc implementation and may fail in some circumstances. The best way to deal with this is doing autoconf style detection. (The easiest way to do everything correctly may actually be adding a configure script, but it would be extreme for just the test suite.)

[ivanperez-keera]

I believe so. Is the result ever executed?

Yes:

copilot/copilot-c99/tests/Test/Copilot/Compile/C99.hs

Lines 168 to 169 in 7a379d0

	r2 <- compileExecutable "main" [ "copilot_test.o" ]
	callProcess "./main" []

[ivanperez-keera]

The best way to deal with this is doing autoconf style detection. (The easiest way to do everything correctly may actually be adding a configure script, but it would be extreme for just the test suite.)

That'd definitely be too much just for this, and not something I'd want to have to do in the tests.