From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 14247 invoked by alias); 24 Jan 2010 08:02:45 -0000 Received: (qmail 9490 invoked by uid 48); 24 Jan 2010 07:59:27 -0000 Date: Sun, 24 Jan 2010 08:02:00 -0000 Message-ID: <20100124075927.9489.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug target/39947] Shared libgcc getting clobbered for multilib builds In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "jon_y at users dot sourceforge 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: 2010-01/txt/msg02813.txt.bz2 ------- Comment #5 from jon_y at users dot sourceforge dot net 2010-01-24 07:59 ------- Ping, We need to get this fixed ASAP. Probably involving the libtool devs as well. I propose the following naming scheme. libw64stdc++-6.dll (64bit mingw-w64) libw32stdc++-6.dll (32bit mingw-w64) libstdc++-6.dll (mingw.org) libtool can check -dumpmachine for the vendor key. Comments? -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39947