public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "textdirected at gmail dot com" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug fortran/66534] Compilation error of gfortran building on YDL6.2 Date: Thu, 15 Oct 2015 05:29:00 -0000 [thread overview] Message-ID: <bug-66534-4-d9UIXkEv4E@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-66534-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=66534 --- Comment #6 from HEMMI, Shigeru <textdirected at gmail dot com> --- Thanks for the reply. > Did you asked yellow dog linux for help? No, YDL seems stopping maintenance/developing. > IMO it would be more honest to close this PR as WONTFIX. I closed this thread at your suggestion. > Well, gfortran is built on a quite broad range of platforms without the problem you report. My work is very much relying on gfortran. I am using prebuilte gfortran binary (mingw-w64) mainly on Windows machine. Almost all things going well. Since gcc-5.2.0 gcc/g++ are built without problem on my outdated YDL machine, so I expected gfortran is also well built on my YDL machine, but not. Anyway, thank you very much for developing gfortran. Best regards,
prev parent reply other threads:[~2015-10-15 5:29 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-06-14 11:13 [Bug fortran/66534] New: " textdirected at gmail dot com 2015-06-14 11:33 ` [Bug fortran/66534] " schwab@linux-m68k.org 2015-08-30 10:42 ` dominiq at lps dot ens.fr 2015-09-06 8:08 ` textdirected at gmail dot com 2015-10-10 8:48 ` dominiq at lps dot ens.fr 2015-10-15 5:29 ` textdirected at gmail dot com [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=bug-66534-4-d9UIXkEv4E@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).