From owner-freebsd-arm@FreeBSD.ORG Thu Apr 17 01:25:49 2014 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id E8286C23 for ; Thu, 17 Apr 2014 01:25:48 +0000 (UTC) Received: from mail-pd0-f175.google.com (mail-pd0-f175.google.com [209.85.192.175]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id BAD9B1FE6 for ; Thu, 17 Apr 2014 01:25:48 +0000 (UTC) Received: by mail-pd0-f175.google.com with SMTP id x10so11360493pdj.34 for ; Wed, 16 Apr 2014 18:25:42 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:content-type:mime-version:subject:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=STavD8qn05rbIN4YCaGZY9eHG4EW8EO7aZXojtzxKDQ=; b=bAukHTrkIhTzFvhcjr00NDIxPYMFnB5A6S1+GPy2fSYAg5sAS9hrG0WPztvHTHtGMx A/GkjsDMt8/rEPx0Xn3dYM+6Cx2cM5iDiBGOrQ4lWGrIOpQvscb09qnFQR1DBoZOYO06 0maZX61E/gXtQmsfaPo1vIic0CoCt7vUMmq52vJoIpfE/mmmRTSeor8PoV1UTbAL2Nw2 /FXKslDLBPfpHI3y8++WhOWiLhsKryUXPYPokcyNnCjO/FV4uNg8NJgMnafSNS05wSFD TXC+L26Qi4erCqs/O7fGOdiQWoOT5TSqDdLgPdWTrCg87O4ZzFuldZKhD0BNIiojaBqC wiKg== X-Gm-Message-State: ALoCoQlW03aMRHvmRblIHJjA8pkh3/crpnRYiqPf3g764dLtkXplaEfm46XPcypZxOcVQHxlUNmJ X-Received: by 10.66.221.4 with SMTP id qa4mr12252727pac.138.1397697942106; Wed, 16 Apr 2014 18:25:42 -0700 (PDT) Received: from [192.168.1.2] (c-50-156-22-189.hsd1.ca.comcast.net. [50.156.22.189]) by mx.google.com with ESMTPSA id pe3sm49784443pbc.23.2014.04.16.18.25.40 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Wed, 16 Apr 2014 18:25:41 -0700 (PDT) Content-Type: text/plain; charset=windows-1252 Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\)) Subject: Re: Building an ARM/RPI-B release (hacked) on CURRENT/AMD64. From: Tim Kientzle In-Reply-To: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org> Date: Wed, 16 Apr 2014 18:25:39 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org> To: Mark R V Murray X-Mailer: Apple Mail (2.1874) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Apr 2014 01:25:49 -0000 On Apr 15, 2014, at 12:23 PM, Mark R V Murray 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. 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