random hangs

[Allen Hewes]

On Tue, 2025-01-07 at 17:56 +0100, Marco Atzeri via Cygwin wrote:
> On 07/01/2025 14:42, Rainer Emrich wrote:
> > I played a bit around and tried to install severall python
> > packages.
> > There seems to be a severe issue, because an increasing number of
> > python
> > packages need a working rust compiler to build. And AFAIK there is
> > no
> > rust compiler for cygwin at the moment.
> >
>
> that I can not solve :-(
>
> Porting a compiler to Cygwin with a not collaborating upstream
> developer team is a major major effort
>
>

I feel this issue is more acute. Using rust isn't just happening in
Python / PyPi Land. This is happening in Ruby and common C/C++
libraries. I have also encountered this technique with Go but no where
near the frequency like I have with Rust. AFAIK, go doesn't target
Cygwin either.

I did find some folks discussing what it would take for Rust to target
a new platform in Git Hub issues (I _think_, it's been over a year
since I spent some effort looking into this). They were in fact
discussing Cygwin.

I am not going to say the Sky Is Falling, it certainly isn't, but it
does feel like Cygwin is traveling down a road that will intersect with
Rust and there will be a train wreck. IMHO of course...

Because I was struggling with this issue, I decided to leave Windows
for Fedora, but YMMV. I know not everyone who uses Cygwin can switch to
something like Fedora.

Many Thanks to all the Cygwin contribs for the Python ecosystem and
cygbuild. I used and was quite happy with Cygwin for a long time. It Is
Good Stuff, IMHO.

/allen

________________________________

Disclaimer Confidentiality Notice: This e-mail, and any attachments and/or documents linked to this email, are intended for the addressee and may contain information that is privileged, confidential, proprietary, or otherwise protected by law. Any dissemination, distribution, or copying is prohibited. This notice serves as a confidentiality marking for the purpose of any confidentiality or nondisclosure agreement. If you have received this communication in error, please contact the original sender.