[PATCH v3 modular] build.sh: better integrate --autoresume and -n

Gaetan Nadon memsize at videotron.ca
Tue Jan 31 12:09:07 PST 2012

On 12-01-27 06:27 PM, Trevor Woerner wrote:
> From: Trevor Woerner <twoerner at gmail.com>
> The --autoresume <file> option allows a user to specify a <file> into which
> the build prints each module/component it has built. When a subsequent build
> is restarted with <file>, the build can skip all previously built modules,
> start with the last one (which is assumed to have failed previously), and
> continue on.
> The -n option allows a build to continue with subsequent modules even if
> one or more of the modules fails to build correctly.
> With this change, in addition to updating the --autoresume <file> with the
> name of the module/component just built, <file> is also updated with the
> status of the build. Therefore if you use -n you will have an --autoresume
> <file> which lists the build status of all the modules you wanted to build.
> A subsequent build using the --autoresume <file> will scan <file> looking
> for failures and attempt to build them before continuing on with the build
> from the end of the list.
> Signed-off-by: Trevor Woerner <twoerner at gmail.com>
A couple of minor problems. I wouldn't rock the code too much as we can
live with them. I am prepared to accept the patch as it is.

If autoresume reaches the last module in the autoresume file, it will
get built anyway, whether it has previously passed or failed.

--autoresume takes precedence over -o. They don't really make sense
together, so whichever one takes precedence is a luck of the draw and is

More information about the xorg-devel mailing list