On Sun, Sep 09, 2007 at 11:58:26AM +0200, Sven Panne wrote:
> On Saturday 08 September 2007 19:33, Stefan O'Rear wrote:
> > [...]
> > $(MAKE) always includes the flags (at least with gnumake), cf "info make
> > MAKE\ Variable".
>
> Nope... Don't stop reading manuals prematurely: ;-)
>
> http://
Sven Panne wrote:
On Saturday 08 September 2007 19:33, Stefan O'Rear wrote:
[...]
$(MAKE) always includes the flags (at least with gnumake), cf "info make
MAKE\ Variable".
Nope... Don't stop reading manuals prematurely: ;-)
http://www.gnu.org/software/make/manual/html_node/Options_002fRecur
On Saturday 08 September 2007 19:33, Stefan O'Rear wrote:
> [...]
> $(MAKE) always includes the flags (at least with gnumake), cf "info make
> MAKE\ Variable".
Nope... Don't stop reading manuals prematurely: ;-)
http://www.gnu.org/software/make/manual/html_node/Options_002fRecursion.html
Easy
m monitor), because the sub-make
> gets the -j option.
>
> There were some discussions about parallel builds some time ago, but I can't
> remember what the conclusion was. Even if a large-scale parallelism on
> package level might be tricky, having parallel builds within a packag
m monitor), because the sub-make
> gets the -j option.
>
> There were some discussions about parallel builds some time ago, but I can't
> remember what the conclusion was. Even if a large-scale parallelism on
> package level might be tricky, having parallel builds within a pac
s ghc/libraries not ready for -j2 and friends or
is this an unintentional omission? The build of the compiler itself *is*
nicely parallelized (confirmed by my system monitor), because the sub-make
gets the -j option.
There were some discussions about parallel builds some time ago, but I can&#
Thu Mar 15 05:24:57 PDT 2007 [EMAIL PROTECTED]
* Added support for parallel builds
With this patch, one can define the degree of build parallelism via a 'jobs'
rpm variable. A comfortable way to use this is having a ~/.rpmmacros file with
a line like:
%jobs 2
Alt
