public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: <tlake@twcny.rr.com>
To: <cygwin@cygwin.com>
Subject: RE: Segmentation fault when compiling *FIXED*
Date: Wed, 05 Sep 2018 21:33:00 -0000	[thread overview]
Message-ID: <!&!AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAAmRymg6bL7QLuD+lale3y3AQAAAAA=@twcny.rr.com> (raw)

In the latest build of Windows 10, sent out on 5 Sep 2018, the gcc compiler
no longer gives a segmentation error. Whew! I'm glad that's fixed.

Tom L

-----Original Message-----
From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> On Behalf Of
cygwin-digest-help@cygwin.com
Sent: Wednesday, August 29, 2018 8:35 PM
To: cygwin@cygwin.com
Subject: cygwin Digest 30 Aug 2018 00:35:09 -0000 Issue 10983


cygwin Digest 30 Aug 2018 00:35:09 -0000 Issue 10983

Topics (messages 213705 through 213711):

[ANNOUNCEMENT] Updated: xorg-server-1.20.1-1
	213705 by: Jon Turney

Re: libmpi_cxx.dll.a missing
	213706 by: Marco Atzeri

Re: gecko Segmentation fault when compiling
	213707 by: Marco Atzeri
	213708 by: Andrey Repin
	213709 by: tlake.twcny.rr.com

Re: "build-essential" metapackage [WAS: FW: gecko Segmentation fault when
compiling]
	213710 by: cyg Simple
	213711 by: Andrey Repin

Administrivia:

To subscribe to the digest, e-mail:
	cygwin-digest-subscribe@cygwin.com

To unsubscribe from the digest, e-mail:
	cygwin-digest-unsubscribe@cygwin.com

To post to the list, e-mail:
	cygwin@cygwin.com


----------------------------------------------------------------------


--
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:[~2018-09-05 21:33 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=''\!'&'\!'AAAAAAAAAAAuAAAAAAAAAOY+MTsETahCgLYsSiyFXC4BAMO2jhD3dRHOtM0AqgC7tuYAAAAAAA4AABAAAAAmRymg6bL7QLuD+lale3y3AQAAAAA=@twcny.rr.com' \
    --to=tlake@twcny.rr.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).