From owner-freebsd-arm@FreeBSD.ORG Mon Dec 24 02:04:05 2012 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 5B3F8EA9 for ; Mon, 24 Dec 2012 02:04:05 +0000 (UTC) (envelope-from shurd@sasktel.net) Received: from mail111c7.megamailservers.com (mail111c7.megamailservers.com [69.49.98.211]) by mx1.freebsd.org (Postfix) with ESMTP id ECB088FC0C for ; Mon, 24 Dec 2012 02:04:04 +0000 (UTC) X-Authenticated-User: hurds.sasktel.net Received: from stephen.hurd.local (ip70-187-145-241.oc.oc.cox.net [70.187.145.241]) (authenticated bits=0) by mail111c7.megamailservers.com (8.13.6/8.13.1) with ESMTP id qBO23tnO025158; Sun, 23 Dec 2012 21:03:57 -0500 Message-ID: <50D7B80B.2030106@sasktel.net> Date: Sun, 23 Dec 2012 18:03:55 -0800 From: Stephen Hurd User-Agent: Mozilla/5.0 (X11; FreeBSD i386; rv:16.0) Gecko/20121022 Firefox/16.0 SeaMonkey/2.13.1 MIME-Version: 1.0 To: Alie Tan Subject: Re: FreeBSD10-CURRENT r244480 hang while compiling lighttpd or any port References: <6FC3E540-DEBD-4763-BB46-13F3422508E9@kientzle.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-CSC: 0 X-CHA: v=1.1 cv=2sEl+nYIWn3GVGOYG7vvzr4q0iGv5BXujfxzLqGOH1s= c=1 sm=1 a=sd1-78TbSwQA:10 a=W-nA_WuoWwAA:10 a=YxfxW3ofkq8A:10 a=8nJEP1OIZ-IA:10 a=qWhSLQ/2FgUpSQgLv9E1tw==:17 a=umj3UH_-hbk645b1_P8A:9 a=wPNLvfGTeEIA:10 a=qWhSLQ/2FgUpSQgLv9E1tw==:117 X-CTCH-Spam: Unknown X-CTCH-RefID: str=0001.0A02020A.50D7B80D.00AE, ss=1, re=0.000, recu=0.000, reip=0.000, cl=1, cld=1, fgs=0 Cc: Tim Kientzle , "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, 24 Dec 2012 02:04:05 -0000 Alie Tan wrote: >>> Anyone having hang issue while compiling any big port or portsnap fetch >>> extract? >> On what system? >> >> Tim >> > Oops sorry. On Raspberry Pi 256 and 512 I consistently do on my RPi 512, haven't looked into it yet though.