public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Compiling for different CPU but same architecture
Date: Fri, 1 Aug 2014 09:09:24 +0100	[thread overview]
Message-ID: <20140801090924.5493337a@digimed.co.uk> (raw)
In-Reply-To: <1406880069.31927.1.camel@nileshgr.com>

[-- Attachment #1: Type: text/plain, Size: 547 bytes --]

On Fri, 01 Aug 2014 13:31:09 +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.
.
Do the same for systemd-nspawn or chroot. Alternatively, set up CFLAGS
that are compatible with both systems and use packages built for the
faster machine on both.


-- 
Neil Bothwick

Bug: (n.) any program feature not yet described to the marketing
department.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2014-08-01  8:09 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 [this message]
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
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=20140801090924.5493337a@digimed.co.uk \
    --to=neil@digimed.co.uk \
    --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