public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Corinna Vinschen <corinna-cygwin@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] Updated: mingw64-*-{gcc,headers,runtime,pthreads}, New package: mingw64-*-winpthreads
Date: Tue, 30 Jul 2013 11:17:00 -0000	[thread overview]
Message-ID: <20130730082656.GK4166@calimero.vinschen.de> (raw)
In-Reply-To: <51F6EEB7.9020400@gmail.com>

On Jul 30 06:37, JonY wrote:
> Hi,
> 
> After removing 4.8-cmodel-medium.patch and 4.8-duplicate-symbols.patch
> for 32bit cygwin, 2nd stage libgcc fails with spawn error, "C compiler
> cannot create executables".

I thought the 4.8-cmodel-medium.patch only affects the x86_64 target.

> Running the compile command manually does show it running cc1, but hangs
> indefinitely, adding -v causes it to emit xgcc: error: unrecognized
> command line option ‘-v’.
> 
> Piping the C files over stdin and adding -xc makes it run, but it never
> does produce any output file. It does print some Execution times statistics.
> 
> I'm not sure what's going on.

Can you discuss this in the gcc mailing lists?  I hope Kai is available
for some input...


Corinna

-- 
Corinna Vinschen                  Please, send mails regarding Cygwin to
Cygwin Maintainer                 cygwin AT cygwin DOT com
Red Hat

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

      reply	other threads:[~2013-07-30  8:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12 12:42 JonY
2013-07-26  5:23 ` Yaakov (Cygwin/X)
2013-07-26 10:26   ` JonY
2013-07-27  5:17     ` JonY
2013-07-30  8:27       ` JonY
2013-07-30 11:17         ` Corinna Vinschen [this message]

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=20130730082656.GK4166@calimero.vinschen.de \
    --to=corinna-cygwin@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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: link
Be 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).