Date: Tue, 17 May 2011 17:26:25 -0700 From: Oleksandr Tymoshenko <gonzo@freebsd.org> To: freebsd-mips@freebsd.org Subject: Re: Trouble with dynamic executables Message-ID: <4DD31231.5010000@freebsd.org> In-Reply-To: <BANLkTimp7inXtFN2O_Pw9AZ_CA5nb9ecKQ@mail.gmail.com> References: <AC6674AB7BC78549BB231821ABF7A9AEB53018A09F@EMBX01-WF.jnpr.net> <BANLkTi=Jw=q5sUVs8-sEG09nSHwFbMFKjw@mail.gmail.com> <AC6674AB7BC78549BB231821ABF7A9AEB52F19511B@EMBX01-WF.jnpr.net> <BANLkTimp7inXtFN2O_Pw9AZ_CA5nb9ecKQ@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 15/04/2011 9:12 AM, Artem Belevich wrote: > On Fri, Apr 15, 2011 at 5:26 AM, Andrew Duane<aduane@juniper.net> 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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4DD31231.5010000>