From: Jonathan Corbet <corbet@lwn.net>
To: Mauro Carvalho Chehab <mchehab@kernel.org>
Cc: kbuild test robot <lkp@intel.com>,
kbuild-all@01.org, linux-doc@vger.kernel.org,
linux-media@vger.kernel.org
Subject: Re: [lwn:docs-next 25/31] htmldocs: /bin/bash: ./scripts/sphinx-pre-install: No such file or directory
Date: Tue, 4 Jun 2019 07:41:37 -0600 [thread overview]
Message-ID: <20190604074137.7cf859d6@lwn.net> (raw)
In-Reply-To: <20190604063318.34c7bde5@coco.lan>
On Tue, 4 Jun 2019 06:33:18 -0300
Mauro Carvalho Chehab <mchehab@kernel.org> wrote:
> Hi Jon,
>
> The fix is incomplete... there are other occurrences of this
> within the Makefile:
Argh...at least I was on the right track :) I'll clean up the rest today.
Thanks,
jon
prev parent reply other threads:[~2019-06-04 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 20:19 [lwn:docs-next 25/31] htmldocs: /bin/bash: ./scripts/sphinx-pre-install: No such file or directory kbuild test robot
2019-05-30 21:32 ` Jonathan Corbet
2019-06-04 9:33 ` Mauro Carvalho Chehab
2019-06-04 13:41 ` Jonathan Corbet [this message]
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=20190604074137.7cf859d6@lwn.net \
--to=corbet@lwn.net \
--cc=kbuild-all@01.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=lkp@intel.com \
--cc=mchehab@kernel.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: link
Be 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 NNTP newsgroup(s).