public inbox for frysk-bugzilla@sourceware.org help / color / mirror / Atom feed
From: "pmachata at redhat dot com" <sourceware-bugzilla@sourceware.org> To: frysk-bugzilla@sourceware.org Subject: [Bug general/5183] broken build with -j>1 Date: Tue, 16 Oct 2007 12:55:00 -0000 [thread overview] Message-ID: <20071016125446.18818.qmail@sourceware.org> (raw) In-Reply-To: <20071015190334.5183.swagiaal@redhat.com> ------- Additional Comments From pmachata at redhat dot com 2007-10-16 12:54 ------- The problem seems to be with two .g.antlered implicit rules being run in parallel, which step on each other's .antlr-fixes temporary files. In this particular case, this is caused by missing rule: frysk/expr/CExprEvaluator.antlered: frysk/expr/Completer.antlered Makefile rules are generated from importVocab directives in .g files by way of Makefile.gen.sh, so frysk really tries to give make proper parallelization hints. So the real problem is with temporary file handling. I believe what happens is that antlr-warnings.awk produces e.g. CExprEvaluator.antlr-fixes, when suddently the other make invocation removes it via 'rm -f $$d/*.antlr-fixes'. So the file being just built is removed, and misses its beginning. Later on, there's 'for fix in $$d/*.antlr-fixes', which picks both files, the "healthy" one as well as the truncated one, and tries to use them as a sed source. For that reason both parallel make branches fail. -- http://sourceware.org/bugzilla/show_bug.cgi?id=5183 ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.
next prev parent reply other threads:[~2007-10-16 12:55 UTC|newest] Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top 2007-10-15 19:03 [Bug general/5183] New: " swagiaal at redhat dot com 2007-10-16 12:55 ` pmachata at redhat dot com [this message] 2008-06-11 20:09 ` [Bug general/5183] " cagney at redhat dot com
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20071016125446.18818.qmail@sourceware.org \ --to=sourceware-bugzilla@sourceware.org \ --cc=frysk-bugzilla@sourceware.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).