public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alex Schuster <wonko@wonkology.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Hoping someone can help explain distcc to me
Date: Mon, 22 Aug 2011 22:41:40 +0200	[thread overview]
Message-ID: <4044064.hXcqPjLJx7@weird> (raw)
In-Reply-To: <4E5118A4.50302@persimplex.net>

victor romanchuk writes:

> >> i had noticed that distcc is peevish about CFLAGS: these should be
> >> compatible on both client and server. in my case i made these
> >> similar on both machines (laptop is core2duo and desktop is
> >> core2quad; both are running  amd64 arch)
> > 
> > I don't think this is true - as long as the CHOST is identical, there
> > should be no problem.
> 
> CHOST defines the arch (i686, amd64, arm ..) whilst CFLAGS control gcc
> behavior and the binary code generation produced by compiler. in my case
> core2quad (q8300) i'm using in the desktop supports sse4.1 instruction
> set and notebook powered with core2duo (t7600) does not have that cpu
> feature. having option `-msse4.1' set in CFLAGS at desktop side will
> causes frequent compilation failures (initiated by distcc) or, in worst
> case - arbitrary crashes at notebook when running binaries compiled in
> distributed distcc environment

But how could the gcc on the desktop, called via distcc, even see the CFLAGS 
in the desktops make.conf? This just cannot be.
I have been using march=athlon-xp on my desktop, and yet used it as distcc 
server for my Pentium-III notebook for years. Worked fine.

	Wonko



  reply	other threads:[~2011-08-22 20:42 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-20 22:56 [gentoo-user] Hoping someone can help explain distcc to me Paul Hartman
2011-08-21  0:35 ` Peter Humphrey
2011-08-21  1:08   ` Paul Hartman
2011-08-21  1:58     ` Peter Humphrey
2011-08-21  2:46       ` Dale
2011-08-21  3:04         ` Matthew Finkel
2011-08-21  9:41           ` Peter Humphrey
2011-08-21 13:53             ` Joost Roeleveld
2011-08-21 16:27               ` Peter Humphrey
2011-08-21 17:42               ` Neil Bothwick
2011-08-24 11:04             ` Dale
2011-08-21  1:34 ` victor romanchuk
2011-08-21 10:38   ` Alex Schuster
2011-08-21 14:39     ` victor romanchuk
2011-08-22 20:41       ` Alex Schuster [this message]
2011-08-22 22:36         ` Bill Longman
2011-08-22 22:41         ` Bill Longman
2011-08-22 19:47 ` [gentoo-user] " Paul Hartman

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=4044064.hXcqPjLJx7@weird \
    --to=wonko@wonkology.org \
    --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