public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: "Cygwin (cygwin@cygwin.com)" <cygwin@cygwin.com>
Subject: Re: search and install packages via bash?
Date: Sat, 10 Jul 2021 10:20:33 -0400	[thread overview]
Message-ID: <8cdf7f32-4fcb-4c44-1aa9-8145e4889720@cs.umass.edu> (raw)
In-Reply-To: <CA+kUOano_G-ZqQzi5O_9igB09EAzUbLjbCfmW36HSP80NX=X0w@mail.gmail.com>

On 7/10/2021 10:13 AM, Adam Dinwoodie wrote:
 > On Thu, 8 Jul 2021 at 22:15, Richard Beels via Cygwin wrote:
 >> 2, use fzf.  i don't use it (yet?) but it should be something like:

 > Just as a warning: the fzf package available on Cygwin is an old and
 > unsupported version. The upstream fzf project switched to Go, which doesn't
 > have a Cygwin compiler, so bringing it up-to-date is not an easy project.

I've noticed that gcc supports go (gccgo).  I gather that gccgo has not been
ported to cygwin, and that there is some problem doing so?  I did notice
remarks about using small stacks for goroutines requires the Gold linker.

It's more a point of curiosity, but perhaps someone could expand a bit on the
details :-) ...

Regards - Eliot Moss

  reply	other threads:[~2021-07-10 14:20 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-08  8:45 Ulli Horlacher
2021-07-08 12:13 ` Jon Turney
2021-07-08 13:53   ` Ulli Horlacher
2021-07-08 14:46     ` Marco Atzeri
2021-07-08 15:02       ` Ulli Horlacher
2021-07-08 14:19   ` Ulli Horlacher
2021-07-08 21:11     ` Richard Beels
2021-07-08 21:11     ` Richard Beels
2021-07-08 21:11     ` Richard Beels
     [not found]     ` <20210708211451.0007A3888821@sourceware.org>
2021-07-10  4:14       ` Richard Beels
     [not found]     ` <20210708211539.705673AA9C30@sourceware.org>
2021-07-10 14:13       ` Adam Dinwoodie
2021-07-10 14:20         ` Eliot Moss [this message]
2021-07-08 18:28 ` Thomas Wolff

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=8cdf7f32-4fcb-4c44-1aa9-8145e4889720@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --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).