From: Luca Barbato <lu_zero@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] distcc and precompiled headers
Date: Fri, 18 May 2007 15:26:19 +0200 [thread overview]
Message-ID: <464DA97B.5090800@gentoo.org> (raw)
In-Reply-To: <47748.192.168.2.155.1179492070.squirrel@www.aei-tech.com>
Caleb Tennis wrote:
> Based on some recent findings, it looks like the two above mentioned features don't
> work together. pch don't get distributed to distcc nodes, so they're basically
> mutually exclusive. However, distcc is a FEATURE and pch are a USE flag.
>
> Should we just put a check in each ebuild that uses the pch use flag, make an
> eclass, or build something into the package manager(s) ? Thoughts?
Enhance distcc?
lu
--
Luca Barbato
Gentoo/linux Gentoo/PPC
http://dev.gentoo.org/~lu_zero
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-05-18 13:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 12:41 [gentoo-dev] distcc and precompiled headers Caleb Tennis
2007-05-18 13:26 ` Luca Barbato [this message]
2007-05-19 6:59 ` [gentoo-dev] " Steve Long
2007-05-19 15:38 ` [gentoo-dev] " Kevin F. Quinn
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=464DA97B.5090800@gentoo.org \
--to=lu_zero@gentoo.org \
--cc=gentoo-dev@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