Date: Thu, 27 Nov 2014 21:27:58 -0500 From: Ed Maste <emaste@freebsd.org> To: Baptiste Daroussin <bapt@freebsd.org> Cc: toolchain@freebsd.org Subject: Re: Using more elftoolchain tools? Message-ID: <CAPyFy2BMLc7otf_27NHT0-e4m5fwzbES76cQQyroFvDXM_NyDQ@mail.gmail.com> In-Reply-To: <20141124000947.GK68776@ivaldir.etoilebsd.net> References: <20141124000947.GK68776@ivaldir.etoilebsd.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On 23 November 2014 at 19:09, Baptiste Daroussin <bapt@freebsd.org> wrote: > Hi all, > > From what I can see on the elftoolchain website, they do have working > replacement for: > - size(1) > - addr2line(1) > - strings(1) > - nm(1) > - strip(1) > > Does anyone knows if there are known issues with those? or if they are viable > replacement for the version we have in base? > > I'm planning to spend a bit of time on those (I think emaste@ is already working > on strip(1) so I'll skip that one). I'll save you the effort, since it was easy to add the rest after getting the first one incorporated into our build. The set above are in code review at https://reviews.freebsd.org/D1224. It adds a WITH_ELFTOOLCHAIN_TOOLS knob to enable building them instead of binutils. I have a -current VM built with that enabled and it passes basic sanity tests. I know that at elftoolchain is missing some required functionality for MIPS at least, but I don't think it'll be hard to add. What I'd like to do is commit the change in D1224 after a little more refinement, then call for broader testing and a ports exp run. We can enable WITH_ELFTOOLCHAIN_TOOLS by default on a per-architecture basis until it works properly everywhere. -Ed
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAPyFy2BMLc7otf_27NHT0-e4m5fwzbES76cQQyroFvDXM_NyDQ>