From owner-freebsd-ports@freebsd.org Wed Apr 5 16:15:42 2017 Return-Path: Delivered-To: freebsd-ports@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 24483D30339; Wed, 5 Apr 2017 16:15:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: from freefall.freebsd.org (freefall.freebsd.org [96.47.72.132]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 038BA7A6; Wed, 5 Apr 2017 16:15:42 +0000 (UTC) (envelope-from danfe@freebsd.org) Received: by freefall.freebsd.org (Postfix, from userid 1033) id 2DFA33568; Wed, 5 Apr 2017 16:15:41 +0000 (UTC) Date: Wed, 5 Apr 2017 16:15:41 +0000 From: Alexey Dokuchaev To: Matthew Rezny Cc: Dimitry Andric , Mark Millard , Johannes M Dieterich , FreeBSD Current , FreeBSD Toolchain , FreeBSD Ports , FreeBSD PowerPC ML Subject: Re: FYI: what it takes for RAM+swap to build devel/llvm40 with 4 processors or cores and WITH__DEBUG= (powerpc64 example) Message-ID: <20170405161541.GA32323@FreeBSD.org> References: <3EDEF0B7-59C5-4648-9737-6682E18645BC@dsl-only.net> <7F94CE59-D2CC-4D6F-B1CD-FF3D1F8EDCE7@FreeBSD.org> <20170330170648.GA38004@FreeBSD.org> <2502554.oHoOYGyFJH@workstation.reztek> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <2502554.oHoOYGyFJH@workstation.reztek> User-Agent: Mutt/1.7.1 (2016-10-04) X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Apr 2017 16:15:42 -0000 On Thu, Mar 30, 2017 at 07:26:43PM +0200, Matthew Rezny wrote: > LLVM 3.8 introduced the option to build a shared LLVM library, which is > what Mesa needs for use at runtime (for e.g. compiling shaders), separate > from linking to it. Previous versions only had one option, if the library > was built then all the LLVM binaries were staticly linked to it. [...] > > llvm{35,36,37} are statically linked and thus smaller than normal. llvm38 > switched to dynamic linking, the default, thus the size grew. Hmm, I don't quite get it: shouldn't static linking actually increase the binaries (and thus the package) size? > I assume llvm40 will be a bit bigger, but do not expect to see another > jump as you've observed. As Mark Millard reports: > I've also tried without WITH_DEBUG= and now. . . > > # pkg delete llvm40 > Checking integrity... done (0 conflicting) > Deinstallation has been requested for the following 1 packages (of 0 > packages in the universe): > > Installed packages to be REMOVED: > llvm40-4.0.0 > > Number of packages to be removed: 1 > > The operation will free 1 GiB. That 1G looks like a big jump from 259M of llvm39-3.9.1_1.txz to me. I'm surely looking forward modularization of LLVM port; rebuilding it every time becomes a real PITA given that X11 stack requires it. :-( ./danfe