Projects / distcc / Comments

Comments for distcc

24 Jun 2008 20:58 fergushenderson

Re: Makefile oversights


> The Makefile doesn't support 'make

> uninstall' or 'make install-strip'

distcc 3.0 supports 'make uninstall'.

See http://distcc.org

06 Jul 2004 06:15 nigelhorne

Re: Makefile oversights
I take it that you agree that 'make install-strip' is
needed since you didn't say anything about it.

06 Jul 2004 06:12 bootswork

Re: Makefile oversights


> The Makefile doesn't support 'make

> uninstall' or 'make install-strip'

I think uninstall is better handled through package management. It is hard to do it reliably from a makefile.

03 May 2004 19:08 nigelhorne

Makefile oversights
The Makefile doesn't support 'make uninstall' or 'make install-strip'

12 Jan 2003 04:14 bootswork

Re: force to do remotely

> Maybe an external "knowledge-base", as
> file(1) has magic(5), would be the best
> solution.

If it turned out that there was sufficient interest in other tasks which fit within this general concept then some kind of scriptable system would be good.


The task has to be something where it's completely determined by a small number of input and output files, and by the command line. If this is all that's needed, it may be simpler just to use rsh or ssh. distcc is needed mostly because the input has to be preprocessed and checked before being sent across. If it's a simpler task like for example sort then just running it on some random machine will be sufficient.

12 Jan 2003 02:40 igor2

Re: force to do remotely
...

> It would be possible to add similar
> intelligence for other "batch" tasks
> that can be easily run remotely, such as
> perhaps compiling other languages.
> Perhaps distcc could be the start of a
> framework for such tools.


Maybe an external "knowledge-base", as file(1) has magic(5), would be the best solution.

12 Jan 2003 01:30 bootswork

Re: force to do remotely
I'm glad you like it. Thanks for saying so.


If I understand correctly, you'd like to use distcc to distribute tasks other than C compilation across the network.


distcc has some domain-specific knowledge about C files that lets it know how to distribute them across the network. For example, it needs to know how to run the preprocessor locally so as to remove dependencies on header files, and it needs to know which gcc options will conflict with remote compilation. (This is different to systems like MOSIX, which don't know anything about the tasks they're running, or dmake, which assumes you'll have a shared filesystem by some other means.)


It would be possible to add similar intelligence for other "batch" tasks that can be easily run remotely, such as perhaps compiling other languages. Perhaps distcc could be the start of a framework for such tools.

11 Jan 2003 00:44 igor2

force to do remotely
First of all, I really like distcc, it does distributed compiling better
than I ever expected from any distributed compiling stuff.

However, when I tried to use it for other purposes, I found out that
it done everything locally, since it wasn't sure that could be done
remotely. If there would be an option that would force distcc to do
a task remotely, that would not bother the original way of use, but
would make people able to do other things than compiling. Like running
cpu-intensive distributed mathematic calculations.

Screenshot

Project Spotlight

ReciJournal

An open, cross-platform journaling program.

Screenshot

Project Spotlight

Veusz

A scientific plotting package.