Crochet Updates for RPi, BeagleBone

[Ian Lepore]

On Sat, 2015-08-08 at 10:52 -0700, Tim Kientzle wrote:
> > On Aug 6, 2015, at 4:15 PM, kah42pub <kah42pub at blarg.com> wrote:
> > 
> > On 7/19/15 18:39, Tim Kientzle wrote:
> >> I just committed changes to Crochet so that it now uses the U-Boot ports for RPi and BeagleBone (including BBB).  It already used the port for RPi2.
> > 
> > Has anyone successfully built the u-boot-rpi port recently for RPI-B?
> 
> I just tried building each U-Boot port with an upgraded -CURRENT system (including packages).  Looks like anything based on U-Boot older than 2015.04 is broken:
> 
> The following did not build for me:
>    u-boot-beaglebone (uses U-Boot 2014.10)
>    u-boot-cubox-hummingbird (based on U-Boot 2013.10)
>    u-boot-duovero (based on U-Boot 2014.10)
>    u-boot-pandaboard (uses U-Boot 2014.10)
>    u-boot-rpi  (based on U-Boot 2013.01)
>    u-boot-wandboard (based on U-Boot 2013.10)
> 
> These did build:
>    u-boot-bananapi (uses U-Boot 2015.04)
>    u-boot-cubieboard (uses U-Boot 2015.04)
>    u-boot-cubieboard2 (uses U-Boot 2015.04)
>    u-boot-rpi2 (uses U-boot 2015.04)

The cross-compiler port used for u-boot got upgraded behind our backs to
gcc5, and that breaks all the u-boots that are based on older
vendor-supplied sources.  I have a new arm-none-eabi-gcc492 port ready
to go, but I'm not a ports committer, so I'm waiting for someone to
review and approve the commit.

I also plan to try and get as many of our u-boot ports as possible
updated to the latest mainline u-boot sources, but I still want to get
the gcc492 port in first because I think updating to mainline u-boot is
more than a day or two of work.

-- Ian