From owner-freebsd-ports-bugs@FreeBSD.ORG Sat Aug 25 18:40:04 2012 Return-Path: Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id C14E8106564A for ; Sat, 25 Aug 2012 18:40:04 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:4f8:fff6::28]) by mx1.freebsd.org (Postfix) with ESMTP id A66188FC0A for ; Sat, 25 Aug 2012 18:40:04 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.5/8.14.5) with ESMTP id q7PIe4U4050638 for ; Sat, 25 Aug 2012 18:40:04 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.5/8.14.5/Submit) id q7PIe4cs050637; Sat, 25 Aug 2012 18:40:04 GMT (envelope-from gnats) Date: Sat, 25 Aug 2012 18:40:04 GMT Message-Id: <201208251840.q7PIe4cs050637@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: Mark Linimon Cc: Subject: Re: ports/170946: [patch] mark certain ports broken on ARM X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Mark Linimon List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 25 Aug 2012 18:40:04 -0000 The following reply was made to PR ports/170946; it has been noted by GNATS. From: Mark Linimon To: Chris Rees Cc: "Mikhail T." , dougb@FreeBSD.org, Eitan Adler , bug-followup@freebsd.org Subject: Re: ports/170946: [patch] mark certain ports broken on ARM Date: Sat, 25 Aug 2012 13:32:51 -0500 On Sat, Aug 25, 2012 at 05:06:11PM +0100, Chris Rees wrote: > Also, don't forget that package building runs are often done with > TRY_BROKEN, which is very helpful when doing !intel builds. Well, I wouldn't say "often" :-) But yes, this is the distinction: whether or not we should even try to build it on the cluster in any circumstances. (e.g. if it has not yet been ported to that architecture, ONLY_FOR is the right thing AFAIC.) The errorlog URLs that I should have included (note that they are a bit disjoint): http://pointyhat-west.isc.freebsd.org/errorlogs/arm-errorlogs/e.9.20120812031641.pointyhat-west/index-category.html http://pointyhat-west.isc.freebsd.org/errorlogs/arm-errorlogs/e.9.20120818210612.pointyhat-west/index-category.html Finally, I wanted to use this PR as kind of a heads-up to maintainers that we had a new architecture up and going, so as to reduce the surprise. mcl