From: "Dominik Zajac" <banym.tuxaner@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] distcc with other distro (Debian)
Date: Mon, 6 Aug 2007 15:03:59 +0200 [thread overview]
Message-ID: <5158e0dd0708060603n5d868d90ub174698e098d294e@mail.gmail.com> (raw)
In-Reply-To: <200708040854.57974.bss03@volumehost.net>
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
Hi,
if there is an gcc version problem icecream is your friend
there you dont have so big problems with different gcc versions
and it is easier to configure
2007/8/4, Boyd Stephen Smith Jr. <bss03@volumehost.net>:
>
> On Friday 03 August 2007 01:34:37 am Ric de France wrote:
> > There may be a gotcha of glibc (or other)
> > incompatibilities / inconsistencies between Gentoo and Debian, but I'm
> > sure others on this list can advise you better.
>
> distcc only "farms out" the actual compiling. Pre-processing is done
> locally,
> so it uses your local header files. Linking is also done locally, so it
> will
> use your local libraries. [1]
>
> That said, if you have incompatible compilers (e.g. gcc-3.3 vs. gcc-3.4)
> you
> may have issues, and they may or may not be caught at link time.
>
> --
> Boyd Stephen Smith Jr. ,= ,-_-. =.
> bss03@volumehost.net ((_/)o o(\_))
> ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-'
> http://iguanasuicide.org/ \_/
>
> [1] distcc tries to be smart when passed a command-line that would do both
> compiling and (pre-processing or linking), but when it can't separate the
> stages, it will end up using your local compiler.
>
>
[-- Attachment #2: Type: text/html, Size: 1598 bytes --]
prev parent reply other threads:[~2007-08-06 13:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-02 10:30 [gentoo-user] distcc with other distro (Debian) Kacper Goc
2007-08-03 6:34 ` Ric de France
2007-08-04 13:54 ` Boyd Stephen Smith Jr.
2007-08-06 13:03 ` Dominik Zajac [this message]
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=5158e0dd0708060603n5d868d90ub174698e098d294e@mail.gmail.com \
--to=banym.tuxaner@googlemail.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