From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26253 invoked by alias); 17 Jul 2007 12:50:05 -0000 Received: (qmail 26145 invoked by uid 48); 17 Jul 2007 12:49:51 -0000 Date: Tue, 17 Jul 2007 12:50:00 -0000 Message-ID: <20070717124951.26144.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug libfortran/32784] [win32] Using 'con' as assigned file generates Fortran runtime error: File 'con' does not exist In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "steven dot chapel at sbcglobal dot net" Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org X-SW-Source: 2007-07/txt/msg01855.txt.bz2 ------- 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