From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugs-return-344611-listarch-gcc-bugs=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 25091 invoked by alias); 24 Jan 2011 23:29:41 -0000
Received: (qmail 25015 invoked by uid 22791); 24 Jan 2011 23:29:40 -0000
X-SWARE-Spam-Status: No, hits=-2.8 required=5.0	tests=ALL_TRUSTED,AWL,BAYES_00,TW_BG
X-Spam-Check-By: sourceware.org
Received: from localhost (HELO gcc.gnu.org) (127.0.0.1)    by sourceware.org (qpsmtpd/0.43rc1) with ESMTP; Mon, 24 Jan 2011 23:29:36 +0000
From: "joseph at codesourcery dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug libfortran/46607] [4.6 Regression] libgfortran relocated install fails
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: libfortran
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: joseph at codesourcery dot com
X-Bugzilla-Status: NEW
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: 4.6.0
X-Bugzilla-Changed-Fields:
Message-ID: <bug-46607-4-xgH0GR0GEJ@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-46607-4@http.gcc.gnu.org/bugzilla/>
References: <bug-46607-4@http.gcc.gnu.org/bugzilla/>
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
Content-Type: text/plain; charset="UTF-8"
MIME-Version: 1.0
Date: Mon, 24 Jan 2011 23:45:00 -0000
Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc-bugs.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-help@gcc.gnu.org>
Sender: gcc-bugs-owner@gcc.gnu.org
X-SW-Source: 2011-01/txt/msg02550.txt.bz2

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

--- Comment #6 from joseph at codesourcery dot com <joseph at codesourcery dot com> 2011-01-24 23:29:27 UTC ---
That would not be an appropriate use of WONTFIX; WONTFIX is for cases such 
as bugs in a target that has been removed.  It's a clear bug in libtool; 
SUSPENDED might be more appropriate for things waiting on a libtool fix.

I would note incidentally a suggestion (comment #3) to work around the 
general libtool bug on MinGW by stopping it relinking on MinGW.  I don't 
believe there's any good reason for it to be relinking for GCC builds to 
ELF targets either, so perhaps stopping relinking there would help avoid 
this problem in many more cases.