From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7238 invoked by alias); 31 Mar 2008 18:17:08 -0000 Received: (qmail 6614 invoked by uid 48); 31 Mar 2008 18:16:17 -0000 Date: Mon, 31 Mar 2008 18:17:00 -0000 Message-ID: <20080331181617.6613.qmail@sourceware.org> X-Bugzilla-Reason: CC References: Subject: [Bug bootstrap/35752] [4.3/4.4 Regression]: Combined gcc + binutils source tree doesn't bootstrap In-Reply-To: Reply-To: gcc-bugzilla@gcc.gnu.org To: gcc-bugs@gcc.gnu.org From: "hjl dot tools at gmail dot com" 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: 2008-03/txt/msg02562.txt.bz2 ------- Comment #5 from hjl dot tools at gmail dot com 2008-03-31 18:16 ------- (In reply to comment #4) > Patch seems fine, but before approving it I would like a description of why > "tries to [...] relink itself" (important part is *re*link itself), and that > description should also go in exec-tool.in. > I am not a libtool person. My best understanding is when shared library is enabled, libtool will create a shell script, ld-new, and the real executable as .libs/ld-new. But .libs/ld-new isn't suitable to be used in place directly. When the ld-new shell script is run the first time, it will relink a new real linker, .libs/lt-ld-new, and use .libs/lt-ld-new instead of .libs/ld-new. I hope libtool person can provide a real explanation in exec-tool.in. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=35752