From owner-freebsd-arm@FreeBSD.ORG Thu Apr 17 10:31:53 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 06C3B3C6 for ; Thu, 17 Apr 2014 10:31:53 +0000 (UTC) Received: from raven.bwct.de (raven.bwct.de [85.159.14.73]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client CN "raven.bwct.de", Issuer "BWCT" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8D2FF1898 for ; Thu, 17 Apr 2014 10:31:51 +0000 (UTC) Received: from mail.cicely.de ([10.1.1.37]) by raven.bwct.de (8.13.4/8.13.4) with ESMTP id s3HAVOCn027745 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL); Thu, 17 Apr 2014 12:31:24 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (cicely7.cicely.de [10.1.1.9]) by mail.cicely.de (8.14.5/8.14.4) with ESMTP id s3HAVIAR037181 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 17 Apr 2014 12:31:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: from cicely7.cicely.de (localhost [127.0.0.1]) by cicely7.cicely.de (8.14.2/8.14.2) with ESMTP id s3HAVIQC044314; Thu, 17 Apr 2014 12:31:18 +0200 (CEST) (envelope-from ticso@cicely7.cicely.de) Received: (from ticso@localhost) by cicely7.cicely.de (8.14.2/8.14.2/Submit) id s3HAVHCa044313; Thu, 17 Apr 2014 12:31:17 +0200 (CEST) (envelope-from ticso) Date: Thu, 17 Apr 2014 12:31:17 +0200 From: Bernd Walter To: Tim Kientzle Subject: Re: Building an ARM/RPI-B release (hacked) on CURRENT/AMD64. Message-ID: <20140417103117.GE44138@cicely7.cicely.de> References: <9FDD6F0E-B2A9-48D9-A3E4-181868995FDA@grondar.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD cicely7.cicely.de 7.0-STABLE i386 User-Agent: Mutt/1.5.11 X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED=-1, BAYES_00=-1.9, T_RP_MATCHES_RCVD=-0.01 autolearn=ham version=3.3.0 X-Spam-Checker-Version: SpamAssassin 3.3.0 (2010-01-18) on spamd.cicely.de Cc: freebsd-arm , Mark R V Murray X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list Reply-To: ticso@cicely.de 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 10:31:53 -0000 On Wed, Apr 16, 2014 at 06:25:39PM -0700, Tim Kientzle wrote: > > On Apr 15, 2014, at 12:23 PM, Mark R V Murray wrote: > > > Hi Tim > > > > I?ve been doing some local hacks to cross-build ARM/RPI releases on CURRENT/AMD64. > > > > What I?m doing aren?t clean releases in that I want to use the state of /usr/src and /usr/ports ?as-is? 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 ?if?!) I mess things up properly on the RPI. It has the advantage also of being quicker than the usual release build. > > > > (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.) > > > > 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. > > > > 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?t have the R9 fix. > > > > Questions: > > > > 1) Are you aware of any of this? > > Yes. > > > > > 2) Do you have a quick fix idea (preferably not involving GCC)? > > No. > > Right now, the ?get it working? answer is to install GCC XDEV tools. > > Though I tried that on a clean system last weekend and it > still failed to build. Haven?t tracked down why. > > > > > I?m rather short of time right now, but may be able to get to this over Easter. > > Long-term, we?d all like to see U-Boot build with clang. > > No idea yet whether that?s hard or not. No idea if > I?ll have time to work on it in the near future. What are the symptoms with clang U-Boot? -- B.Walter http://www.bwct.de Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.