Date: Mon, 2 Sep 2013 11:18:20 -0700 From: Tim Kientzle <tim@kientzle.com> To: Mark R V Murray <mark@grondar.org> Cc: Takeshi Taguchi <taguchi949@gmail.com>, freebsd-arm@freebsd.org Subject: Re: What's the recipe? Message-ID: <FCBE5AA4-D3D9-4C3A-8E32-706149908C54@kientzle.com> In-Reply-To: <0AC24F9A-7AE0-4E98-BC21-273FA097AE0F@grondar.org> References: <522229C0.5030504@m5p.com> <20130901200726.ac7317a5f0ddfddcbed34484@gmail.com> <DBD761B2-0DF0-4D72-BF62-EC7D32A520DC@kientzle.com> <0AC24F9A-7AE0-4E98-BC21-273FA097AE0F@grondar.org>
index | next in thread | previous in thread | raw e-mail
On Sep 2, 2013, at 12:30 AM, Mark R V Murray <mark@grondar.org> wrote: > > CURRENT + crochet cannot build u-boot because it looks like the antique CURRENT/GCC-xdev can't handle a couple of command-line options that u-boot wants (-fstack-usage, the other is hiding), but if I remove those it eventually fails with redefinitions of things like __packed, __pure and so on (this is GCC "armv6-freebsd-gcc", not CLANG). This is very odd. I've been occupied elsewhere, so I haven't done any RPi builds recently, but I don't think anything has changed (in either the U-boot version used there or in CURRENT/GCC) since the last time I built. > I tried to hack up a u-boot port using the Beaglebone Black u-boot port as an example; that needs devel/arm-eabi-gcc which fails because of redefinition of some functions during the build. The BBB U-Boot port is badly broken for some reason and I have no idea why. (Seems to break at the point ubldr first calls into U-Boot.) I've been digging through it a little this weekend but have yet to isolate the issue. Hmmm… I haven't rebuilt devel/arm-eabi-gcc in a while; I wonder what broke that? <sigh> Timhelp
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?FCBE5AA4-D3D9-4C3A-8E32-706149908C54>