Date: Thu, 15 Aug 2013 19:09:15 -0400 From: Paul Mather <paul@gromit.dlib.vt.edu> To: Adrian Chadd <adrian@freebsd.org> Cc: freebsd-arm <freebsd-arm@freebsd.org> Subject: Re: pkg repository for ARM? Message-ID: <41577B23-E4DE-451B-B5F7-912024C05AB7@gromit.dlib.vt.edu> In-Reply-To: <CAJ-Vmo=HffPx1nfRPaO7ZWx15EcY9DRbACqs-F1tDrea_murzw@mail.gmail.com> References: <522A0D57-4DD4-4669-BB5A-AFCD81E9F497@netsense.nl> <DE75F074-D232-4D6F-AB78-C7C606E5F59A@ugh.net.au> <CAJ-Vmo=HffPx1nfRPaO7ZWx15EcY9DRbACqs-F1tDrea_murzw@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Aug 15, 2013, at 6:46 PM, Adrian Chadd <adrian@freebsd.org> 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 <andrew@ugh.net.au> wrote: >=20 >>=20 >>=20 >> On 15.08.2013, at 22:45, Johan Henselmans <johan@netsense.nl> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?41577B23-E4DE-451B-B5F7-912024C05AB7>