From owner-freebsd-mips@FreeBSD.ORG Wed May 18 00:26:26 2011 Return-Path: Delivered-To: freebsd-mips@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 758131065673 for ; Wed, 18 May 2011 00:26:26 +0000 (UTC) (envelope-from gonzo@launchpad.bluezbox.com) Received: from launchpad.bluezbox.com (hq.bluezbox.com [70.38.37.145]) by mx1.freebsd.org (Postfix) with ESMTP id 33D418FC0C for ; Wed, 18 May 2011 00:26:25 +0000 (UTC) Received: from localhost ([127.0.0.1]) by launchpad.bluezbox.com with esmtpsa (TLSv1:CAMELLIA256-SHA:256) (Exim 4.73 (FreeBSD)) (envelope-from ) id 1QMUal-000Gqg-EC for freebsd-mips@freebsd.org; Tue, 17 May 2011 17:26:24 -0700 Message-ID: <4DD31231.5010000@freebsd.org> Date: Tue, 17 May 2011 17:26:25 -0700 From: Oleksandr Tymoshenko User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.17) Gecko/20110414 Thunderbird/3.1.10 MIME-Version: 1.0 To: freebsd-mips@freebsd.org References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Sender: gonzo@launchpad.bluezbox.com X-Spam-Level: ---- X-Spam-Report: Spam detection software, running on the system "hq.bluezbox.com", has identified this incoming email as possible spam. The original message has been attached to this so you can view it (if it isn't spam) or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: On 15/04/2011 9:12 AM, Artem Belevich wrote: > On Fri, Apr 15, 2011 at 5:26 AM, Andrew Duane wrote: >> I'm assuming it's a change to "ld", but it could be one of the directive scripts. I spent yesterday combing changes to the tree, and looking for any files that could have caused this. I came up empty, but then I'm not really sure what I'm looking for. Is there a toolchain person who might know? There's a good person here at Juniper, but he's on California time.... > > Pass --verbose to linker and see what's in the linker script it uses. > I suspect the issue may be somewhere there. > You can then tweak the linker script, put .interp in the right place > and pass the new script to linker with -T. > > That should get you by until proper toolchain fix is available. [...] Content analysis details: (-4.4 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.8 ALL_TRUSTED Passed through trusted hosts only via SMTP -2.6 BAYES_00 BODY: Bayesian spam probability is 0 to 1% [score: 0.0000] Subject: Re: Trouble with dynamic executables X-BeenThere: freebsd-mips@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to MIPS List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2011 00:26:26 -0000 On 15/04/2011 9:12 AM, Artem Belevich wrote: > On Fri, Apr 15, 2011 at 5:26 AM, Andrew Duane wrote: >> I'm assuming it's a change to "ld", but it could be one of the directive scripts. I spent yesterday combing changes to the tree, and looking for any files that could have caused this. I came up empty, but then I'm not really sure what I'm looking for. Is there a toolchain person who might know? There's a good person here at Juniper, but he's on California time.... > > Pass --verbose to linker and see what's in the linker script it uses. > I suspect the issue may be somewhere there. > You can then tweak the linker script, put .interp in the right place > and pass the new script to linker with -T. > > That should get you by until proper toolchain fix is available. This patch should fix it: http://people.freebsd.org/~gonzo/patches/elf64.diff This bug was introduced due to some change in ldscripts generation logic. I'm not sure if it's proper fix. May be someone with better toolchain knowledge will suggest something better.