This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: Cygwin support
Brian Dessent wrote:
> Cygwin has been a secondary target for a number of years. MinGW has
> been a secondary target since 4.3. This generally means that they
> should be in fairly good shape, more or less. To quote the docs:
>
>> Our release criteria for the secondary platforms is:
>>
>> * The compiler bootstraps successfully, and the C++ runtime library builds.
>> * The DejaGNU testsuite has been run, and a substantial majority of the tests pass.
>
>
> More recently I've seen Danny Smith report that the IRA merge broke
> MinGW (and presumably Cygwin, since they share most of the same code)
> bootstrap. I haven't tested this myself recently so I don't know if
> it's still broken or not.
>
I've run the bootstrap and testsuite twice in the last month. The
bootstrap failures are due to a broken #ifdef specific to cygwin in the
headers provided with cygwin, the requirement for a specific version of
autoconf (not available in setup), and the need to remove the -werror in
libstdc++ build (because of minor discrepancies in cygwin headers). All
of those are easy to rectify, but fixes seem unlikely to be considered by
the decision makers. However, the C++ testsuite results are unacceptable,
with many internal errors.
For some time now, gfortran has been broken for practical purposes, even
when it passes testsuite, as it seems to have a memory leak. This shows
up in the public wiki binaries.
So, there are clear points for investigation of cygwin problems, and
submission of PRs, should you be interested.
> Running the dejagnu testsuite on Cygwin is
> excruciatingly slow due to the penalty incurred from emulating fork.
It runs over a weekend on a Pentium D which I brought back to life by
replacing the CPU cooler system. I have no problem with running this if I
am in the office when the snapshot is released, but I think there is
little interest in fixing the problems which are specific to g++ on
cygwin, yet working gcc and gfortran aren't sufficient for gcc upgrades to
be accepted. Support for 64-bit native looks like it will be limited to
mingw, so I no longer see a future for gcc on cygwin.