public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Doug Henderson <djndnbvg@gmail.com>
To: 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 05:13:00 -0000	[thread overview]
Message-ID: <CAJ1FpuNMrwKY65SMFQ+Zv38WZyNW6SrMz53dYKPZ_Qs8GmCaRw@mail.gmail.com> (raw)
In-Reply-To: <DB7PR01MB5386E5F177071EF6DCF66DE4DE090@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>

On Wed, 15 May 2019 at 14:58, Jose Isaias Cabrera <> wrote:

> Is there a way an easy way to install gcc-6 and g++-6 on cygwin?  I just uninstalled v7.4.x or whatever was on the setup.  I am trying to build a software and gcc 7.x and g++ 7.x is giving too many compiler errors.  I want to try 6 to see if these errors minimize or go away.  Thanks for the help.

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.

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.

You can use the help option to get more information about a lot of topics.

 | --help={common|optimizers|params|target|warnings|[^]{joined|separate|undocumented}}[,...].
 |                          Display specific types of command line options.

You can use gcc options to determine which version of C the compiler
will compile. There are also options to control which warnings are
generated, and possibly turned into errors by a -Werror option.

Use the info command:

info gcc

and enter the info search command: (CR=press enter)

/-std=CR

to find the relavent section.

HTH
Doug

-- 
Doug Henderson, Calgary, Alberta, Canada - from gmail.com

--
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

  parent reply	other threads:[~2019-05-18  5:13 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 [this message]
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=CAJ1FpuNMrwKY65SMFQ+Zv38WZyNW6SrMz53dYKPZ_Qs8GmCaRw@mail.gmail.com \
    --to=djndnbvg@gmail.com \
    --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).