From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18100 invoked by alias); 22 Jan 2010 17:44:46 -0000 Received: (qmail 18033 invoked by uid 48); 22 Jan 2010 17:44:30 -0000 Date: Fri, 22 Jan 2010 17:44:00 -0000 Message-ID: <20100122174430.18032.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug fortran/42848] compiler crashes and asks for this bug report In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "burnus at gcc dot gnu dot org" 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: 2010-01/txt/msg02755.txt.bz2 ------- Comment #1 from burnus at gcc dot gnu dot org 2010-01-22 17:44 ------- Thanks for the bug report. However, I think this a duplicate of PR 40195 which was fixed 2009-05-22. Thus, the solution is to use any GCC 4.4.x or 4.5.x newer than 22 May 2009 such as 4.4.1, 4.4.2, or 4.4.3 - or a recent 4.5 experimental version. Comment from the other bug report: "If a module file m.mod already exist, we look into it to check if it's ours; if not, we delete it and write ours. The problem is that the code doing that actually unlinks the file before closing it, which is not allowed on Windows" Thus, a work around is to delete the *.mod file(s) manually before instructing gfortran to (over)write it. -- burnus at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- Summary|compiler crashes and asks |compiler crashes and asks |for this bug report |for this bug report http://gcc.gnu.org/bugzilla/show_bug.cgi?id=42848