From: Jose Isaias Cabrera <jicman@outlook.com>
To: "Csaba Ráduly" <rcsaba@gmail.com>, "cygwin list" <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 03:28:00 -0000 [thread overview]
Message-ID: <DB7PR01MB5386DDBE46994F520877EE09DE0B0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <6eb060d0-545b-4c7d-f6c6-a40772dda74f@gmail.com>
Csaba Ráduly, on Thursday, May 16, 2019 05:47 PM, wrote...
>Hi José,
Hi Csaba.
>Building GMP, MPFR and MPC seems like overkill. The following packages are
>available for Cygwin:
>
>libgmp-devel 6.1.2
>libmpfr-devel 4.0.2
>libmpc-devel 1.1.0
Yep, tried these, and for some reason, when I ran ./configure to build GCC6, it told me that I needed those libraries. The error message was,
[clip]
checking for the correct version of gmp.h... no
configure: error: Building GCC requires GMP 4.2+, MPFR 2.4.0+ and MPC 0.8.0+.
[clip]
So, I said, let me just do this, and there will not be any excuse. :-)
>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.
josé
--
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
next prev parent reply other threads:[~2019-05-17 3:28 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 [this message]
2019-05-17 13:16 ` Eliot Moss
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=DB7PR01MB5386DDBE46994F520877EE09DE0B0@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=rcsaba@gmail.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).