https://bugs.kde.org/show_bug.cgi?id=503419
--- Comment #10 from Paul Floyd <pjfl...@wanadoo.fr> --- (In reply to Martin Liška from comment #9) > I can confirm that if I build the Valgrind with `make -j1`, then it builds > correctly, while previously I used `make -j4`. Do you run autogen.sh? The problem is either that parallel make is failing to produce pub/libvex_guest_offsets.h or somehow make is reaching coregrind before the header has been generated. I believe that automake is supposed to only run parallel make recursively in subdirectories. It's not parallel at the top level. Can you post the first 30 lines of make.log (up to the first C file compiled in VEX) when you do make distclean ./autogen.sh make -j 4 2>&1 | tee make.log (change the redirection to |& if you use [t]csh) -- You are receiving this mail because: You are watching all bug changes.
