[snip]
Yes you understand it perfectly.
The $PATH thing is a dirty hack but works nicely in 99% of cases.
> And I probably have to do the same trick with the PATH on the host machines so
> that the cross compiler is run?
Check the file 'rc.local-addition' - this is how I start distcc on the
x86
Am Tuesday 31 August 2010 12:03:15 schrieb Stuart Winter:
> > is there a good guide how to set up distcc to build to help building arm
> > packages on my x86_64 and i486 hosts?
>
> Yep. Go back to the FTP site and download the script "dbuild" - I just
> put it there.
OK, had time to take a look a
On 1 September 2010 10:07, Stuart Winter wrote:
>
>> > Too bad shipping costs are so high between Germany & France :-(
>>
>> I've seen it somewhere in France for 19 ?, too. But IIRC this was one of
>
> I haven't had time to digest this site, so I'll only post the link with
> the thought that NewIT
> > Too bad shipping costs are so high between Germany & France :-(
>
> I've seen it somewhere in France for 19 ?, too. But IIRC this was one of
I haven't had time to digest this site, so I'll only post the link with
the thought that NewIT can ship it around Europe cheaper than GlobalScale
in the
Am Tuesday 31 August 2010 14:27:31 schrieb Christophe Lyon:
> > Did you use distcc there, too? What about moving all jobs to the other
> > hosts? I know there are still tasks left for the build host (linking?),
> > but no idea how much RAM they need.
> > But I've already thought that RAM will be a
> PS: Could the 128 MB RAM on my Dockstar be a problem, even if I use distcc?
I compiled MythTV on my DockStar using distcc so my SheevaPlug could
do all the grunt work (not cross-compiling in my case). RAM and CPU
consumption on the 'Star were very very low except linking; I had to
add 32MB of sw
> Why wouldn't you completely cross-build?
I tried when I first started AS back in 2002 and it wasn't a lot of fun.
Some will build nicely and easily, but there are some builds which require
the just-compiled binaries to be executed in order to create data files
or something like that.
Also, when
> Did you use distcc there, too? What about moving all jobs to the other hosts?
> I know there are still tasks left for the build host (linking?), but no idea
> how much RAM they need.
> But I've already thought that RAM will be a problem. Perhaps there may be some
> tricks that can help, e.g.
> ht
Am Tuesday 31 August 2010 12:03:15 schrieb Stuart Winter:
> > is there a good guide how to set up distcc to build to help building arm
> > packages on my x86_64 and i486 hosts?
>
> Yep. Go back to the FTP site and download the script "dbuild" - I just
> put it there.
Thanks, I'll have a look ther
> is there a good guide how to set up distcc to build to help building arm
> packages on my x86_64 and i486 hosts?
Yep. Go back to the FTP site and download the script "dbuild" - I just
put it there.
> PS: Could the 128 MB RAM on my Dockstar be a problem, even if I use distcc?
Depends what you
Hi,
is there a good guide how to set up distcc to build to help building arm
packages on my x86_64 and i486 hosts?
What I have right now:
I've compiled the cross toolchain from
ftp://ftp.armedslack.org/armedslack/armedslack-devtools/x-toolchain/
and installed it in /opt/arm/$LOCALARCH
I've ins
11 matches
Mail list logo
