public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "burnus at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/49683] The system cannot execute the specified program Date: Sat, 09 Jul 2011 11:44:00 -0000 [thread overview] Message-ID: <bug-49683-4-ag3HXsglqa@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-49683-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=49683 Tobias Burnus <burnus at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |burnus at gcc dot gnu.org --- Comment #1 from Tobias Burnus <burnus at gcc dot gnu.org> 2011-07-09 11:44:03 UTC --- I don't have a good idea about the issue which you see. However, it is better to ask such questions at the mailing list - either gcc-help@ or fortran@ - than in a bug report. See http://gcc.gnu.org/lists.html for more information about GCC's lists. Note: g77 is no longer supported, it has been replaced since 6 years by "gfortran", which is a complete rewrite, which still supports Fortran 77 inclusive many vendor extensions (but which also supports Fortran 90 to (with restrictions) Fortran 2008). In particular, the Windows support (both MinGW and Cygwin, including 64bit Windows) of gfortran is much better than of g77. Thus, I would strongly suggest to update to gfortran. For binaries, see http://gcc.gnu.org/wiki/GFortranBinaries , which links to the official MinGW and Cygwin builds but also to other GCC builds.
next prev parent reply other threads:[~2011-07-09 11:44 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-07-08 23:23 [Bug fortran/49683] New: " mgrech at shaw dot ca 2011-07-09 11:44 ` burnus at gcc dot gnu.org [this message] 2011-07-24 18:43 ` [Bug fortran/49683] " dfranke at gcc dot gnu.org 2011-11-07 22:38 ` fxcoudert at gcc dot gnu.org
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=bug-49683-4-ag3HXsglqa@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /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: linkBe 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).