From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19805 invoked by alias); 15 Dec 2004 22:54:57 -0000 Mailing-List: contact gcc-bugs-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Archive: List-Post: List-Help: Sender: gcc-bugs-owner@gcc.gnu.org Received: (qmail 19778 invoked by uid 48); 15 Dec 2004 22:54:48 -0000 Date: Wed, 15 Dec 2004 22:54:00 -0000 Message-ID: <20041215225448.19777.qmail@sourceware.org> From: "hjl at lucon dot org" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041026004311.18153.hjl@lucon.org> References: <20041026004311.18153.hjl@lucon.org> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug target/18153] [3.4/4.0 Regression] -static-libgcc links in libunwind.so.7 X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg02262.txt.bz2 List-Id: ------- Additional Comments From hjl at lucon dot org 2004-12-15 22:54 ------- We tried very hard to provide -static-libgcc which links against libgcc.a and libgcc_eh.a instead of libgcc.a and libgcc_s.so.1. The main purpose of -static-libgcc is to link in the copy of the unwind stuff. Introduction of libunwind moved the unwind stuff from libgcc_s.so.1/libgcc_eh.a into libunwind.so.7/libunwind.a. With libunwind, -static-libgcc should still link in the copy of the unwind stuff, instead of from a shared library. Otherwise, applications which expect that behavior of -static-libgcc won't work correctly. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=18153