13 Mar
2013
13 Mar
'13
8:49 p.m.
Further to bug #992124 <RFE: clang support> [1], is there any reason why we still have a hardcoded check for gcc >= 3.0 in the configure script?
1. It prevents easy use of non-gcc compilers (clang)
2. Version 3.0 is archaic, and is presumably available on every platform that could feasibly build Inkscape (i.e., other infrastructure checks in the configure script would fail, so the test is redundant)
3. Why are we specifically looking for version 3.0? If we're wanting to check for a compiler feature, there are more elegant ways of checking for this than just looking for the version number.
If no one objects, I'll remove the version check.
Best wishes,
Alex