From owner-freebsd-arm@FreeBSD.ORG Sat Jan 3 19:40:01 2015 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A599B190 for ; Sat, 3 Jan 2015 19:40:01 +0000 (UTC) Received: from monday.kientzle.com (99-115-135-74.uvs.sntcca.sbcglobal.net [99.115.135.74]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 7E9231069 for ; Sat, 3 Jan 2015 19:40:01 +0000 (UTC) Received: (from root@localhost) by monday.kientzle.com (8.14.4/8.14.4) id t03JdsCO062823; Sat, 3 Jan 2015 19:39:54 GMT (envelope-from tim@kientzle.com) Received: from [192.168.2.102] (gateway.kientzle.com [192.168.1.65]) by kientzle.com with SMTP id ggru9qjii2wu3w5u84g4c7w296; Sat, 03 Jan 2015 19:39:53 +0000 (UTC) (envelope-from tim@kientzle.com) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 8.1 \(1993\)) Subject: Re: Cross-Compiling RPi Ports From amd64 Using Native Toolchain From: Tim Kientzle In-Reply-To: Date: Sat, 3 Jan 2015 11:39:53 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <02C43C8A-E9BB-4E59-8442-FC382689D941@kientzle.com> References: To: Jeremy Brown X-Mailer: Apple Mail (2.1993) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 03 Jan 2015 19:40:01 -0000 > On Jan 2, 2015, at 7:42 PM, Jeremy Brown = wrote: >=20 > One additional thing: I checked my toolchain and did see that some of = my > programs (ar, as, cc, gcc, ld, ranlib) are statically linked, whereas = the > rest are dynamically linked, including cpp and nm which also gave me = the > ELF interpreter error. So I'll change my question somewhat - if I use = the > command given on the qemu page (env -u TARGET -u TARGET_ARCH make -j 4 > toolchain) instead of the one provided by crochet (make XDEV=3D${XDEV} > XDEV_ARCH=3D${XDEV_ARCH} WITH_GCC=3D1 WITH_GCC_BOOTSTRAP=3D1 = WITHOUT_CLANG=3D1 > WITHOUT_CLANG_BOOTSTRAP=3D1 WITHOUT_CLANG_IS_CC=3D1 WITHOUT_TESTS=3D1 = xdev), > would I be more likely to succeed in cross-compiling my ports and will = I be > able to use this toolchain to build the kernel and world with crochet? You should install both and use them for different purposes: Crochet uses the =E2=80=98xdev=E2=80=99 tools *only* for compiling the = U-Boot boot loader. (It does *not* use it for building kernel and world. The standard FreeBSD build infrastructure automatically builds appropriate cross-compilers as needed for kernel and world.) Tim