Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 27 Jan 2017 13:39:21 -0800
From:      John Baldwin <jhb@freebsd.org>
To:        Ed Maste <emaste@freebsd.org>
Cc:        "src-committers@freebsd.org" <src-committers@freebsd.org>, "svn-src-all@freebsd.org" <svn-src-all@freebsd.org>, "svn-src-head@freebsd.org" <svn-src-head@freebsd.org>
Subject:   Re: svn commit: r312857 - head
Message-ID:  <1890872.SdRWTz4Mbe@ralph.baldwin.cx>
In-Reply-To: <CAPyFy2A4PpGYm5pnz-iEbh4b0BLtOT0GtyBQToQkev1RDOCrYQ@mail.gmail.com>
References:  <201701270343.v0R3hIww068402@repo.freebsd.org> <5921766.B6ayWRhOVb@ralph.baldwin.cx> <CAPyFy2A4PpGYm5pnz-iEbh4b0BLtOT0GtyBQToQkev1RDOCrYQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Friday, January 27, 2017 03:36:01 PM Ed Maste wrote:
> On 27 January 2017 at 14:38, John Baldwin <jhb@freebsd.org> wrote:
> >
> > Which external toolchain?  Building with GCC 6 and binutils from ports worked
> > fine for me?
> 
> This was using the mips64-xtoolchain-gcc package and
> CROSS_TOOLCHAIN=mips64-gcc. It appears that it picked up the host's nm
> while building compat32.
> 
> If you are building on a FreeBSD 11 or -CURRENT host it will work even
> if it gets the host nm, because /usr/bin/nm is ELF Tool Chain's and
> includes support for all architectures, but I'm building on 10.x and
> the GNU nm there only handles x86 objects.

Ah, yes I am testing on 11.  Good catch then.

-- 
John Baldwin



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?1890872.SdRWTz4Mbe>