On Fri, Nov 3, 2017 at 11:54 AM, Lasse Pouru
wrote:
> I have a bunch of old laptops that large builds such as texlive and ghc fail
> on, I'm assuming because of insufficient memory and disk space. If I've
> understood correctly, with Distcc I could build everything
On 2017-11-03 18:21, Ian Zimmerman wrote:
On 2017-11-03 02:53, Kai Peter wrote:
2. the shell script have to do some checks, e.g. the last run - I did
wrote a small 'include' script for that
Isn't your 'small include script' just another implementation of
run-crons?
No.
On 04/11/17 04:45, Wol's lists wrote:
> On 03/11/17 18:02, Rich Freeman wrote:
>> My understanding is that the preprocessing is all done on the target
>> machine, and the remote workers take all their marching orders from
>> there. The contents of CFLAGS, libraries, and so on don't matter on
>>
On 03/11/17 18:02, Rich Freeman wrote:
My understanding is that the preprocessing is all done on the target
machine, and the remote workers take all their marching orders from
there. The contents of CFLAGS, libraries, and so on don't matter on
the workers. You can build a program that requires
On Thu, Nov 2, 2017 at 6:53 PM, Kai Peter wrote:
>
> *I* recommend fcron, it is a bit under estimated. Beside its progressive
> design and w/o consulting the man page now again - AFAIR it can handle
> DST issues like above through options in fcrontab. But with my concept
On Fri, Nov 3, 2017 at 10:51 AM, Lasse Pouru
wrote:
>
> So the flags would have to be the same on all machines? What about the
> CPU architecture? Isn't there a way to cross-compile for a 32-bit
> machine (with minimal flags) on a 64-bit machine, and specify which
>
Wol's lists writes:
> On 03/11/17 16:54, Lasse Pouru wrote:
>> I have a bunch of old laptops that large builds such as texlive and
>> ghc fail on, I'm assuming because of insufficient memory and disk
>> space. If I've understood correctly, with Distcc I could build
>>
On 03/11/17 16:54, Lasse Pouru wrote:
I have a bunch of old laptops that large builds such as texlive and ghc fail
on, I'm assuming because of insufficient memory and disk space. If I've
understood correctly, with Distcc I could build everything on my main desktop
PC and have the binaries
On 2017-11-03 02:53, Kai Peter wrote:
> 2. the shell script have to do some checks, e.g. the last run - I did
> wrote a small 'include' script for that
Isn't your 'small include script' just another implementation of run-crons?
If not: how does it handle _missed_ jobs, if at all?
If you want
I have a bunch of old laptops that large builds such as texlive and ghc fail
on, I'm assuming because of insufficient memory and disk space. If I've
understood correctly, with Distcc I could build everything on my main desktop
PC and have the binaries transferred through network? How does this
10 matches
Mail list logo