unofficial mirror of guile-devel@gnu.org 
 help / color / mirror / Atom feed
From: "Mike Gran" <spk121@yahoo.com>
To: guile-devel@gnu.org
Subject: Cygwin port of Guile 2.2
Date: Tue, 04 Apr 2017 09:45:43 -0700	[thread overview]
Message-ID: <874ly49l54.fsf@joshua.spikycactus.dnsalias.com> (raw)

Hello All,

I push a branch that mostly makes Guile 2.2 work on Cygwin.

In the end, I had a few issues.

Cygwin's uselocale is broken and can segrault.  I fell back
to the standard nl-langinfo.  I understand the issue and may
push a patch upstream to Cygwin sometime.

Also Cygwin's langinfo is incomplete with regards to LC
MONETARY.  This also is fixable upstream in Cygwin.

Cygwin requires stability on both ends of a pipe being used
for inter-thread communication.  If one tries to read from a
pipe that is closing on the other end, Cygwin may fault.  I
worked around this by replacing pipes with a
producer/consumer pattern of semaphores and mutex-protected
variables.  A dirty workaround.

Lastly, Cygwin's fork just doesn't play well with Guile's
new GC and threading model.  Despite a copy of days in the
guts of it all, I don't understand the specifics of the
issue.  So, in the branch, I disabled forking altogether,
and by extension, popen and friends.

While I couldn't get fork to work, the other threading
primitives seem fine.

The branch is wip-cygwin-guile-2.2.

Thanks,

Mike Gran



             reply	other threads:[~2017-04-04 16:45 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 16:45 Mike Gran [this message]
2017-04-04 17:03 ` Cygwin port of Guile 2.2 Eli Zaretskii
2017-04-14  8:35 ` Andy Wingo
2017-04-14 13:41   ` Derek Upham
2017-04-17  8:04     ` Andy Wingo
2017-04-17 15:05       ` Derek Upham
2017-05-01 20:48         ` Derek Upham
2017-05-02 19:35           ` Andy Wingo
2017-05-03  3:18             ` Derek Upham
2017-05-03  9:24               ` Andy Wingo
2017-05-03  9:39                 ` szgyg
2017-05-03 14:21                 ` Derek Upham
2017-05-09 19:08                   ` Andy Wingo
2017-05-12 14:13                     ` Derek Upham
2017-05-15 20:06                       ` Andy Wingo
2017-05-04  5:21               ` zv

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

  List information: https://www.gnu.org/software/guile/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874ly49l54.fsf@joshua.spikycactus.dnsalias.com \
    --to=spk121@yahoo.com \
    --cc=guile-devel@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: 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).