Re: [gentoo-user] Compiling for different CPU but same architecture

[Nilesh Govindrajan]

On Fri, 2014-08-01 at 18:23 +1000, wraeth wrote:
> 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=native. For using distcc I copied all the
> > flags that gcc selects in march=native 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=native" 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.

I wouldn't have taken interest in that one if I didn't have systemd. I'm
using GNOME3 on both my desktop and the laptop, so systemd is a must.
-- 
Nilesh Govindrajan <me@××××××××.com>