From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:08:16 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 64A57995 for ; Sat, 25 Jan 2014 20:08:16 +0000 (UTC) Received: from mailhost.m5p.com (ip-2-1-0-2.r03.asbnva02.us.ce.gin.ntt.net [IPv6:2001:418:0:5000::16]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 185E5115F for ; Sat, 25 Jan 2014 20:08:15 +0000 (UTC) Received: from wonderland.m5p.com (localhost [IPv6:::1]) by mailhost.m5p.com (8.14.5/8.14.5) with ESMTP id s0PJuGrg080657 for ; Sat, 25 Jan 2014 14:56:21 -0500 (EST) (envelope-from george+freebsd@m5p.com) Message-ID: <52E416E0.7060204@m5p.com> Date: Sat, 25 Jan 2014 14:56:16 -0500 From: George Mitchell User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: freebsd-arm@freebsd.org Subject: Re: my private build RaspberryPi Image is available References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.73 on 10.100.0.3 X-Greylist: Sender passed SPF test, not delayed by milter-greylist-4.2.7 (mailhost.m5p.com [IPv6:::1]); Sat, 25 Jan 2014 14:56:22 -0500 (EST) 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: Sat, 25 Jan 2014 20:08:16 -0000 On 01/25/14 14:24, Tim Kientzle wrote: > > On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: > >> Unfortunately, there are some ports which I can't compile >> on -current FreeBSD/RaspberryPi. >> These ports requires GCC, but gcc ports in -current does not support >> arm/armv6. > > Why not? Any suggestion how to fix that? > > Tim > [...] For me, specifying WITH_GCC="yes" in src.conf at the time I built the world gave me a gcc that works for at least the ports I needed. (And any port that specifies USES_GCC=any). -- George