[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJZ5v0gu_2wkncukKK7u340KLzSCVL_7F9cJTz3wVhxfogR8NQ@mail.gmail.com>
Date: Fri, 21 Feb 2020 09:40:01 +0100
From: "Rafael J. Wysocki" <rafael@...nel.org>
To: Kees Cook <keescook@...omium.org>
Cc: "Rafael J. Wysocki" <rafael@...nel.org>,
Jonathan Corbet <corbet@....net>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
"open list:DOCUMENTATION" <linux-doc@...r.kernel.org>
Subject: Re: [Regression] Docs build broken by commit 51e46c7a4007
On Thu, Feb 20, 2020 at 11:49 PM Kees Cook <keescook@...omium.org> wrote:
>
> On Thu, Feb 20, 2020 at 10:44:35PM +0100, Rafael J. Wysocki wrote:
> > On Thu, Feb 20, 2020 at 9:05 PM Kees Cook <keescook@...omium.org> wrote:
> > >
> > > On Thu, Feb 20, 2020 at 07:50:47PM +0100, Rafael J. Wysocki wrote:
> > > > On two of my systems the docs build has been broken by commit
> > > > 51e46c7a4007 ("docs, parallelism: Rearrange how jobserver reservations
> > > > are made").
> > > >
> > > > The symptom is that the build system complains about the "output"
> > > > directory not being there and returns with an error.
> > > >
> > > > Reverting the problematic commit makes the problem go away.
> > >
> > > How strange! This must be some race in the parallel build.
> >
> > I don't think so, I didn't use -j with htmldocs builds.
>
> What version of Sphinx do you have?
1.6.5 (I realize that it is older than recommended, but it had been
working fine before 5.5-rc1 :-)).
> > And you know what, adding "-j 2" to the command line actually makes it work. :-)
>
> Without a -j argument, the Documentation build has been using -jauto on
> Sphinx itself.
Well, maybe this particular version of Sphinx has problems with that.
> > > AFAICT, "output" is made in the first sub-target (Documentation/media). This
> > > doesn't look entirely stable (there's no ordering implied by the "all"
> > > target in there)...
> > >
> > > Does this work for you?
> >
> > No, it doesn't.
>
> Well now I'm really baffled. What make target are you specifying? I was
> assuming you were doing "make htmldocs"?
I've tried that too, but most often I do something like "make
O=../build/somewhere/ htmldocs".
But I can do "make O=../build/somewhere/ -j 2 htmldocs" too just fine. :-)
Cheers!
Powered by blists - more mailing lists