From: Yaakov Selkowitz <yselkowitz@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: [ANNOUNCEMENT] [Updated] mingw64-{i686,x86_64}-gcc-7.4.0-1
Date: Mon, 31 Dec 2018 10:58:00 -0000 [thread overview]
Message-ID: <4d34f1150b08e95b78a0de4cf696c2660bd86101.camel@cygwin.com> (raw)
In-Reply-To: <5c296c8a.1c69fb81.b7c1d.b304@mx.google.com>
On Sun, 2018-12-30 at 17:10 -0800, Steven Penny wrote:
> On Sun, 30 Dec 2018 02:36:15, JonY wrote:
> > The mingw-w64 cross compilers have been updated:
> >
> > * mingw64-i686-gcc-7.4.0-1
> > * mingw64-x86_64-gcc-7.4.0-1
>
> Note the problem i detailed in august has not been resolved:
>
> https://cygwin.com/ml/cygwin/2018-08/msg00275.html
Have you considered that perhaps the issue is with MSYS2 (incomplete
libstdc++ debuginfo)?
--
Yaakov
--
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 prev parent reply other threads:[~2018-12-31 6:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-31 1:10 JonY
2018-12-31 6:20 ` Steven Penny
2018-12-31 10:58 ` Yaakov Selkowitz [this message]
2018-12-31 12:58 ` Steven Penny
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=4d34f1150b08e95b78a0de4cf696c2660bd86101.camel@cygwin.com \
--to=yselkowitz@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).