Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 16 Apr 2014 18:25:39 -0700
From:      Tim Kientzle <tim@kientzle.com>
To:        Mark R V Murray <mark@grondar.org>
Cc:        freebsd-arm <freebsd-arm@freebsd.org>
Subject:   Re: Building an ARM/RPI-B release (hacked) on CURRENT/AMD64.
Message-ID:  <EC41E53F-96EF-4652-9A02-D49448D104BE@kientzle.com>
In-Reply-To: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org>
References:  <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org>

next in thread | previous in thread | raw e-mail | index | archive | help

On Apr 15, 2014, at 12:23 PM, Mark R V Murray <mark@grondar.org> wrote:

> Hi Tim
>=20
> I=92ve been doing some local hacks to cross-build ARM/RPI releases on =
CURRENT/AMD64.
>=20
> What I=92m doing aren=92t clean releases in that I want to use the =
state of /usr/src and /usr/ports =93as-is=94 and not a clean check out. =
This allows me to experimentally break stuff without having to check it =
in first. It also give me a way to build bootable images for when (not =
=93if=94!) I mess things up properly on the RPI. It has the advantage =
also of being quicker than the usual release build.
>=20
> (The hacks, as they stand now, are attached. I null-mount /usr/src and =
/usr/ports instead of checking them out, and I have local checkouts of =
crochet and u-boot to copy as checking them out during a release build =
fails too often.)
>=20
> The problem is that sometime in the last month or so, things stopped =
working, and its taken me until now to have the time to have a look at =
it.
>=20
> The problem is that during the u-boot build, a CLANG-based xdev build =
is used, and this has no *-gcc, only a *-cc. If I fix that with a =
symlink, clang then objects to the -ffixed-r8 option. Clang has an =
equivalent -ffixed-r9, but the u-boot that is  mandated for =
FreeBSD/Arm/RPI use doesn=92t have the R9 fix.
>=20
> Questions:
>=20
> 1) Are you aware of any of this?

Yes.

>=20
> 2) Do you have a quick fix idea (preferably not involving GCC)?

No.  <sigh>

Right now, the =93get it working=94 answer is to install GCC XDEV tools.

Though I tried that on a clean system last weekend and it
still failed to build.  Haven=92t tracked down why.

>=20
> I=92m rather short of time right now, but may be able to get to this =
over Easter.

Long-term, we=92d all like to see U-Boot build with clang.

No idea yet whether that=92s hard or not.  No idea if
I=92ll have time to work on it in the near future.

Tim




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?EC41E53F-96EF-4652-9A02-D49448D104BE>