unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Alexandrov <dag@gnui.org>
Cc: guile-user@gnu.org, help-guix@gnu.org
Subject: Re: No Guile on Windows? (was: My Guile Hacker Handbook)
Date: Fri, 24 Jul 2020 08:41:47 +0300	[thread overview]
Message-ID: <83wo2teag4.fsf@gnu.org> (raw)
In-Reply-To: <tuxxsrmq.dag@gnui.org> (message from Dmitry Alexandrov on Fri, 24 Jul 2020 03:06:53 +0300)

> From: Dmitry Alexandrov <dag@gnui.org>
> Date: Fri, 24 Jul 2020 03:06:53 +0300
> Cc: Guile User <guile-user@gnu.org>, Guix Help <help-guix@gnu.org>
> 
> > ## Installation
> 
> > ### On Windows
> >
> > No solution yet.
> 
> Is that true?  Itʼs true (and a pity) that there no official packages, of course, but ‘no solution’?
> 
> I vaguely recall, there was a Guile on MinGW a couple of years ago, does it no longer build?  And what happened with Cygwin package after all?  cygwin.com says, that 3.0.4 is there [1].

  https://sourceforge.net/projects/ezwinports/files/guile-2.0.11-2-w32-bin.zip/download

Mind you, this is a 32-bit build, and it is configured without threads
(because building with threads produces Guile that crashes for almost
any non-trivial operation, you can find the details in the Guile
mailing list archives).

I never tried to build a newer Guile, as doing a fully-functional
MinGW port is a non-trivial endeavor that consumes a lot of time, and
I don't have that time now.

<rant>
Sadly, Guile seems to care only about one OS: GNU/Linux, and more or
less disregard the rest.  Features are added that clearly cannot
easily work on other OSes, let alone non-Posix ones, and with each
such new feature producing a working MinGW port becomes harder and
harder, even for experienced hackers.

Please don't bother replying to this rant, it's just FYI, to convey my
personal recollections and experiences from doing the 2.0.x port, and
I don't intend to argue about it.
</rant>


  reply	other threads:[~2020-07-24  7:52 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-23  6:18 My Guile Hacker Handbook Jérémy Korwin-Zmijowski
2020-07-23  6:46 ` test anything? (Re: My Guile Hacker Handbook) Marc Chantreux
2020-07-23 15:08   ` a French mailing list (was: test anything? (Re: My Guile Hacker Handbook)) Dmitry Alexandrov
2020-07-23 20:34     ` Marc Chantreux
2020-07-23  7:41 ` My Guile Hacker Handbook Zelphir Kaltstahl
2020-07-23  9:17   ` Jérémy Korwin-Zmijowski
2020-07-23 10:32 ` Bonface M. K.
2020-07-23 14:09   ` Jérémy Korwin-Zmijowski
2020-07-24  0:58     ` Bonface M. K.
2020-07-24  0:06 ` No Guile on Windows? (was: My Guile Hacker Handbook) Dmitry Alexandrov
2020-07-24  5:41   ` Eli Zaretskii [this message]
2020-07-24  7:22     ` Dr. Arne Babenhauserheide
2020-07-24  9:32       ` Christopher Lam
2020-07-24 11:50       ` Mike Gran
2020-07-24 16:25         ` Licensing of Cygwin comatibility layer (was: No Guile on Windows?) Dmitry Alexandrov
2020-07-24 23:33           ` Mike Gran
     [not found]     ` <878sf9812f.fsf@gnu.org>
2020-07-24 14:20       ` No Guile on Windows? Stefan Israelsson Tampe
2020-07-24 17:46         ` Dr. Arne Babenhauserheide
2020-07-24 17:47       ` Dmitry Alexandrov
2020-07-24 18:41       ` Jan Wielkiewicz
2020-07-25  3:48     ` No Guile on Windows? (was: My Guile Hacker Handbook) David Pirotte
2020-07-25  6:31       ` Eli Zaretskii
2020-07-25 13:56         ` Christopher Lam
2020-07-25 14:28           ` Eli Zaretskii
2020-07-28  2:52             ` Christopher Lam
2020-07-25 16:49         ` Mike Gran
2020-07-25 16:33       ` Jérémy Korwin-Zmijowski
2020-07-25 21:38       ` No Guile on Windows? Dmitry Alexandrov
2020-07-24  6:47   ` No Guile on Windows? (was: My Guile Hacker Handbook) divoplade
2020-07-24 11:38   ` Stefan Israelsson Tampe

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://guix.gnu.org/

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

  git send-email \
    --in-reply-to=83wo2teag4.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=dag@gnui.org \
    --cc=guile-user@gnu.org \
    --cc=help-guix@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).