Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 28 Sep 2014 10:19:09 -0700
From:      Warner Losh <imp@bsdimp.com>
To:        Andrew Turner <andrew@fubar.geek.nz>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: MK_ARM_EABI to retire in current
Message-ID:  <E594E133-F3A7-46EA-BCEF-B2B62B5FCE4C@bsdimp.com>
In-Reply-To: <20140928121818.741e7e7e@bender.lan>
References:  <C66667D9-2F5E-44E0-AF04-E9DFE70BAF5A@gmail.com> <20140928121818.741e7e7e@bender.lan>

index | next in thread | previous in thread | raw e-mail

[-- Attachment #1 --]

On Sep 28, 2014, at 4:18 AM, Andrew Turner <andrew@fubar.geek.nz> wrote:

> 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.

I’m game. I think we should move forward on option #1. We’ve had no issues
in the 10.1 release related to this that I’m aware of. Should there be no further
objections, my plan is to move forward with this later this week.

Warner

[-- Attachment #2 --]
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJUKEMNAAoJEGwc0Sh9sBEAkMIP/1ceBEbvJuPZzpMKEDNGxALa
N8fQfEL0gwqOeUQPTKGvCmgQN8LtpaZToYRZIZh3KBoknYDVd/UgV4sbRgpVCScb
fXyGruHAfbXpWPaDpRCC6Sv9STnyVrstGVnhps6DsKKG1ai49W8/yWnDQ66uPY6z
YVF465/6yS8zQAmMCF2j3Zc7xum19Towsvp0ptRJW67tzl+N9BBdsv+SvQqHXmAY
ocMLLUj65a5fKgFGXFn6fYLjd7KSt2NAE5uFzU4Uy7PEjNS59JcuSaAc2atg/x0F
Esn6oEik1bFk2wCBVqcvgakVgztrzY9OQ3LqfthUQGYTS7v+VW2BT6HBA/aganRO
sT/XfuiGz0dQqOxE/6u80jpSEjKM48fljLTYv2p1+brqBtSPqPL1fNXnWdf6rqV0
/E7lK+/HcYTvlM3ACZ9Wdc7ssS4SlEMrMa7pR0pga5Fcfpz4uwHoFkukIdtNZsif
il2n5IdiPVXa4HSWt5wxXvWkzu2bI0SO7NnaQ50Vyt/oNjtIIY53CFSvHM6eLsRZ
Sx6evJoAzPRLGh2r/DJdxfdh6WF7neiK5kBYdELnuZGPKhpMWD0RqvNiUGjlzjfM
isIMhttuw5lPn7zN+mh9IEB16tnNG6m+8n4N5BqLTydobtvk1dO1cDoFS2RyFx4Q
z9nUQF09nQWP3b33me5b
=MuGK
-----END PGP SIGNATURE-----
help

Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E594E133-F3A7-46EA-BCEF-B2B62B5FCE4C>