[haiku-development] Re: Several script-based errors in the build system
- From: "Ingo Weinhold" <ingo_weinhold@xxxxxx>
- To: haiku-development@xxxxxxxxxxxxx
- Date: Mon, 06 Jul 2009 02:15:46 +0200
-------- Original-Nachricht --------
> Datum: Sun, 5 Jul 2009 23:02:10 +0000
> Von: Matt Madia <mattmadia@xxxxxxxxx>
> While working on build-o-matic, i've noticed a few unique errors that
> are from various shell scripts that the build system utilizes.
> This doesn't appear to be local to a particular OS.
> Though, it seems to occur more frequently with more than one jam job (
> jam -jX, where X > 2)
X >= 2 even. :-)
> Thing is, even if one of these errors occur, jam seems to return 0 (no
> error)
> Should jam be treating these as an actual error?
Jam is not really to blame. The problem is that in such a case the scripts
generated by the build system contain scrambled lines. Since the scripts don't
abort when an error is encountered and the last command is one that doesn't
fail, jam can't know that something went wrong.
> If wanted, i could find log files that do contain these errors.
That's not so interesting. They will just show weird errors (syntax errors,
missing files, etc.) in the generated files. There are already several Trac
tickets covering problems related to -jX builds.
For the time being the only really reliable method it to build with a single
job. I suppose for build-o-matic it isn't even a big problem, as you could just
run the builds for the different target architectures/ABIs in parallel.
CU, Ingo
Other related posts:
