public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
To: cygwin@cygwin.com
Subject: Re: How to install gcc and g++ 6 on cygwin which are not on the setup.exe
Date: Fri, 17 May 2019 13:16:00 -0000	[thread overview]
Message-ID: <94231473-d378-952e-a450-d0323e3906dd@cs.umass.edu> (raw)
In-Reply-To: <DB7PR01MB5386DDBE46994F520877EE09DE0B0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>

On 5/16/2019 11:28 PM, Jose Isaias Cabrera wrote:
> Csaba Ráduly, on Thursday, May 16, 2019 05:47 PM, wrote...

>> BTW, if you're trying to build Bedrockdb, G++ 6 is likely unable to help you.
>> The Bedrockdb developers seem to suffer a bit from "all the world is Linux"
>> syndrome.
> 
> Yeah.  Seems like the whole world is thinking like that. :-)  I do have linux boxes at home, but I also have windows.  Thanks for all the help.  I will let you know the outcome.  Already built GMP and MPFR.  Now running 'make' on MPC.  This one should take less time than MPFR.  GMP took a good 3 hours just to run make.  YIKES.  Later.

I've been a Cygwin user for a long time, and I like it, but
another possibility here for you is WSL (Windows Subsystem
for Linux).  It's a pretty easy install, and because it is
done by Microsoft and can reliably use internal interfaces,
there are ways in which it is more Linux-like -- for many
packages you can just do apt-get install and they work.  In
my experience the performance is comparable to Cygwin, maybe
a touch faster (but no where near as fast for heavy forking
as running inside a Virtual Box Ubuntu virtual machine, for
example).  It has its limitations, for sure, but I have found
it helpful for some things.

Regards - Eliot Moss

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2019-05-17 13:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-15 20:58 Jose Isaias Cabrera
2019-05-16  7:36 ` Csaba Raduly
2019-05-16 16:47   ` Jose Isaias Cabrera
2019-05-16 21:47     ` Csaba Ráduly
2019-05-17  3:28       ` Jose Isaias Cabrera
2019-05-17 13:16         ` Eliot Moss [this message]
2019-05-17 15:21           ` Jose Isaias Cabrera
2019-05-18  3:18             ` Jose Isaias Cabrera
2019-05-18  5:14               ` Brian Inglis
2019-05-18  6:50                 ` Csaba Raduly
2019-05-18 12:19                   ` Jose Isaias Cabrera
2019-05-18 15:54                     ` Ken Brown
2019-05-18 20:15                       ` Csaba Raduly
2019-05-18 23:15                       ` Jose Isaias Cabrera
2019-05-19  1:24                         ` Jose Isaias Cabrera
2019-05-19  2:57                           ` Jack
2019-05-19  8:37                             ` Csaba Raduly
2019-05-20 14:56                               ` Jose Isaias Cabrera
2019-05-18 12:16                 ` Jose Isaias Cabrera
2019-05-18 12:01               ` Jose Isaias Cabrera
2019-05-18  5:13 ` Doug Henderson
2019-05-18 12:14   ` Jose Isaias Cabrera

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=94231473-d378-952e-a450-d0323e3906dd@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).