[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-08-14 Thread jvdelisle at gcc dot gnu dot org


--- Comment #37 from jvdelisle at gcc dot gnu dot org  2009-08-15 00:50 
---
Fixed on 4.5.  


-- 

jvdelisle at gcc dot gnu dot org changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution||FIXED


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-07-22 Thread jvdelisle at gcc dot gnu dot org


--- Comment #35 from jvdelisle at gcc dot gnu dot org  2009-07-23 00:59 
---
Subject: Bug 32784

Author: jvdelisle
Date: Thu Jul 23 00:58:46 2009
New Revision: 149970

URL: http://gcc.gnu.org/viewcvs?root=gccview=revrev=149970
Log:
2009-07-22  Jerry DeLisle  jvdeli...@gcc.gnu.org

PR libfortran/32784
* unix.c (regular_file): Check for CONIN$ CONOUT$, and CONERR$ and open
the respective /dev/conin or /dev/conout devices.  This is Cygwin
specific.

Modified:
trunk/libgfortran/ChangeLog
trunk/libgfortran/io/unix.c


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-07-19 Thread jvdelisle at gcc dot gnu dot org


--- Comment #34 from jvdelisle at gcc dot gnu dot org  2009-07-19 13:43 
---
Cygwin only patch submitted. MingW next.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-06-13 Thread jvdelisle at gcc dot gnu dot org


--- Comment #33 from jvdelisle at gcc dot gnu dot org  2009-06-14 00:59 
---
Patch tested on Cygwin and submitted for approval.  Need a tester for mingw.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-06-04 Thread steven at gcc dot gnu dot org


--- Comment #32 from steven at gcc dot gnu dot org  2009-06-04 12:54 ---
Jerry, was the patch submitted already?


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2009-04-11 Thread jvdelisle at gcc dot gnu dot org


--- Comment #31 from jvdelisle at gcc dot gnu dot org  2009-04-11 16:45 
---
now that 4.5 branch is alive I will try once again to submit patch for
approval.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2008-11-18 Thread steve dot chapel at a2pg dot com


--- 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
normally on Windows, that is, sending output to the console output.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2008-11-17 Thread steve dot chapel at a2pg dot com


--- 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 to get NONMEM to work with gfortran on Windows,
and users are waiting for a resolution to this issue.

Thanks.


-- 

steve dot chapel at a2pg dot com changed:

   What|Removed |Added

Summary|[win32] Using 'con' or  |[win32] Using 'CONOUT$',
   |'CONOUT$' as assigned file  |'CONIN$', or 'CONERR$' as
   |generates Fortran runtime   |assigned file generates
   |error: File 'con' does not  |Fortran runtime error: Bad
   |exist   |file descriptor


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784



[Bug libfortran/32784] [win32] Using 'CONOUT$', 'CONIN$', or 'CONERR$' as assigned file generates Fortran runtime error: Bad file descriptor

2008-11-17 Thread jvdelisle at gcc dot gnu dot org


--- Comment #29 from jvdelisle at gcc dot gnu dot org  2008-11-18 03:02 
---
Steve, I will try but we also still have the issue of 38122 as well.


-- 


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=32784