From owner-freebsd-arm@FreeBSD.ORG Thu Aug 15 23:55:59 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTP id 0E52674; Thu, 15 Aug 2013 23:55:59 +0000 (UTC) (envelope-from paul@gromit.dlib.vt.edu) Received: from lennier.cc.vt.edu (lennier.cc.vt.edu [198.82.162.213]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id BAD5E2121; Thu, 15 Aug 2013 23:55:58 +0000 (UTC) Received: from mr3.cc.vt.edu (mr3.cc.vt.edu [198.82.141.68]) by lennier.cc.vt.edu (8.13.8/8.13.8) with ESMTP id r7FN9JsB003186; Thu, 15 Aug 2013 19:09:20 -0400 Received: from auth3.smtp.vt.edu (auth3.smtp.vt.edu [198.82.161.152]) by mr3.cc.vt.edu (8.14.4/8.14.4) with ESMTP id r7FN9HPX000587; Thu, 15 Aug 2013 19:09:17 -0400 Received: from gromit.chumby.lan (c-98-249-9-133.hsd1.va.comcast.net [98.249.9.133]) (authenticated bits=0) by auth3.smtp.vt.edu (8.13.8/8.13.8) with ESMTP id r7FN9FgB022644 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 15 Aug 2013 19:09:16 -0400 Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\)) Subject: Re: pkg repository for ARM? From: Paul Mather In-Reply-To: Date: Thu, 15 Aug 2013 19:09:15 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <41577B23-E4DE-451B-B5F7-912024C05AB7@gromit.dlib.vt.edu> References: <522A0D57-4DD4-4669-BB5A-AFCD81E9F497@netsense.nl> To: Adrian Chadd X-Mailer: Apple Mail (2.1508) Cc: freebsd-arm X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Aug 2013 23:55:59 -0000 On Aug 15, 2013, at 6:46 PM, Adrian Chadd wrote: > ... why can't libgcrypt be marked as requiring gcc for now? I'm presuming you'd have to make this exception just for arm, because it = works with clang on other platforms? But, I think this just masks the problem, because I think there's the = bigger issue that the clang toolchain on arm appears to be broken. In = fact, I think there's a good argument to be made that the switch to = clang as the default compiler shouldn't have been thrown on FreeBSD/arm = because clang doesn't work fully there. See, e.g., PR arm/178495 for a = typical example. AFAIK, a native build under clang on arm is still broken. I have only = been able to do a successful native build on arm, or build ports = successfully, by using gcc as the default compiler, i.e., to set = WITHOUT_CLANG_IS_CC in /etc/src.conf. So, instead of marking ports on arm on a piecemeal basis, couldn't we = undo the WITH_CLANG_IS_CC default setting until clang works properly? (Hopefully, someone will reply and tell me it's fixed; I've kind of = backed off from using my Raspberry Pi and Beaglebone Black on FreeBSD = the past couple of weeks due to the broken toolchain issues.:) Cheers, Paul. >=20 >=20 >=20 > -adrian >=20 >=20 >=20 > On 15 August 2013 15:10, Andrew Stevenson wrote: >=20 >>=20 >>=20 >> On 15.08.2013, at 22:45, Johan Henselmans wrote: >>=20 >>> there. Reason is that libgcrypt does not compile: error log is over >> here: >>>=20 >>> http://pastebin.com/D3LTUv2P >>=20 >> A few ppl have hit that if you check the archives. I believe = compiling >> with gcc (or maybe using the clang flag suggested) should get you = further. >>=20 >> Andrew >> _______________________________________________ >> freebsd-arm@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-arm >> To unsubscribe, send any mail to = "freebsd-arm-unsubscribe@freebsd.org" >>=20 > _______________________________________________ > freebsd-arm@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-arm > To unsubscribe, send any mail to "freebsd-arm-unsubscribe@freebsd.org" >=20