unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: David Pirotte <david@altosw.be>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Dmitry Alexandrov <dag@gnui.org>, guile-user@gnu.org, help-guix@gnu.org
Subject: Re: No Guile on Windows? (was: My Guile Hacker Handbook)
Date: Sat, 25 Jul 2020 00:48:35 -0300	[thread overview]
Message-ID: <20200725004835.3e0c7056@capac> (raw)
In-Reply-To: <83wo2teag4.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 797 bytes --]

Hello,

> > > ### On Windows
> > > No solution yet.  

fwiw, i've used msys2 (not so much anymore, but i still would if i had
to ...), easy to install, update, well maintained, very friendly on irc
when i needed to ask for help ...:

	https://www.msys2.org/

it has guile-2.2.7-1, threaded (which I've used. it works ...)

	https://packages.msys2.org/base/guile

for me, it was fantastic _not to have to deal_ with ouindoze on
ouindoze, so msys2, its numerous packages ... and guile-2.2.7-1
'saved my life' :)

	dowload the lastest msys2
	double-click -> linux terminal
	use pacman (*) to update and install new packages

David

	** Update

	pacman -Syu
	pacman -Su

	** Packages

	pacman -S emacs
	pacman -S guile
	pacman -S libguile
	pacman -S libguile-devel

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  parent reply	other threads:[~2020-07-25  3:49 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
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     ` David Pirotte [this message]
2020-07-25  6:31       ` No Guile on Windows? (was: My Guile Hacker Handbook) 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=20200725004835.3e0c7056@capac \
    --to=david@altosw.be \
    --cc=dag@gnui.org \
    --cc=eliz@gnu.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).