From owner-freebsd-arm@FreeBSD.ORG Wed May 21 19:28:12 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 5CF6DB00; Wed, 21 May 2014 19:28:12 +0000 (UTC) Received: from zibbi.meraka.csir.co.za (zibbi.meraka.csir.co.za [IPv6:2001:4200:7000:2::1]) by mx1.freebsd.org (Postfix) with ESMTP id F2F36276F; Wed, 21 May 2014 19:28:11 +0000 (UTC) Received: by zibbi.meraka.csir.co.za (Postfix, from userid 3973) id 09CE9B828; Wed, 21 May 2014 21:28:08 +0200 (SAST) Date: Wed, 21 May 2014 21:28:07 +0200 From: John Hay To: Adrian Chadd Subject: Re: MK_ARM_EABI to retire in current Message-ID: <20140521192807.GA48338@zibbi.meraka.csir.co.za> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 May 2014 19:28:12 -0000 On Mon, May 19, 2014 at 09:50:21AM -0700, Adrian Chadd wrote: > isn't eabi on the xscale still broken? It might still be broken. But there are more brokenness than that. :-( By defining WITHOUT_ARM_EABI=yes 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. John > > > -a > > > On 19 May 2014 08:40, Warner Losh 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? > > > > Warner > > > > _______________________________________________ > > 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"