http://bugzilla.gdcproject.org/show_bug.cgi?id=63
Iain Buclaw changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
http://bugzilla.gdcproject.org/show_bug.cgi?id=63
Timo Sintonen changed:
What|Removed |Added
CC||t.sinto...@luukku.com
--- Comment #5 from
http://bugzilla.gdcproject.org/show_bug.cgi?id=63
--- Comment #4 from Iain Buclaw ---
I think it should now be possible to remove this.
C++ is now *the* boot language for gcc. So by that measure it *must* be
automatically enabled in bootstrapped builds.
Let me test...
--
You are receiving th
http://bugzilla.gdcproject.org/show_bug.cgi?id=63
--- Comment #3 from Iain Buclaw ---
Brad, I can add a --running-autotester switch to the setup-gcc script that
enables this behaviour.
Are you in favour?
--
You are receiving this mail because:
You are watching all bug changes.
http://bugzilla.gdcproject.org/show_bug.cgi?id=63
Ketmar Dark changed:
What|Removed |Added
CC||ket...@ketmar.no-ip.org
--- Comment #2 from
http://bugzilla.gdcproject.org/show_bug.cgi?id=63
--- Comment #1 from Iain Buclaw 2013-06-16 10:28:29
UTC ---
This is gcc configure scripts related. Have tweaked the config-lang.in scripts
so that the dependency on c++ is explicitly as a stage1 language only. However
it looks like the gcc ./co