From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 4693 invoked by alias); 28 Dec 2004 15:04:56 -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 4680 invoked by uid 48); 28 Dec 2004 15:04:52 -0000 Date: Tue, 28 Dec 2004 15:04:00 -0000 Message-ID: <20041228150452.4679.qmail@sourceware.org> From: "hideishi at graduate dot chiba-u dot jp" To: gcc-bugs@gcc.gnu.org In-Reply-To: <20041228143407.19176.hideishi@graduate.chiba-u.jp> References: <20041228143407.19176.hideishi@graduate.chiba-u.jp> Reply-To: gcc-bugzilla@gcc.gnu.org Subject: [Bug bootstrap/19176] static gcc cannot be build (libgcc_eh.a required for static gcc) X-Bugzilla-Reason: CC X-SW-Source: 2004-12/txt/msg03739.txt.bz2 List-Id: ------- Additional Comments From hideishi at graduate dot chiba-u dot jp 2004-12-28 15:04 ------- (In reply to comment #2) > Really only building static is not supported on darwin. I will look into the problem but only after a week > if no one else has looked into this. Yes, I totally agree to your comment. It is not possible to create a "completely static gcc binary" on darwin. However, if gcc is built with gcc's shared libraries (i.e. --enable-shared), g++ and gfortran produces binaries that require libgcc_s.dylib for runtime. In order to distribute gfortran compiled binaries, it is troublesome to handle with libgcc_s.dylib. So, what I mean by static gcc is "gcc which produces binaries free of shared-gcc-libraries". -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=19176