Community
Participate
Working Groups
It appears that Internal Builder is unable to run gcc directly due to gcc/g++ being cygwin links to elsewhere. This is not a problem for External Builder as it uses cygwin make which handles the links. Note that we use a workaround calling gcc via shell for scanner discovery, see bug 218444.
*** Bug 367340 has been marked as a duplicate of this bug. ***
*** Bug 277833 has been marked as a duplicate of this bug. ***
Fixed on master.
*** cdt git genie on behalf of Andrew Gvozdev *** bug 364733: Internal Builder does not work with Cygwin toolchain [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=dc01366f97a94046176447c2b7be076d72e1d3b0
*** Bug 364740 has been marked as a duplicate of this bug. ***
Reopen to fix ParallelBuilder (ProcessLauncher)
*** cdt git genie on behalf of Andrew Gvozdev *** bug 364733: Fixed problem with not picking environment correctly [*] http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/commit/?id=13ab9fa3c4b556defbc3dbe4605a7828f664bb6e
Opened a separate bug 384518 for Parallel Builder so this one can be closed.