Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 21 May 2014 14:01:42 -0600
From:      Warner Losh <imp@bsdimp.com>
To:        John Hay <jhay@meraka.org.za>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: MK_ARM_EABI to retire in current
Message-ID:  <95AD97BA-AA48-4BBF-845C-D0CB585ACAA3@bsdimp.com>
In-Reply-To: <20140521192807.GA48338@zibbi.meraka.csir.co.za>
References:  <C66667D9-2F5E-44E0-AF04-E9DFE70BAF5A@gmail.com> <CAJ-VmonSHCyD-8jpK0EPkctVwpJ%2BPu4dfBkvATdOS3yrN4ttVg@mail.gmail.com> <20140521192807.GA48338@zibbi.meraka.csir.co.za>

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

--Apple-Mail=_A8FC32A3-D51C-4D62-B98E-152C950A91E4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii


On May 21, 2014, at 1:28 PM, John Hay <jhay@meraka.org.za> wrote:

> On Mon, May 19, 2014 at 09:50:21AM -0700, Adrian Chadd wrote:
>> isn't eabi on the xscale still broken?
>=20
> It might still be broken. But there are more brokenness than that. :-(
> By defining WITHOUT_ARM_EABI=3Dyes in src.conf, I can get an AVILA =
kernel
> built that boots with src from head at around mid December. Latest 10
> and head just give no output, with or without WITHOUT_ARM_EABI =
defined.

Does the same thing happen with make.conf instead of src.conf?

Warner

> John
>=20
>>=20
>>=20
>> -a
>>=20
>>=20
>> On 19 May 2014 08:40, Warner Losh <imp@bsdimp.com> wrote:
>>> Greetings,
>>>=20
>>> 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.
>>>=20
>>> So, to that end, I see two options:
>>>=20
>>> (1) Retire and remove oabi support.
>>> (2) Retain oabi support, but change its name to armo and armoeb.
>>>=20
>>> 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.
>>>=20
>>> 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.
>>>=20
>>> Comments?
>>>=20
>>> Warner
>>>=20
>>> _______________________________________________
>>> freebsd-arm@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>>> To unsubscribe, send any mail to =
"freebsd-arm-unsubscribe@freebsd.org"
>> _______________________________________________
>> freebsd-arm@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-arm
>> To unsubscribe, send any mail to =
"freebsd-arm-unsubscribe@freebsd.org"


--Apple-Mail=_A8FC32A3-D51C-4D62-B98E-152C950A91E4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP using GPGMail

-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - https://gpgtools.org

iQIcBAEBCgAGBQJTfQYmAAoJEGwc0Sh9sBEAxXkP/RBwo9yg97eBGf07SITcTCt4
85josysqg4FDKUWYa0fLoZRZ3d6vUzKXvAlMh2GzsuL9rNRh1wWT2me95PjlfUrE
SSctSPe0e2CQbmDrPvuerQe++R5jPI/5+T9UQJSxC+Ij0QolBur+sKxAhPdSIuAs
rlyqqnTwF0qSJK5lhJk3I36pSz1BypNyzTZcJopB6HV7vfU5nEJ/cLMcqxOOiNKz
mgze6CD+7LD2b0h0Ym3Iy7HwVKD5rW5HHLxByDWvpJL+myEMzfBLfmCXfOscrkPh
UtqAwhGcXf3DYt8ySLg8+r/mgpbLAkt0CJLpI1SBUW/QMA/UpAqKtKWDgXUx/BN+
X+RR95JxkPnPNCmPyHv5nLV8dPnI3w+S00sln70eWEpE+bpD+G1mbyL8VCYb/Bad
WMWi4MGeZyrmYeZfX+PK+1tQQky5V4aQm5+d4LAZehVD5UosvimwKW9GMESHh5yr
3Y9qpxp7d96jX1M+8ap9OrkHEriVLHB7ToM0V5bPxrppZWhwthYujlt4ZCtFWDP9
L3makivhX558s+PtRZ5D3irq7EDh369CkSulL4XDZZIFcVjcrYDBY6qD8HaP59KS
0QMCEKTqfsP2KLFTJJPrPUBCKjljgo5bpOR5V3m+NUoT2zFc4NMXezGAzl4UI/sK
vNkwO+cLgs15TjoynPat
=lheu
-----END PGP SIGNATURE-----

--Apple-Mail=_A8FC32A3-D51C-4D62-B98E-152C950A91E4--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?95AD97BA-AA48-4BBF-845C-D0CB585ACAA3>