From: "Roger Orr" <rogero@howzatt.demon.co.uk>
To: <cygwin@cygwin.com>
Subject: RE: Compiling gcc trunk under cygwin
Date: Tue, 02 Feb 2016 08:10:00 -0000 [thread overview]
Message-ID: <1274A5F0B9F549B1AC77D4B02A271F78@Tamar> (raw)
In-Reply-To:
FYI
Fixes for both issues now released to gcc trunk.
Roger.
-----Original Message-----
From: Roger Orr [mailto:rogero@howzatt.demon.co.uk]
Sent: 27 January 2016 00:16
To: 'cygwin@cygwin.com'
Subject: RE: Compiling gcc trunk under cygwin
FYI
(1) Revision 232071 problem
The pr66655 has a new proposed patch, which does appear to build on cygwin,
and is awaiting final approval.
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655
(2) Revision 232454 problem
I've now reported the revision 232454 problem as pr69506 (as it's been well
over a week since the problematic check-in)
See https://gcc.gnu.org/bugzilla/show_bug.cgi?id=69506
Regards,
Roger.
-----Original Message-----
From: Roger Orr [mailto:rogero@howzatt.demon.co.uk]
Sent: 23 January 2016 14:19
To: cygwin@cygwin.com
Subject: Re: Compiling gcc trunk under cygwin
David Wohlferd <dw <at> LimeGreenSocks.com> writes:
> Until recently, I've been able to build gcc under cygwin just fine. But
> (relatively) recent checkins (232454 & 232071) are causing problems.
Have you reported the problems with 232454 to gcc yet?
I've already reported the 232071 problem, on the original bug report this
was trying to fix. See gcc's bugzilla:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66655
Roger.
--
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
next reply other threads:[~2016-02-02 8:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 8:10 Roger Orr [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-01-22 7:35 David Wohlferd
2016-01-23 16:42 ` Roger Orr
2016-01-27 6:45 ` Roger Orr
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=1274A5F0B9F549B1AC77D4B02A271F78@Tamar \
--to=rogero@howzatt.demon.co.uk \
--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).