From: "Jc García" <jyo.garcia@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling for different CPU but same architecture
Date: Fri, 1 Aug 2014 06:00:01 -0600 [thread overview]
Message-ID: <CAGQH77fM8tZSKeMi9stdxAMp7+Vvx4gJBYuH0pnBF1M5AooWxQ@mail.gmail.com> (raw)
In-Reply-To: <20140801125120.4c7a35ff@hactar.digimed.co.uk>
2014-08-01 5:51 GMT-06:00 Neil Bothwick <neil@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.
next prev parent reply other threads:[~2014-08-01 12:00 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 3:53 [gentoo-user] Compiling for different CPU but same architecture Nilesh Govindrajan
2014-08-01 5:46 ` Canek Peláez Valdés
2014-08-01 5:59 ` wraeth
2014-08-01 7:53 ` Neil Bothwick
2014-08-01 8:01 ` Nilesh Govindrajan
2014-08-01 8:09 ` Neil Bothwick
2014-08-01 8:23 ` wraeth
2014-08-01 8:25 ` Nilesh Govindrajan
2014-08-01 8:37 ` wraeth
2014-08-01 11:45 ` Jc García
2014-08-01 11:51 ` Neil Bothwick
2014-08-01 12:00 ` Jc García [this message]
2014-08-01 12:22 ` Nilesh Govindrajan
2014-08-01 13:04 ` Jc García
2014-08-01 12:29 ` Nilesh Govindrajan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAGQH77fM8tZSKeMi9stdxAMp7+Vvx4gJBYuH0pnBF1M5AooWxQ@mail.gmail.com \
--to=jyo.garcia@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox