From owner-freebsd-arm@freebsd.org Thu Jan 19 00:10:59 2017 Return-Path: Delivered-To: freebsd-arm@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 20540CB6019 for ; Thu, 19 Jan 2017 00:10:59 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: from asp.reflexion.net (outbound-mail-210-16.reflexion.net [208.70.210.16]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id BACF91CDE for ; Thu, 19 Jan 2017 00:10:58 +0000 (UTC) (envelope-from markmi@dsl-only.net) Received: (qmail 29030 invoked from network); 19 Jan 2017 00:11:24 -0000 Received: from unknown (HELO rtc-sm-01.app.dca.reflexion.local) (10.81.150.1) by 0 (rfx-qmail) with SMTP; 19 Jan 2017 00:11:24 -0000 Received: by rtc-sm-01.app.dca.reflexion.local (Reflexion email security v8.20.1) with SMTP; Wed, 18 Jan 2017 19:10:57 -0500 (EST) Received: (qmail 26636 invoked from network); 19 Jan 2017 00:10:56 -0000 Received: from unknown (HELO iron2.pdx.net) (69.64.224.71) by 0 (rfx-qmail) with (AES256-SHA encrypted) SMTP; 19 Jan 2017 00:10:56 -0000 Received: from [192.168.1.111] (c-67-170-167-181.hsd1.or.comcast.net [67.170.167.181]) by iron2.pdx.net (Postfix) with ESMTPSA id 3836FEC9092; Wed, 18 Jan 2017 16:10:56 -0800 (PST) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\)) Subject: Re: Using poudriere (with -a arm.armv6 -x ) on amd64 vs. building lang/gcc6: Some notes from my first attempts From: Mark Millard In-Reply-To: <6eab4388-bbdd-7b87-b2d3-0b8b03ea6d07@t-online.de> Date: Wed, 18 Jan 2017 16:10:55 -0800 Cc: freebsd-arm@freebsd.org Content-Transfer-Encoding: quoted-printable Message-Id: <7973979C-8B24-48AA-8355-4E28A263646E@dsl-only.net> References: <6eab4388-bbdd-7b87-b2d3-0b8b03ea6d07@t-online.de> To: diffusae X-Mailer: Apple Mail (2.3259) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2017 00:10:59 -0000 On 2017-Jan-18, at 2:33 PM, diffusae wrote: > On 18.01.2017 23:13, Mark Millard wrote: >>> Stop. >>> make: stopped in /usr/ports/lang/gcc6 >> from running out of swap space. >=20 > I've had the same with lang/gcc. > After upgrading to the lastest emulators/qemu-user-static, it takes > quite a long time, but it will compile and finished. Thanks for the note. But. . . My installation is from ports head -r431413 and https://svnweb.freebsd.org/ports/head/emulators/ shows qemu-user-static and qemu-sbruno have not changed since: qemu-sbruno/ 431215 7 days qemu-user-static/ 415498 8 months (user-static is a slave port off of sbruno) # svnlite info /usr/ports/ | grep "Re[plv]" Relative URL: ^/head Repository Root: svn://svn.freebsd.org/ports Repository UUID: 35697150-7ecd-e111-bb59-0022644237b5 Revision: 431413 Last Changed Rev: 431413 # pkg info qemu-user-static qemu-user-static-2.8.50.g20161228_1 Name : qemu-user-static Version : 2.8.50.g20161228_1 Installed on : Sun Jan 15 13:39:14 2017 PST Origin : emulators/qemu-user-static Architecture : freebsd:12:x86:64 Prefix : /usr/local Categories : emulators Licenses : GPLv2 Maintainer : sbruno@FreeBSD.org WWW : http://wiki.qemu.org/Main_Page Comment : QEMU CPU Emulator github bsd-user branch - static user = targets Annotations : Flat size : 112MiB lang/gcc6 is a much bigger build than lang/gcc49 (or lang/gcc) from what I can tell (full bootstrap). I'd noticed that on various native builds (armv6, powerpc64, amd64). poudriere and the rest of the installed were also from -r431413 . > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D214944 This predates what I was using and so is not a "fix" for what I observed with the memory and swap that I provided. I had deliberately picked the port that I build that I thought would use the most time and RAM/swap. I've not done anything that would indicate if more memory leaks are involved or not. If there are I'd expect that the leak rate was slow since it ran for over 72 hours and made sustained progress right up to where it failed from what I can tell. =3D=3D=3D Mark Millard markmi at dsl-only.net