Re: HEADS UP: arm ports now building EABI by default

[Alan Barrett <apb%cequrux.com@localhost>]

On Tue, 05 Aug 2014, Greg Troxel wrote:
> I just updated and built, and got
>
> ERROR: No MACHINE_ARCH provided
> *** BUILD ABORTED ***
> ERROR: './build.sh -m evbarm -j8 -x -u -U -O /usr/obj/gdt-current/evbarm
> -T /usr/obj/gdt-current/tools -D /usr/obj/gdt-current/destdir/evbarm -R
> /usr/obj/gdt-current/releasedir -X /u0/n0/gdt/NetBSD-current/xsrc
> release' failed

That's unexpected.  Build.sh used to have:

MACHINE=evbarm         MACHINE_ARCH=arm        ALIAS=evbarm-el DEFAULT

and from revision 1.286 it now has:

MACHINE=evbarm         MACHINE_ARCH=earm       ALIAS=evbearm-el DEFAULT

Either way, when build.sh is passed "-m evbarm" without "-a", it
is supposed to use that DEFAULT line to set MACHINE_ARCH.

There seems to be a bug in build.sh where a DEFAULT that is not 
the first line for its MACHINE is not parsed properly.  I'll fix 
that soon.

> so I have a few questions:
>
> 1) This is with passing -m but not -a.   I see in BUILDING that evbarm is
> basically not allowed as -m without -a, and this is a change from
> before.  Perhaps a note belongs in updating.

I think BUILDING is out of date with respect to permitted -m/-a options.
For the definitive list, search for valid_MACHINE_ARCH in build.sh.

Both BUILDING and UPDATING should probably be updated for the recent
changes.

> 2) Why doesn't evbarm default to the endianness that everybody wants to
> use?  My impression is that there is a standard endianness, and that
> it's sufficiently standard that I am so far ignorant of which it is,
> even though I've booted netbsd on a rpi.

Once build.sh is fixed, the default will be MACHINE_ARCH=evbearm-el.

> 3) BUILDING doesn't address the eabi/oabi in the examples.  Maybe that's
> ok, but I don't see it in http://wiki.netbsd.org/ports/evbarm/

It would be nice if somebody documented all this.

--apb (Alan Barrett)