public inbox for cygwin-talk@cygwin.com
 help / color / mirror / Atom feed
From: Warren Young <wyml@etr-usa.com>
To: The Vulgar and Unprofessional Cygwin-Talk List <cygwin-talk@cygwin.com>
Subject: Re: earlier gcc version installation
Date: Thu, 21 May 2015 19:26:00 -0000	[thread overview]
Message-ID: <00BA695A-9B4D-4F3C-A045-A3EF9F91FB10@etr-usa.com> (raw)
In-Reply-To: <555DEE10.20409@nchc.narl.org.tw>

On May 21, 2015, at 8:39 AM, Jyh-Shyong Ho <9003101@nchc.narl.org.tw> wrote:
> 
> Dear Cygwin users,

This is the off-topic chat mailing list, not the user help list.  Please post such questions to the main Cygwin list next time, not here.

Mostly the rest of this message is going to send you to other sources, so if you feel the need to reply to this, send it to on one of those other places.  If you want, you can post a pointer to the new location for the discussion to this thread.

> I am not able to build the same program with the gcc/gfortran (4.9.2) in the latest version of Cgywin/CygwinX.

Then I suggest that you post the problem code and the error messages to an appropriate forum.

If the same version of GCC compiles this program on other platforms, and fails only on Cygwin, then that “appropriate forum" may be one of the Cygwin mailing lists.

If GCC 4.9.x won’t compile that software on *any* platform, then you need to take it up on a more general C/Fortran programming forum.

> I tried to install the older version of gcc/gfortran (4.6.x) on the current Cygwin/CugwinX so I can build my program again, but I have not been successful.

“It fails” is not a diagnosable condition.  How exactly did it fail?  What errors do you get?  Where did you get the older GCC packages?  How did you install them, given that you must not have done it through setup.exe?

We need details, and it would be nice to have a replicable test case, too.

Also, standard practice is to include the output of “cygcheck -rsv” with problem reports, as an attachment to the mailing list post.

> I wonder if it is possible to build an older version of gcc on the current Cygwin environment?

Why not?

I suggest starting with the Cygwin package source, which should be available from the same source that provided the old Cygwin GCC binary packages.  (If not, that archive is not complying with the GPL.)

If you got these packages from the Cygwin Time Machine, then I believe you have everything you need.

  reply	other threads:[~2015-05-21 19:26 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-21 14:39 Jyh-Shyong Ho
2015-05-21 19:26 ` Warren Young [this message]
2015-06-02 14:30 ` UFRJLu

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=00BA695A-9B4D-4F3C-A045-A3EF9F91FB10@etr-usa.com \
    --to=wyml@etr-usa.com \
    --cc=cygwin-talk@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).