--- Comment #4 from steve dot chapel at a2pg dot com 2010-05-13 16:28
---
:)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38404
--- Comment #2 from steve dot chapel at a2pg dot com 2010-05-13 13:15
---
Excellent! The new warning is far more understandable than the old.
X'"R" IN CALL RANDOM MAY NOT BE USED OUTSIDE THE BLOCK CONTAINING T
1
Warning: Initialization string starting at (1
cc
Version: 4.3.2
Status: UNCONFIRMED
Severity: minor
Priority: P3
Component: fortran
AssignedTo: unassigned at gcc dot gnu dot org
ReportedBy: steve dot chapel at a2pg dot com
GCC build triplet: i386-redhat-linux
GCC host triplet: i3
--- Comment #30 from steve dot chapel at a2pg dot com 2008-11-18 12:59
---
Although bug 38122 causes NONMEM to not run as is, all it takes is a simple
one-line change to get it to run normally on Linux.
This bug, on the other hand, makes it effectively impossible to run NONMEM
--- Comment #28 from steve dot chapel at a2pg dot com 2008-11-17 15:01
---
I'm changing the summary of this bug report to better indicate the problem that
the patch fixes.
Could we get the patch into gfortran 4.5? There is discussion on the NONMEM
users mailing list about how t
--- Comment #2 from steve dot chapel at a2pg dot com 2008-11-14 20:19
---
It's not a bug in my program. It's a bug in NONMEM VI. That is, assuming that
/dev/tty and /dev/null are files, which they're not. They're devices.
Regardless, it's code that runs in an o
