------- Comment #12 from davek at gcc dot gnu dot org 2010-03-23 04:03 -------
(In reply to comment #11)
> That's the next thing to try. I'm just testing a build of HEAD using your
> formula to see if it reproduces.
Well, nope, that's gone way past stage 1 by now and no sign of any problems.
Bizarre. Here's another possibility:
(In reply to comment #10)
> $ cygcheck gcc/cc1.exe
[ windows dlls snipped ]
> J:\Home\cvsroot\gcc-obj\gcc\cc1.exe
> C:\cygwin\bin\cygcloog-0.dll
> C:\cygwin\bin\cyggcc_s-1.dll
> C:\cygwin\bin\cygwin1.dll
> C:\cygwin\bin\cyggmp-3.dll
> C:\cygwin\bin\cygppl_c-2.dll
> C:\cygwin\bin\cygppl-7.dll
> C:\cygwin\usr\local\bin\cygstdc++-6.dll
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> C:\cygwin\usr\local\bin\cyggcc_s-sjlj-1.dll
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> C:\cygwin\bin\cyggmpxx-4.dll
> C:\cygwin\bin\cygiconv-2.dll
> C:\cygwin\bin\cygmpc-1.dll
> C:\cygwin\bin\cygmpfr-1.dll
You seem to have some self-built dlls in your path from an earlier build? And
what's all this about sjlj exceptions? You'll need to get those out of your
path. I'm afraid that although we version libgcc's soname according to the EH
type, we don't have similar functionality for the other shared libs yet, so
Cygwin doesn't support mixing DLLs built on the two different EH models.
Please check if the problem invoking cc1 goes away once you've got those DLLs
out of your PATH.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42529
