https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
Jerry DeLisle changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
--- Comment #6 from Jerry DeLisle ---
Author: jvdelisle
Date: Mon Oct 24 21:42:29 2016
New Revision: 241497
URL: https://gcc.gnu.org/viewcvs?rev=241497=gcc=rev
Log:
2016-10-24 Jerry DeLisle
PR fortran/77828
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
Jerry DeLisle changed:
What|Removed |Added
CC||damian at sourceryinstitute
dot or
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
--- Comment #4 from Jerry DeLisle ---
Just need to edit the trunk/libgfortran/libtool-version file, bumping the major
rev number and build from a clean build directory. I have tested this and it
works fine. I want to see if we are going to get
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
--- Comment #3 from vehre at gcc dot gnu.org ---
That's what library version numbering was made, wasn't it? I.e., this is the
way to go IMO.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |7.0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
--- Comment #2 from Jerry DeLisle ---
Created attachment 39746
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39746=edit
One approach to resolving this
With the attached patch, here is the result of trying to go forward or backward
with
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
Jerry DeLisle changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77828
vehre at gcc dot gnu.org changed:
What|Removed |Added
Priority|P3 |P4