Date: Sun, 28 Sep 2014 12:18:18 +0100 From: Andrew Turner <andrew@fubar.geek.nz> To: Warner Losh <imp@bsdimp.com> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: MK_ARM_EABI to retire in current Message-ID: <20140928121818.741e7e7e@bender.lan> In-Reply-To: <C66667D9-2F5E-44E0-AF04-E9DFE70BAF5A@gmail.com> References: <C66667D9-2F5E-44E0-AF04-E9DFE70BAF5A@gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 19 May 2014 09:40:33 -0600 Warner Losh <imp@bsdimp.com> wrote: > Greetings, > > MK_ARM_EABI is going to die in current. It is the default for all > platforms currently. I’m eliminating it as a build option. It must > die because it invisibly (to uname) effects the ABI. > > So, to that end, I see two options: > > (1) Retire and remove oabi support. > (2) Retain oabi support, but change its name to armo and armoeb. > > The rough consensus of arm developers I’ve polled now, and in the > past, is that we just let oabi support die now that EABI support is > working for everybody. > > Before I pull the trigger on this, however, I must ask if anybody has > a problem with my doing option (1), and if so, what keeps you using > oabi. > > Comments? As far as I know all the problems with ARM EABI on armeb mentioned in this thread have been fixed. I think we should now retire the oabi support and remove MK_ARM_EABI. Andrew
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20140928121818.741e7e7e>