public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "davek at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug bootstrap/42529] Stage 1 compiler cannot compile Date: Tue, 23 Mar 2010 04:04:00 -0000 [thread overview] Message-ID: <20100323040359.16277.qmail@sourceware.org> (raw) In-Reply-To: <bug-42529-6183@http.gcc.gnu.org/bugzilla/> ------- 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
next prev parent reply other threads:[~2010-03-23 4:04 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2009-12-28 23:51 [Bug bootstrap/42529] New: " mckelvey at maskull dot com 2009-12-28 23:52 ` [Bug bootstrap/42529] " mckelvey at maskull dot com 2009-12-28 23:53 ` mckelvey at maskull dot com 2009-12-28 23:54 ` mckelvey at maskull dot com 2009-12-28 23:58 ` mckelvey at maskull dot com 2009-12-29 16:52 ` rwild at gcc dot gnu dot org 2009-12-30 2:28 ` mckelvey at maskull dot com 2010-01-02 1:28 ` mckelvey at maskull dot com 2010-02-17 15:39 ` davek at gcc dot gnu dot org 2010-03-21 0:04 ` davek at gcc dot gnu dot org 2010-03-22 2:00 ` mckelvey at maskull dot com 2010-03-23 0:22 ` davek at gcc dot gnu dot org 2010-03-23 4:04 ` davek at gcc dot gnu dot org [this message] 2010-03-24 2:35 ` mckelvey at maskull dot com 2010-03-24 4:57 ` mckelvey at maskull dot com 2010-03-24 18:26 ` mckelvey at maskull dot com 2010-03-25 14:54 ` davek at gcc dot gnu dot org 2010-03-26 16:49 ` mckelvey at maskull dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20100323040359.16277.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).