From owner-freebsd-arm@FreeBSD.ORG Sat Jan 25 20:40:46 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 D3BF6D98 for ; Sat, 25 Jan 2014 20:40:46 +0000 (UTC) Received: from mail-ig0-f171.google.com (mail-ig0-f171.google.com [209.85.213.171]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 98CE31482 for ; Sat, 25 Jan 2014 20:40:46 +0000 (UTC) Received: by mail-ig0-f171.google.com with SMTP id uy17so5577448igb.4 for ; Sat, 25 Jan 2014 12:40:40 -0800 (PST) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:sender:subject:mime-version:content-type:from :in-reply-to:date:cc:content-transfer-encoding:message-id:references :to; bh=/nbNhgJxgO+N4BTa+KUyKqEp7i0u6gJj52m4RmcAAJ8=; b=mSBYJlyZbPodnbTB+Ofv3qqKfAuu7FdL3fmRsxKYW2T8SCiWFLmqjzcsT/zsADZ1x+ FCaWEsyq3baWpqBl8crmiljvE5wqD1IhHtV2yBKeqsrT1z8FhkgzdKEvg/ZDCek86BIQ PkiETIIkm9sTuVNCYTHutE83N2gcGeJMWJ0BBLMPvMJmWcQ3lkTg9uE3GEaAkzsfYNWe YAmmAzQwx/hFg9dQhq76J2y8eygTMD//W0ijufkah7GGJonCHu3cVgf1FPwn75m8wJgc Cd+DX74WECEtvUg9MaDcbTuFL3vbojQu/01TT1sPN/eGcaf1/6yFlZ5iu8nItozfMZ6W uknw== X-Gm-Message-State: ALoCoQlcWpAX3+H+B6huImpcZBrX/NxPMfQ6yVh3D0ssMNV7OF8BqV7O9R6FGkbElxTEk0VHUvja X-Received: by 10.50.27.103 with SMTP id s7mr10586192igg.33.1390682440303; Sat, 25 Jan 2014 12:40:40 -0800 (PST) Received: from fusion-mac.bsdimp.com (50-78-194-198-static.hfc.comcastbusiness.net. [50.78.194.198]) by mx.google.com with ESMTPSA id f2sm25043790igt.6.2014.01.25.12.40.39 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Sat, 25 Jan 2014 12:40:39 -0800 (PST) Sender: Warner Losh Subject: Re: my private build RaspberryPi Image is available Mime-Version: 1.0 (Apple Message framework v1085) Content-Type: text/plain; charset=us-ascii From: Warner Losh In-Reply-To: <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> Date: Sat, 25 Jan 2014 13:40:38 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: 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> <40C89CEB-7107-416C-80EF-FC6A4B687040@kientzle.com> To: Tim Kientzle X-Mailer: Apple Mail (2.1085) 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:40:46 -0000 On Jan 25, 2014, at 1:14 PM, Tim Kientzle wrote: > On Jan 25, 2014, at 11:56 AM, George Mitchell = wrote: >=20 >> 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 >=20 > 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. >=20 > So it's certainly worth exploring how to build ports that require GCC > without using the in-tree GCC. Step 1 is getting my patches into the ports tree so that we can = configure for freebsd/arm and freebsd/armv6 (among others). Let me go = looking for them... Warner