From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 74DCB1391DB for ; Fri, 1 Aug 2014 08:23:24 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 8E1AAE091D; Fri, 1 Aug 2014 08:23:18 +0000 (UTC) Received: from wraeth.id.au (wraeth.id.au [106.187.101.125]) by pigeon.gentoo.org (Postfix) with ESMTP id 4F875E090A for ; Fri, 1 Aug 2014 08:23:17 +0000 (UTC) Received: from [10.1.60.14] (unknown [103.6.189.72]) (using TLSv1.2 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by wraeth.id.au (Postfix) with ESMTPSA id 38D8BC03D for ; Fri, 1 Aug 2014 08:23:14 +0000 (UTC) Message-ID: <1406881383.2106.1.camel@wraeth.id.au> Subject: Re: [gentoo-user] Compiling for different CPU but same architecture From: wraeth To: gentoo-user@lists.gentoo.org Date: Fri, 01 Aug 2014 18:23:03 +1000 In-Reply-To: <1406880069.31927.1.camel@nileshgr.com> References: <1406872796.1957.1.camel@wraeth.id.au> <20140801085351.02b6bf18@digimed.co.uk> <1406880069.31927.1.camel@nileshgr.com> Content-Type: multipart/signed; micalg="pgp-sha256"; protocol="application/pgp-signature"; boundary="=-nWLQnfoLxwR2j4XcnY7q" X-Mailer: Evolution 3.12.4 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org Mime-Version: 1.0 X-Archives-Salt: e118ae4a-98b2-466e-b4e3-f86551f7b7ea X-Archives-Hash: cd77e8b37f16e99f8ea21b09103bee0a --=-nWLQnfoLxwR2j4XcnY7q Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Fri, 2014-08-01 at 13:31 +0530, Nilesh Govindrajan wrote: > systemd-nspawn seems to be interesting. But will it work on my i5? > Because I prefer to use -march=3Dnative. For using distcc I copied all th= e > flags that gcc selects in march=3Dnative mode to make.conf. systemd-nspawn is described as "a chroot on steroids". It has no impact on what flags you use for compiling packages. The advantage of systemd-nspawn is the fact that it actually isolates and executes the chroot's own init process, either systemd or (as I understand - haven't tested myself) newer versions of OpenRC. Once you're in the chroot, things work almost the same as if you had actually booted the system itself (with some exceptions). It manages mounting the virtual filesystems it needs, and has built-in functionality for managing bind mounts if needed (such as binding your portage tree so you don't have to re-download it). As Neil said, once inside the chroot, you would still have to manually set your CFLAGS - "-march=3Dnative" is a function of gcc to dynamically detect the optimal flags to use *at the time it compiles*. All this is rather meaningless, though, if you don't have systemd on your host system anyway. --=20 wraeth --=-nWLQnfoLxwR2j4XcnY7q Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iF4EABEIAAYFAlPbTmsACgkQXcRKerLZ91miAwD/byPg44miVz8OU4/O8htxL8hL LzlAlfKnnkXZ9eIsDFAA/jxOqAhPN2hA6r8N2XwvwV0ILE180da+vpPOeIA2m9F2 =W3hh -----END PGP SIGNATURE----- --=-nWLQnfoLxwR2j4XcnY7q--