Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-26 Thread David Faure
On Monday 11 January 2010, Lubos Lunak wrote: On Monday 11 of January 2010, Alexander Neundorf wrote: On Friday 08 January 2010, Lubos Lunak wrote: On Thursday 07 of January 2010, Oswald Buddenhagen wrote: a more generic solution would be recognizing a KDE4_TOOL_WRAPPER cmake

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-26 Thread Stephan Kulow
Am Dienstag 26 Januar 2010 schrieb David Faure: I often heard complaints that icecream is also launching too many ld jobs on the local machine at the same time; shouldn't icecream serialize that too, already, given that this -does- go through icecream already? I'm a bit confused as to why ld

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-26 Thread Thiago Macieira
Em Terça-feira 26 Janeiro 2010, às 14:34:43, Stephan Kulow escreveu: Am Dienstag 26 Januar 2010 schrieb David Faure: I often heard complaints that icecream is also launching too many ld jobs on the local machine at the same time; shouldn't icecream serialize that too, already, given that

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-11 Thread Alexander Neundorf
On Friday 08 January 2010, Lubos Lunak wrote: On Thursday 07 of January 2010, Oswald Buddenhagen wrote: On Thu, Jan 07, 2010 at 04:20:39PM +0100, Lubos Lunak wrote: I would like to commit the attached kdelibs/icecream patches, in order to avoid running into pathetic OOM situations on

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-11 Thread Lubos Lunak
On Monday 11 of January 2010, Alexander Neundorf wrote: On Friday 08 January 2010, Lubos Lunak wrote: On Thursday 07 of January 2010, Oswald Buddenhagen wrote: a more generic solution would be recognizing a KDE4_TOOL_WRAPPER cmake variable and prepending it to all non-c-compiler

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-11 Thread Thiago Macieira
Em Segunda-feira 11. Janeiro 2010, às 22.03.44, Alexander Neundorf escreveu: On Monday 11 January 2010, Lubos Lunak wrote: somebody has already reported them various cmake's shortcomings in dealing with parallel make when compared to unsermake. Please do :-) What is needed is for make

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-10 Thread Thiago Macieira
Em Sábado 9. Janeiro 2010, às 23.46.42, Michael Pyne escreveu: On Saturday 09 January 2010 12:58:35 Lubos Lunak wrote: On Friday 08 of January 2010, Oswald Buddenhagen wrote: this sounds like a nice thing to fix then. ;) Gee, I don't need it to be perfect, all I want is parallel make

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-10 Thread Oswald Buddenhagen
On Sun, Jan 10, 2010 at 10:01:48AM +0100, Thiago Macieira wrote: How about my better option? That works fine for everyone, for all programs, regardless of buildfarm? yes, i'd vote for polishing it up (making the variables generic), hosting it somewhere (qt labs?) and adding a respective hint

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-09 Thread Lubos Lunak
On Friday 08 of January 2010, Oswald Buddenhagen wrote: On Fri, Jan 08, 2010 at 04:09:27PM +0100, Lubos Lunak wrote: On Thursday 07 of January 2010, Oswald Buddenhagen wrote: for one, covering just meinproc is a bit shortsighted (i bet a few webkit links can blow your box just as nicely

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-09 Thread Michael Pyne
On Saturday 09 January 2010 12:58:35 Lubos Lunak wrote: On Friday 08 of January 2010, Oswald Buddenhagen wrote: this sounds like a nice thing to fix then. ;) Gee, I don't need it to be perfect, all I want is parallel make not to bring the machine down to its knees. If my improvement isn't

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-08 Thread Lubos Lunak
On Thursday 07 of January 2010, Oswald Buddenhagen wrote: On Thu, Jan 07, 2010 at 04:20:39PM +0100, Lubos Lunak wrote: I would like to commit the attached kdelibs/icecream patches, in order to avoid running into pathetic OOM situations on Linux. i'll comment on the icecream patch when i

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-08 Thread Thiago Macieira
Em Sexta-feira 08 Janeiro 2010, às 16:09:27, Lubos Lunak escreveu: Ok, but I'd prefer a more long-term solution, when I finally got to doing something about it. A more long-term solution would be for cmake to understand the concept of compile farms. In any case, I have solved this problem

Serializing possibly resource-intensive tasks such as meinproc

2010-01-07 Thread Lubos Lunak
Hello, I would like to commit the attached kdelibs/icecream patches, in order to avoid running into pathetic OOM situations on Linux. In short, run (or rather don't) 'make -j30' e.g. in kdebase/runtime/doc. As we have a nice icecream build farm here, I normally do such parallel builds,

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-07 Thread Allan Sandfeld Jensen
Hi Lubak This is an excelent idea (I've tried convincing Dirk to do something similar for years). But why are you detecting icecream and adding in cmake? Wouldn't it be better to simple add a meinproc link during icecream installation like it is done for cc and c++? Regards `Allan

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-07 Thread Lubos Lunak
On Thursday 07 of January 2010, Allan Sandfeld Jensen wrote: Hi Lubak This is an excelent idea (I've tried convincing Dirk to do something similar for years). But why are you detecting icecream and adding in cmake? Wouldn't it be better to simple add a meinproc link during icecream

Re: Serializing possibly resource-intensive tasks such as meinproc

2010-01-07 Thread Oswald Buddenhagen
On Thu, Jan 07, 2010 at 04:20:39PM +0100, Lubos Lunak wrote: I would like to commit the attached kdelibs/icecream patches, in order to avoid running into pathetic OOM situations on Linux. i'll comment on the icecream patch when i find the time. ping me on irc if i don't. but i find the kde