This is a different approach than #7 which involves changes in the spec file (so is more intrusive) but has also some benfits, such as ensure the test program is compiled with the same gcc version of the rest of gc.
~~It also means the gc spec file can no longer be built from scratch in one go since the -tests subpackage build requires gc-devel (which is created in the same spec), ie: it would needs bootstrapping now.~~
With help from @stefw the spec file has been adjusted to drop this issue
This is a different approach than #7 which involves changes in the spec file (so is more intrusive) but has also some benfits, such as ensure the test program is compiled with the same gcc version of the rest of gc.
~~It also means the gc spec file can no longer be built from scratch in one go since the -tests subpackage build requires gc-devel (which is created in the same spec), ie: it would needs bootstrapping now.~~
With help from @stefw the spec file has been adjusted to drop this issue