From: Jose Isaias Cabrera <jicman@outlook.com>
To: Doug Henderson <djndnbvg@gmail.com>, cygwin <cygwin@cygwin.com>
Subject: Re: How to install gcc and g++ 6 on cygwin which are not on the setup.exe
Date: Sat, 18 May 2019 12:14:00 -0000 [thread overview]
Message-ID: <DB7PR01MB53867D0094E233ECE9E2AA1EDE040@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <CAJ1FpuNMrwKY65SMFQ+Zv38WZyNW6SrMz53dYKPZ_Qs8GmCaRw@mail.gmail.com>
Doug Henderson, Saturday, May 18, 2019 01:12 AM, wrote...
>On Wed, 15 May 2019 at 14:58, Jose Isaias Cabrera <> wrote:
>You seem to be having some difficulty getting an older version of the
>compiler running. Perhaps it might be useful to go back to the
>beginning and see if there is an alternative solution.
That is how I started. But, when I started to compile Bedrockdb, there were too many compiler errors. Since the source is gcc-6 compatible, the version I downloaded from cygwin was 7.4.0-01. So, I didn't want to go that way, since the source would have to be changed.
>What kind of compiler errors are you getting? Post the gcc command
>line and a sample of the errors to see if anyone has suggestions for
>resolving them in gcc7.x.
I could try this next, but I would need you to be there. :-) Just kidding.
>
>HTH
>Doug
Thanks, Doug. I have installed gcc-6,
e608313@HOR711318E ~/gcc/gcc-6.4.0
$ gcc --version
gcc (GCC) 6.4.0
Copyright (C) 2017 Free Software Foundation, Inc.
This is free software; see the source for copying conditions. There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
e608313@HOR711318E ~/gcc/gcc-6.4.0
$ which gcc
/usr/local/bin/gcc
So, now I will start to compile Bedrockdb. Thanks for all your help, folks.
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
prev parent reply other threads:[~2019-05-18 12:14 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
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 [this message]
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=DB7PR01MB53867D0094E233ECE9E2AA1EDE040@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
--to=jicman@outlook.com \
--cc=cygwin@cygwin.com \
--cc=djndnbvg@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).