public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Jose Isaias Cabrera <jicman@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
	"moss@cs.umass.edu"	<moss@cs.umass.edu>
Subject: Re: How to install gcc and g++ 6 on cygwin which are not on the setup.exe
Date: Sat, 18 May 2019 12:01:00 -0000	[thread overview]
Message-ID: <DB7PR01MB538653191C58608F0F68DC30DE040@DB7PR01MB5386.eurprd01.prod.exchangelabs.com> (raw)
In-Reply-To: <DB7PR01MB5386024F1F0E0D8B0A0B29E9DE040@DB7PR01MB5386.eurprd01.prod.exchangelabs.com>


Ran,

./configure --enable-languages=c,c++

to take out java.  Finished overnight.  Ran 'make test' and there were none.  So now running 'make install' and waiting...  Thanks for your help.

josé

________________________________
From: cygwin-owner@cygwin.com <cygwin-owner@cygwin.com> on behalf of Jose Isaias Cabrera <jicman@outlook.com>
Sent: Friday, May 17, 2019 11:18 PM
To: cygwin@cygwin.com; moss@cs.umass.edu
Subject: Re: How to install gcc and g++ 6 on cygwin which are not on the setup.exe


After more than 8 hours running, building gcc-6.4.0, this error popped up:

In file included from ../.././libjava/jni-libjvm.cc:14:0:
../.././libjava/include/jvm.h:795:3: error: ‘ParkHelper’ does not name a type
   ParkHelper park_helper;

Did a few duckduckgo searches and nothing helpfult was found.  Before I go to the gcc email support, anyone has an idea?  Thanks.

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


--
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 12:01 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 [this message]
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=DB7PR01MB538653191C58608F0F68DC30DE040@DB7PR01MB5386.eurprd01.prod.exchangelabs.com \
    --to=jicman@outlook.com \
    --cc=cygwin@cygwin.com \
    --cc=moss@cs.umass.edu \
    /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).