i think we're missing -m evbarm -a earmv4 builds, which should
create an evbarm set targetting our speical eabi on armv4, and
that "normal" earm builds should elide them. shouldn't be too
hard, we already collect them eg, into $EVBARM_BOARDS.armv4.
thanks for pointing that out!
.mrg.
> >netbsd 9 will ship without any targets with oabi as the
> >default, and most of the existing ports were already
> >switched to eabi (epoc32 and acorn32 only.)
> >
> >as part of this, i'm going to stop providing the ability
> >to build any arm with oabi -- turn off the MKCOMPAT for
> >all arm
matthew green wrote:
>netbsd 9 will ship without any targets with oabi as the
>default, and most of the existing ports were already
>switched to eabi (epoc32 and acorn32 only.)
>
>as part of this, i'm going to stop providing the ability
>to build any arm with oabi -- turn off the MKCOMPAT for
hi folks.
netbsd 9 will ship without any targets with oabi as the
default, and most of the existing ports were already
switched to eabi (epoc32 and acorn32 only.)
as part of this, i'm going to stop providing the ability
to build any arm with oabi -- turn off the MKCOMPAT for
all arm ports, so
