public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/61173] [4.9/4.10 Regression] Erroneous "end of file" with internal read
Date: Wed, 04 Jun 2014 02:05:00 -0000	[thread overview]
Message-ID: <bug-61173-4-cZQDThCRKh@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-61173-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61173

--- Comment #8 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
I will backport to 4.9 in the next few days so it will get into 4.9.1

I am not sure how your snapshot is set up.  If it is using dynamically loaded
library, you may be getting the newer gfortran calling an older libgfortran in
the library search path. So try with -static to see if that works. It should be
in the 4.10 trunk by the date you gave for the snapshot.


  parent reply	other threads:[~2014-06-04  2:05 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-13 12:59 [Bug libfortran/61173] New: " dominiq at lps dot ens.fr
2014-05-13 13:24 ` [Bug libfortran/61173] " rguenth at gcc dot gnu.org
2014-05-13 14:03 ` krefson at googlemail dot com
2014-05-13 14:11 ` dominiq at lps dot ens.fr
2014-05-14  0:38 ` jvdelisle at gcc dot gnu.org
2014-05-24 13:42 ` jvdelisle at gcc dot gnu.org
2014-05-24 19:26 ` jvdelisle at gcc dot gnu.org
2014-05-24 19:31 ` jvdelisle at gcc dot gnu.org
2014-06-03 13:55 ` krefson at gmail dot com
2014-06-04  2:05 ` jvdelisle at gcc dot gnu.org [this message]
2014-06-07 17:36 ` jvdelisle at gcc dot gnu.org
2014-06-07 17:40 ` jvdelisle at gcc dot gnu.org
2014-06-07 17:41 ` jvdelisle 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-61173-4-cZQDThCRKh@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: 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).