From owner-freebsd-arm@FreeBSD.ORG Mon Aug 5 14:18:49 2013 Return-Path: Delivered-To: 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 ESMTP id 614C0127 for ; Mon, 5 Aug 2013 14:18:49 +0000 (UTC) (envelope-from ian@FreeBSD.org) Received: from mho-02-ewr.mailhop.org (mho-02-ewr.mailhop.org [204.13.248.72]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id 37B0E2FBE for ; Mon, 5 Aug 2013 14:18:48 +0000 (UTC) Received: from c-24-8-230-52.hsd1.co.comcast.net ([24.8.230.52] helo=damnhippie.dyndns.org) by mho-02-ewr.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.72) (envelope-from ) id 1V6LcW-000Msv-4K; Mon, 05 Aug 2013 14:18:48 +0000 Received: from [172.22.42.240] (revolution.hippie.lan [172.22.42.240]) by damnhippie.dyndns.org (8.14.3/8.14.3) with ESMTP id r75EIjRW026357; Mon, 5 Aug 2013 08:18:45 -0600 (MDT) (envelope-from ian@FreeBSD.org) X-Mail-Handler: Dyn Standard SMTP by Dyn X-Originating-IP: 24.8.230.52 X-Report-Abuse-To: abuse@dyndns.com (see http://www.dyndns.com/services/sendlabs/outbound_abuse.html for abuse reporting information) X-MHO-User: U2FsdGVkX1+iYfEINArY6DmjWzXk55Pj Subject: Re: problem compiling libgcrypt from ports From: Ian Lepore To: Tom Everett In-Reply-To: References: <1375710734.3320.1.camel@revolution.hippie.lan> Content-Type: text/plain; charset="us-ascii" Date: Mon, 05 Aug 2013 08:18:45 -0600 Message-ID: <1375712325.3320.3.camel@revolution.hippie.lan> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port Content-Transfer-Encoding: 7bit Cc: "freebsd-arm@freebsd.org" 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: Mon, 05 Aug 2013 14:18:49 -0000 On Mon, 2013-08-05 at 07:54 -0600, Tom Everett wrote: > ok, I'll give that a try. Just FYI, it seems that my current gcc version > is 4.2.1, so I'd be asking to compile with an older gcc? > You're not compiling with gcc at all right now; those error messages you posted are clang errors (it's complaining that it doesn't support a particular gcc-specific extension). -- Ian