Build failure due to make -j8

[Gérard Milmeister]

I was trying to build a new release of genius, but the build failed due
to unsatisifed make dependencies on machines that use make -j8 or make
-j4 instead of the usual make -j2 and indeed when I tried  make -j8 on
my (uni-processor) machine, it failed too. The package is automake
based. Has this behavior been observed with other packages? Could it be
a problem with make or automake, or would it be specific to the package
only?

Gérard

[Andrew Haley]

Gérard Milmeister wrote:
>  I was trying to build a new release of genius, but the build failed
> due
>  to unsatisifed make dependencies on machines that use make -j8 or make
>  -j4 instead of the usual make -j2 and indeed when I tried  make -j8 on
>  my (uni-processor) machine, it failed too. The package is automake
>  based. Has this behavior been observed with other packages? Could it be
>  a problem with make or automake, or would it be specific to the package
>  only? 
While automake may be at fault, it's almost certainly package-specific.

Andrew.

[Debarshi Ray]

Makefiles generated using older (<1.10) versions of Automake may have
bugs causing failure of parallel builds. Also have a look at:
http://fedoraproject.org/wiki/Packaging/Guidelines#head-525c7d76890cb22df...

I have encountered such faulty Makefiles in some of my packages too.

Cheers,
Debarshi
-- 
Free software for the Indian community:
* ftp://fedora.glug-nith.org/ (Fedora)
* http://gnu.glug-nith.org/ (GNU)
* http://mirror.wbut.ac.in/ (CRAN, Fedora, Mozilla, TLDP)

[Dennis Gilmore]

On Monday 28 January 2008, Gérard Milmeister wrote:
>  I was trying to build a new release of genius, but the build failed
> due
>  to unsatisifed make dependencies on machines that use make -j8 or make
>  -j4 instead of the usual make -j2 and indeed when I tried  make -j8 on
>  my (uni-processor) machine, it failed too. The package is automake
>  based. Has this behavior been observed with other packages? Could it be
>  a problem with make or automake, or would it be specific to the package
>  only?
>
>  Gérard 
most likely its in your package.  going fowrawd we will see in the build 
system -j32   and quite probably -j64  what generally happens is that things 
get built out of order with the higher thread count.

Dennis