From owner-freebsd-bugs@FreeBSD.ORG Wed Mar 26 09:56:48 2003 Return-Path: Delivered-To: freebsd-bugs@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id EFD2437B404; Wed, 26 Mar 2003 09:56:48 -0800 (PST) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.208.78.105]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6B3F243FE3; Wed, 26 Mar 2003 09:56:48 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: from troutmask.apl.washington.edu (localhost [127.0.0.1]) h2QHumPR036587; Wed, 26 Mar 2003 09:56:48 -0800 (PST) (envelope-from kargl@troutmask.apl.washington.edu) Received: (from kargl@localhost)h2QHumLP036586; Wed, 26 Mar 2003 09:56:48 -0800 (PST) From: "Steven G. Kargl" Message-Id: <200303261756.h2QHumLP036586@troutmask.apl.washington.edu> In-Reply-To: <200303261749.h2QHnohP020333@freefall.freebsd.org> To: Gerald Pfeifer Date: Wed, 26 Mar 2003 09:56:47 -0800 (PST) X-Mailer: ELM [version 2.4ME+ PL99b (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII X-Spam-Status: No, hits=-6.5 required=5.0 tests=IN_REP_TO,QUOTED_EMAIL_TEXT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-bugs@FreeBSD.org Subject: Re: gnu/38594: Fortan program don't link post gcc-3.1 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 26 Mar 2003 17:56:49 -0000 Gerald Pfeifer said: > Synopsis: Fortan program don't link post gcc-3.1 > > State-Changed-From-To: analyzed->feedback > State-Changed-By: gerald > State-Changed-When: Wed Mar 26 09:48:44 PST 2003 > State-Changed-Why: > As far as I can see this has been fixed on 5-CURRENT in the meantime (and > also doesn't appear to be a problem on 4.7). Can you confirm this? > > http://www.freebsd.org/cgi/query-pr.cgi?pr=38594 > The problem is fixed with the caveat that you need to read the audit trail. The last email in the audit trail is from David O'Brien. He proposed a much more extensive patch, but did not commit it. I believe he left the PR open to document this patch. -- Steve http://troutmask.apl.washington.edu/~kargl/