From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:14:00 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 B1EFED2C for ; Sat, 25 Jan 2014 20:14:00 +0000 (UTC) Received: from mail-pa0-f51.google.com (mail-pa0-f51.google.com [209.85.220.51]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 812AA11E5 for ; Sat, 25 Jan 2014 20:14:00 +0000 (UTC) Received: by mail-pa0-f51.google.com with SMTP id ld10so4537430pab.10 for ; Sat, 25 Jan 2014 12:13:59 -0800 (PST) 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=owC8TWmlkYHDdGDiAZAwKoLhAHKSdKDzw1yFKBXNbAI=; b=D0r/KC8q7reNvFFzzve6HF0nbzR3mdRjutMbSkd9zmnXLwCSzuHZF0i3MZ0g7FqOam J42DeuR97OadJg5jo+H5mJe0jS9x482hUuINsfKboBpJFNmUsWobdU6tud3jHmiS5rHe LUPtARO7IKPRj9k339MIHpOQKYKRKmxa2/Q0dDgFY21tV5iP+PcbfHikcmBaoP2DJwCj V9m1Qu+zEgsDoVgkBaqziGuOWCJzX+mNoYrWgx4LZyDMbZkEHLnPVOGS5QI4GAzmHXGB Z0ifZw7NJJ7C9Bhy2AOR575o3L4yJDw2JCvM0TTP3wzSBefpfjAaLeDYJjEAAzz7Ih/7 vXJA== X-Gm-Message-State: ALoCoQlEk4qiZOj1NwKgD3dB6p+tBhpWQMV8CelUP2M0AHZQyxIqOJfnHg/i+a12yb+jkiIq3wpX X-Received: by 10.68.172.37 with SMTP id az5mr21378815pbc.139.1390680839827; Sat, 25 Jan 2014 12:13:59 -0800 (PST) Received: from [192.168.2.123] (99-74-169-43.lightspeed.sntcca.sbcglobal.net. [99.74.169.43]) by mx.google.com with ESMTPSA id sq7sm15869213pbc.19.2014.01.25.12.13.58 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 12:13:59 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 7.1 \(1827\)) Subject: Re: my private build RaspberryPi Image is available From: Tim Kientzle In-Reply-To: <52E416E0.7060204@m5p.com> Date: Sat, 25 Jan 2014 12:14:06 -0800 Content-Transfer-Encoding: quoted-printable Message-Id: <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> References: <20140122.190031.29969140.shigeru@os-hackers.jp> <20140122.224425.103076338.shigeru@os-hackers.jp> <20140123.085609.53072279.shigeru@os-hackers.jp> <52E416E0.7060204@m5p.com> To: George Mitchell X-Mailer: Apple Mail (2.1827) Cc: freebsd-arm ml 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:14:00 -0000 On Jan 25, 2014, at 11:56 AM, George Mitchell = wrote: > On 01/25/14 14:24, Tim Kientzle wrote: >>=20 >> On Jan 22, 2014, at 3:56 PM, shigeru@os-hackers.jp wrote: >>=20 >>> 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. >>=20 >> Why not? Any suggestion how to fix that? >>=20 >> Tim >> [...] >=20 > For me, specifying WITH_GCC=3D"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=3Dany). -- George That works today, but isn't a particularly good long-term answer: * Ports that demand GCC will increasingly expect something newer than = GCC 4.2. * Someday (FreeBSD 11? FreeBSD 12?) we will no longer have GCC = in-tree. So it's certainly worth exploring how to build ports that require GCC without using the in-tree GCC. Tim