* Re: [gentoo-dev] crossdev, distcc, and multiple toolchains...
@ 2004-07-11 1:23 99% ` Lars Weiler
0 siblings, 0 replies; 1+ results
From: Lars Weiler @ 2004-07-11 1:23 UTC (permalink / raw
To: gentoo-dev
[-- Attachment #1: Type: text/plain, Size: 1248 bytes --]
* Jeremy Huddleston <eradicator@gentoo.org> [04/07/10 15:33 -0700]:
> Does anyone have any suggestions about this?
Be aware that if you want to provide distcc for more than
one architecture, you can't handle it with one daemon. You
have to configure it so, that every architecture's distccd
listens on another port, as it has to point to the correct
toolchain-directory. But that could be handled very easily
by editing the conf.d-file and provide the path to the
architectures' toolchain and another port.
Another thing is autoconfiguration, as you should first
check the found distcc-host for it's installed toolchain.
Kugelfang and I recently had the fun with our iBooks running
distcc, that other x86-users at our Gentoo User Meeting LAN
used nmap to find distcc-hosts and also wrote them in their
host-file :-) No wonder that the big-endian doped code
wouldn't run on their machine...
Today I found in the distcc-ML-archive a 'sanity-check'
script [1], which sends to every host a snippet of C-code
and fails, if the target does not provide the same
toolchain. In combination with nmap, this looks like a good
start for a kind of automated distcc-host-search.
Regards, Lars
[1] http://lists.samba.org/archive/distcc/2003q3/001301.html
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
^ permalink raw reply [relevance 99%]
Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2004-07-10 1:36 [gentoo-dev] New Global USE: crossdev Kumba
2004-07-10 20:38 ` Lisa Seelye
2004-07-10 22:33 ` [gentoo-dev] crossdev, distcc, and multiple toolchains... (was New global USE: crossdev) Jeremy Huddleston
2004-07-11 1:23 99% ` [gentoo-dev] crossdev, distcc, and multiple toolchains Lars Weiler
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox