[Bug bootstrap/41337] [LTO] Parallel build failure

[Bug bootstrap/41337] [LTO] Parallel build failure

[dmitrij.ledkov at ubuntu dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41337

Dima <dmitrij.ledkov at ubuntu dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |dmitrij.ledkov at ubuntu
                   |                            |dot com

--- Comment #2 from Dima <dmitrij.ledkov at ubuntu dot com> 2010-11-16 21:53:42 UTC ---
I have the same error. Would please share your pilot error and how you have
fixed it? Maybe I'm doing the same thing....

[Bug bootstrap/41337] [LTO] Parallel build failure

[rwild at gcc dot gnu.org]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41337

Ralf Wildenhues <rwild at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rwild at gcc dot gnu.org

--- Comment #3 from Ralf Wildenhues <rwild at gcc dot gnu.org> 2010-11-17 16:52:03 UTC ---
If you encounter parallel build failures, please post exact revision that was
built, configure command line, build system type, number of processors on the
box, N argument in 'make -jN', and ideally also the likelihood (in precent)
that the build fails, if it is not deterministic.  Please also post the last
300 or so lines of build output, and maybe check whether it always fails in the
same spot.

It is not too hard to pinpoint parallel build failures but only if there is
enough data available.

[Bug bootstrap/41337] [LTO] Parallel build failure

[dmitrij.ledkov at ubuntu dot com]

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41337

--- Comment #4 from Dima <dmitrij.ledkov at ubuntu dot com> 2010-11-17 21:02:58 UTC ---
(In reply to comment #3)
> If you encounter parallel build failures, please post exact revision that was
> built, configure command line, build system type, number of processors on the
> box, N argument in 'make -jN', and ideally also the likelihood (in precent)
> that the build fails, if it is not deterministic.  Please also post the last
> 300 or so lines of build output, and maybe check whether it always fails in the
> same spot.
> 

I'm building a cross-compiler: build/host = gnu-linux; target =
i686-w64-mingw32. I've been using gcc-4.4 branch this whole week (will test
again with trunk when I have time). It is fully deterministic (100% fail rate
at the same spot) when I supply --with-build-libsubdir pointing to the
$prefix/$target-triplet/lib. But the mentioned value for --with-build-libsubdir
option is bogus and doesn't make sense.

> It is not too hard to pinpoint parallel build failures but only if there is
> enough data available.

I no longer believe my error was to do with parallel make, it was the error
between the keyboard and the chair =) in other words "pilot error".

If someone else will come across with

> make[1]: *** No rule to make target `build/gencondmd', needed by `s-condmd'

Check your config and make sure it is sane =)

[Bug bootstrap/41337] [LTO] Parallel build failure

[hjl dot tools at gmail dot com]

------- Comment #1 from hjl dot tools at gmail dot com  2009-09-11 15:01 -------
Pilot error.


-- 

hjl dot tools at gmail dot com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|                            |INVALID


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=41337