[Bug fortran/32784] New: Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[Bug fortran/32784] New: Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

When this program is compiled and run:

       character*72 fnint
       data fnint /'con'/
       i=index(fnint,' ');
       open(unit=29,file=fnint(1:i-1),status='new')
       write(29,100)
100    format('1Hello, world!')
       end

It generates this error message:

At line 4 of file bug.for (unit = 29, file = '')
Fortran runtime error: File 'con' does not exist

The same error message is generated when status='new' is omitted.

Here is the info for the compiler I used (it's FX's prebuilt mingw binary):

Using built-in specs.
Target: i386-pc-mingw32
Configured with: ../trunk/configure --prefix=/mingw
--enable-languages=c,fortran
 --with-gmp=/home/coudert/local --disable-nls --with-ld=/mingw/bin/ld
--with-as=
/mingw/bin/as --disable-werror --enable-bootstrap --enable-threads
--build=i386-
pc-mingw32 --disable-shared --enable-libgomp
Thread model: win32
gcc version 4.3.0 20070706 (experimental)

I am not able to run NONMEM <http://c255.ucsf.edu/nonmem1.html> built with
gfortran because of this bug.


-- 
           Summary: Using 'con' as assigned file generates Fortran runtime
                    error: File 'con' does not exist
           Product: gcc
           Version: 4.3.0
            Status: UNCONFIRMED
          Severity: major
          Priority: P3
         Component: fortran
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: steven dot chapel at sbcglobal dot net


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[pinskia at gcc dot gnu dot org]

------- Comment #1 from pinskia at gcc dot gnu dot org  2007-07-16 22:15 -------
This is a windows only issue as using special files (device files) under
GNU/Linux works just fine.


-- 

pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|major                       |normal
          Component|fortran                     |libfortran
 GCC target triplet|                            |i386-
                   |                            |i686-pc-mingw3
            Summary|Using 'con' as assigned file|[win32] Using 'con' as
                   |generates Fortran runtime   |assigned file generates
                   |error: File 'con' does not  |Fortran runtime error: File
                   |exist                       |'con' does not exist


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #2 from jvdelisle at gcc dot gnu dot org  2007-07-17 02:25 -------
Under Cygwin we get:

$ ./a.exe 
At line 4 of file test.f90 (unit = 29, file = '')
Fortran runtime error: File 'con' already exists

con is a reserved device name from MS DOS:

See http://www.tcs.org/ioport/jul98/driver-3.htm

Under cygwin, if I just try to cat to con:

$ cat test.f90 | con
-bash: /home/Jerry/bin/con: Bad file descriptor

This problem has nothing to do with gfortran.  I am afraid you will have to
edit and change the name to something other than 'con'

Even if I try to edit a file named con.f with vi it locks up vi.

Unless someone has a better idea, I suggest closing this bug as invalid.  How
difficult is it to change that name from 'con' to something else? 


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[pinskia at gcc dot gnu dot org]

------- Comment #3 from pinskia at gcc dot gnu dot org  2007-07-17 02:37 -------
Except con should be the console aka /dev/pts/?? .


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

------- Comment #4 from steven dot chapel at sbcglobal dot net  2007-07-17 02:52 -------
What name should I change 'con' to so that the write statement writes to the
console? I asked on the gfortran mailing list, and I was told to submit this
bug report. If it's as simple as changing the name, let me know and I can code
it in a change to NONMEM so that I can use gfortran to compile NONMEM.

It seems that con should work though. At the command prompt in Windows XP, the
following commands work just as I'd expect:
C:\> copy afile con
C:\> copy con anewfile
C:\> dir > con

Piping to con doesn't work, because con is a device, not a process:
C:\> dir | con
' ' is not recognized as an internal or external command,
operable program or batch file.


-- 

steven dot chapel at sbcglobal dot net changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
 GCC target triplet|i386-                       |i386-
                   |i686-pc-mingw3              |


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #5 from jvdelisle at gcc dot gnu dot org  2007-07-17 04:38 -------
I will investigate further, but if all its trying to do is WRITE to the console
use WRITE(unit=6) and don't give it a filename at all. You don't even need to
OPEN it.  It will be OPENed implicitly for you.  READ (unit=5) to read from the
console.

Will this work for you?

In the mean time I will go look at this code for this application a little.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[dannysmith at users dot sourceforge dot net]

------- Comment #6 from dannysmith at users dot sourceforge dot net  2007-07-17 08:43 -------
(In reply to comment #4)
> What name should I change 'con' to so that the write statement writes to the
> console? 

I think it should be CONOUT$ (ie you had it right the first time).
The following works with g77 (and the old Intel Fortran ivf compiler)

      open(unit=29,file='CONOUT$')
      write(29,100)
100   format('1Hello, world!')
      end 

The following works in C

#include <fcntl.h>
#include <sys/stat.h>
#include <stdlib.h>

int main()
{
 int fd= _open ("CONOUT$", _O_RDWR));
  if (fd >= 0)
   _write (fd, "Hello world", sizeof ("Hello world"));   
 return 0;
}


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

------- Comment #7 from steven dot chapel at sbcglobal dot net  2007-07-17 12:49 -------
(In reply to comment #5)
> if all its trying to do is WRITE to the console
> use WRITE(unit=6) and don't give it a filename at all.
> 
> Will this work for you?

Not really. It's been written that way so that you can easily change where the
output goes by changing one line of code. Hardcoding the output to go to the
console defeats the purpose. I'm also not the author of the code, and I don't
want to have to manually change every line of code like that in my local copy
with each release of NONMEM.

> I think it should be CONOUT$ (ie you had it right the first time).
> The following works with g77 (and the old Intel Fortran ivf compiler)

That's what it was the first time, when I got Fortran runtime error: Bad file
descriptor. That's why I changed it to con. If there's something else I can
change it to, I can fairly easily manually make that change with each release
of NONMEM because it's only one line of code.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #8 from jvdelisle at gcc dot gnu dot org  2007-07-18 02:54 -------
I can't get anything to work, but I have some ideas.


-- 

jvdelisle at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         AssignedTo|unassigned at gcc dot gnu   |jvdelisle at gcc dot gnu dot
                   |dot org                     |org
             Status|UNCONFIRMED                 |ASSIGNED
     Ever Confirmed|0                           |1
   Last reconfirmed|0000-00-00 00:00:00         |2007-07-18 02:54:22
               date|                            |


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #9 from jvdelisle at gcc dot gnu dot org  2007-07-21 19:39 -------
The following simple patch enables gfortran to run for the tet case.  I need to
get the proper #ifdef #endif condition set up and do a similar thing for CONIN$
and CONERR$ ( or whatever the windows equivalents are) and this will be all
set. I tested this on cygwin.

Index: unix.c
===================================================================
--- unix.c      (revision 126808)
+++ unix.c      (working copy)
@@ -1259,6 +1259,13 @@ regular_file (st_parameter_open *opp, un
   crflag |= O_BINARY;
 #endif

+  if (strncmp (path, "CONOUT$", 7) == 0)
+    {
+      fd = STDOUT_FILENO;
+      flags->action = ACTION_WRITE;
+      return fd;
+    }
+
   mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH;
   fd = open (path, rwflag | crflag, mode);
   if (flags->action != ACTION_UNSPECIFIED)


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #10 from jvdelisle at gcc dot gnu dot org  2007-07-21 23:08 -------
Here is a complete patch, tested on Cygwin.  I need to test on mingw.  Can
anyone help with that?

Index: unix.c
===================================================================
--- unix.c      (revision 126808)
+++ unix.c      (working copy)
@@ -81,6 +81,13 @@ Boston, MA 02110-1301, USA.  */
 #define S_IWOTH 0
 #endif

+#ifdef __CYGWIN__
+#define HAVE_DOS_CONIO
+#endif
+
+#ifdef __MINGW32__
+#define HAVE_DOS_CONIO
+#endif

 /* Unix stream I/O module */

@@ -1259,6 +1266,27 @@ regular_file (st_parameter_open *opp, un
   crflag |= O_BINARY;
 #endif

+#ifdef HAVE_DOS_CONIO
+  if (strncmp (path, "CONOUT$", 7) == 0)
+    {
+      fd = STDOUT_FILENO;
+      flags->action = ACTION_WRITE;
+      return fd;
+    }
+  if (strncmp (path, "CONIN$", 6) == 0)
+    {
+      fd = STDIN_FILENO;
+      flags->action = ACTION_READ;
+      return fd;
+    }
+  if (strncmp (path, "CONERR$", 7) == 0)
+    {
+      fd = STDERR_FILENO;
+      flags->action = ACTION_WRITE;
+      return fd;
+    }
+#endif
+
   mode = S_IRUSR | S_IWUSR | S_IRGRP | S_IWGRP | S_IROTH | S_IWOTH;
   fd = open (path, rwflag | crflag, mode);
   if (flags->action != ACTION_UNSPECIFIED)


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[dannysmith at users dot sourceforge dot net]

------- Comment #11 from dannysmith at users dot sourceforge dot net  2007-07-22 08:42 -------
(In reply to comment #10)
> Here is a complete patch, tested on Cygwin.  I need to test on mingw.  Can
> anyone help with that?
> 
      open(unit=29,file='CONOUT$')
      write(29,100)
100   format('Hello, world!')
      end

On mingw, with your patch, I get this on stdout:
Hello, world!

and this on stderr:

At line 2 of file conout.f (unit = 29, file = 'CONOUT$')
Fortran runtime error: Bad file descriptor


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #12 from jvdelisle at gcc dot gnu dot org  2007-07-22 14:21 -------
Yes, I found similar on Cygwin, so I am still at it on this one.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #13 from jvdelisle at gcc dot gnu dot org  2007-07-23 02:59 -------
Created an attachment (id=13950)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13950&action=view)
Patch to provide conio support

Danny, can you please check this new patch.  Works on Cygwin as far as I can
tell.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #14 from jvdelisle at gcc dot gnu dot org  2007-07-23 04:41 -------
Created an attachment (id=13951)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13951&action=view)
Update patch

This one does not fail when there is no filename, :)


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[dannysmith at users dot sourceforge dot net]

------- Comment #15 from dannysmith at users dot sourceforge dot net  2007-07-23 04:44 -------
(In reply to comment #13)
> Created an attachment (id=13950)
 --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=13950&action=view) [edit]
> Patch to provide conio support
> 
> Danny, can you please check this new patch.  Works on Cygwin as far as I can
> tell.
> 
Not on mingw.  If you run the app generated from conout.f  in an environ that
dup's and redirects stderr, it appears to work.  If you run from a plain
ordinary Windows console, I still get 
Hello, world! 
At line 2 of file a1.f (unit = 29, file = 'CONOUT$')
Fortran runtime error: Bad file descriptor

Try testing your cygwin-built app from DOS (with cygwin1.dll in %PATH, of
course).

Danny


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #16 from jvdelisle at gcc dot gnu dot org  2007-07-23 05:46 -------
I tried my latest updated patch in DOS terminal window as you suggested and it
works OK, provided the file name is CONOUT$.  If it is con or CON, I get an
error of file already exists.  I will think about that some more.  Maybe we
should make it match "con" with case ignored.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[dannysmith at users dot sourceforge dot net]

------- Comment #17 from dannysmith at users dot sourceforge dot net  2007-07-23 08:04 -------
(In reply to comment #16)

 Maybe we
> should make it match "con" with case ignored.


No, please. "con", "nul", "prn" (with or without suffix) are reserved device
names on windows.  
(eg "gcc -v -dM -E  nul.c" is equivalent  to gcc -v -dM -E  -xc  /dev/null)

CONOUT$ is the win32api name for console output and is used in GUI progs that
don't have  default console output.

Danny


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #18 from jvdelisle at gcc dot gnu dot org  2007-07-25 23:00 -------
More info for everyone.

Under Cygwin, reading and writing from/to /dev/conin$ and /dev/conout$
respectively works fine with gfortran now. (Thanks David Korn for info)

I think this is sufficient for Cygwin.

Under mingw, gfortran has some trouble.  I am still experimenting and testing
on mingw which I just got installed on my test machine here.  I should be able
to finish this when I get the time free to do it. 


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #19 from jvdelisle at gcc dot gnu dot org  2007-07-25 23:35 -------
Regarding my comment #18 on cygwin.  There should be no dollar signs in the
device name.

Thus:  /dev/conout  and /dev/conin


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[dannysmith at users dot sourceforge dot net]

------- Comment #20 from dannysmith at users dot sourceforge dot net  2007-07-26 00:34 -------
(In reply to comment #18)
> 
> Under mingw, gfortran has some trouble.  I am still experimenting and testing
> on mingw which I just got installed on my test machine here.  I should be able
> to finish this when I get the time free to do it. 
> 

For complete testing, I suppose you we need to test GUI progs where
stdout/stdin/stderr default to bitbuckets,  A windows GUI prog is compiled with
"gcc/gfortran  -mwindows ..."
IMO, this is not a critical bug, so don't fritter too much time on it.  
'CONOUT$' etc are  non-portable identifiers that should probably only be used
in w32api context.

Danny 


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #21 from jvdelisle at gcc dot gnu dot org  2007-08-11 15:38 -------
Changing to enhancement.  STANDARD I/O works fine.


-- 

jvdelisle at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Severity|normal                      |enhancement


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

------- Comment #22 from steven dot chapel at sbcglobal dot net  2007-08-11 15:54 -------
This is *not* an enhancement. It is a *regression* that causes an important
application not to work.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[kargl at gcc dot gnu dot org]

------- Comment #23 from kargl at gcc dot gnu dot org  2007-08-11 16:11 -------
(In reply to comment #22)
> This is *not* an enhancement. It is a *regression* that causes an important
> application not to work.
> 

A regression with respect to what version of gfortran?  A scan of the
audit trail did not reveal the working version.

If the important application is that important, you can always roll
up your sleeves and help fix the problem.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[jvdelisle at gcc dot gnu dot org]

------- Comment #24 from jvdelisle at gcc dot gnu dot org  2007-08-11 17:49 -------
Sorry for the spin up here.  I have a patch ready, still trying to test.


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

------- Comment #25 from steven dot chapel at sbcglobal dot net  2007-08-12 22:45 -------
> A regression with respect to what version of gfortran?  A scan of the
> audit trail did not reveal the working version.

The code above works with gcc 3.4.5.

> If the important application is that important, you can always roll
> up your sleeves and help fix the problem.

I suppose, but I'm just using gcc 3.4.5 for the time being. I actually busy
working on cleaning up the Getting Started instructions on the MinGW wiki
because most of the people running this application seem to be using gcc 2.95!


-- 


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

Re: [Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[Andrew Pinski]

On 12 Aug 2007 22:45:07 -0000, steven dot chapel at sbcglobal dot net
<gcc-bugzilla@gcc.gnu.org> wrote:
> The code above works with gcc 3.4.5.

Which means it worked in g77 and not in gfortran (which is new for
4.0.0).  Now we have this weird thing about how gfortran is a new
front-end and g77 was removed.  So this could go either as a
regression or really a new feature.  Also why does this program use
con anyways, shouldn't it just use the default units which are
connected to stdio/stdout anyways as they might not be connected to
the console anyways?

Thanks,
Andrew Pinski

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[pinskia at gmail dot com]

------- Comment #26 from pinskia at gmail dot com  2007-08-12 23:07 -------
Subject: Re:  [win32] Using 'con' as assigned file generates Fortran runtime
error: File 'con' does not exist

On 12 Aug 2007 22:45:07 -0000, steven dot chapel at sbcglobal dot net
<gcc-bugzilla@gcc.gnu.org> wrote:
> The code above works with gcc 3.4.5.

Which means it worked in g77 and not in gfortran (which is new for
4.0.0).  Now we have this weird thing about how gfortran is a new
front-end and g77 was removed.  So this could go either as a
regression or really a new feature.  Also why does this program use
con anyways, shouldn't it just use the default units which are
connected to stdio/stdout anyways as they might not be connected to
the console anyways?

Thanks,
Andrew Pinski


-- 


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

[Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist

[steven dot chapel at sbcglobal dot net]

------- Comment #27 from steven dot chapel at sbcglobal dot net  2007-08-12 23:23 -------
(In reply to comment #26)
> Which means it worked in g77 and not in gfortran.

I don't know if it never worked in gfortran. Until a few days ago, the only
MinGW build of gfortran was a trunk version of 4.3.0. I haven't tested gfortran
4.2.1 or any other version yet.

> Also why does this program use
> con anyways, shouldn't it just use the default units which are
> connected to stdio/stdout anyways as they might not be connected to
> the console anyways?

The program opens a large number of file units, some of them actual files, and
one of them 'con'. I believe one of them is also 'nul'. These are defined at
one place in the program that you can change (similar to the code in the sample
program in the first comment), so that at compile time you can change the names
of the files. That's just the way the program is written, and not being the
author, I can't reasonably change it all around to use the default units
instead.


-- 


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

[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

[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

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

[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

[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

[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

[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

[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

[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=gcc&view=rev&rev=149970
Log:
2009-07-22  Jerry DeLisle  <jvdelisle@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

[jvdelisle at gcc dot gnu dot org]

------- Comment #36 from jvdelisle at gcc dot gnu dot org  2009-08-14 21:10 -------
Subject: Bug 32784

Author: jvdelisle
Date: Fri Aug 14 21:10:06 2009
New Revision: 150779

URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=150779
Log:
2009-08-14  Jerry DeLisle  <jvdelisle@gcc.gnu.org>

        PR libfortran/32784
        io/unix.c (regular_file): Add support for CONIO on mingw.

Modified:
    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

[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