public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "fxcoudert at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug libfortran/37634] Fix libgfortran compiling to support GCC_NO_EXECUTABLES Date: Mon, 29 Jul 2013 13:28:00 -0000 [thread overview] Message-ID: <bug-37634-4-IcPYYNA1TD@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-37634-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37634 Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fxcoudert at gcc dot gnu.org --- Comment #5 from Francois-Xavier Coudert <fxcoudert at gcc dot gnu.org> --- I think this bug was fixed by Steve Ellcey in revision 200374: r200374 | sje | 2013-06-24 17:24:19 +0200 (Mon, 24 Jun 2013) | 5 lines 2013-06-24 Steve Ellcey <sellcey@mips.com> * configure.ac (AC_CHECK_FUNCS_ONCE): Put into if statement. * configure: Regenerate. (though, for some reason, this commit message cannot be found in libgfortran/ChangeLog). I'm closing, please reopen if it is not actually fixed (with current explanation of what goes wrong).
next parent reply other threads:[~2013-07-29 13:28 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-37634-4@http.gcc.gnu.org/bugzilla/> 2013-07-29 13:28 ` fxcoudert at gcc dot gnu.org [this message] 2014-06-20 21:02 ` fxcoudert at gcc dot gnu.org 2008-09-24 6:04 [Bug fortran/37634] New: " burnus at gcc dot gnu dot org 2009-03-29 9:17 ` [Bug libfortran/37634] " fxcoudert at gcc dot gnu dot org 2010-01-09 8:03 ` monaka at monami-software dot com 2010-01-09 8:20 ` monaka at monami-software dot com 2010-01-10 8:45 ` rwild at gcc dot gnu dot 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-37634-4-IcPYYNA1TD@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).