On Fri, 2014-08-01 at 06:00 -0600, Jc García wrote: > 2014-08-01 5:51 GMT-06:00 Neil Bothwick <n...@digimed.co.uk>: > > On Fri, 1 Aug 2014 05:45:36 -0600, Jc García 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. > >> > > >> > > >> I don't think what CFLAGS you are using matters for using > >> systemd-nspawn. > > > > If you are using a chroot to build packages for installation on another > > machine, the CFLAGS should be appropriate for the target machine, not the > > build host. > > > Maybe I misinterpreted what he was asking, I was only thinking about > the part of using nspawn as a replacement for chroot, not beyond that, > but you're right. > > > > -- > > Neil Bothwick > > > > The quickest way to a man's heart is through his sternum. >
Why it shouldn't matter? What if a package's building process depends on some other package? Though the build process isn't for a completely different arch, it might matter. That's my doubt.
