From: Randy Dunlap <rdunlap@infradead.org>
To: Jonathan Corbet <corbet@lwn.net>, pioneer695 <pioneer695@protonmail.com>
Cc: "linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: make cleandocs issue: rm -rf /output when obj not defined
Date: Sun, 25 Jul 2021 13:53:30 -0700 [thread overview]
Message-ID: <5e93f77f-79a5-7dc9-287e-a48865afd133@infradead.org> (raw)
In-Reply-To: <875ywyw3ui.fsf@meer.lwn.net>
On 7/25/21 1:11 PM, Jonathan Corbet wrote:
> pioneer695 <pioneer695@protonmail.com> writes:
>
>> In an attempt to get some readable documentation I cloned the git repository
>> to check how the PDF format is.
>>
>> Entered Documentation and proceeded with:
>>
>> make pdfdocs
Hi,
I'm curious about this part above. Are you saying that you did:
cd Documentation
make pdfdocs
I've never tried that and don't expect it to be done that way.
I do (from the top of the kernel source tree):
make pdfdocs
or
make htmldocs
with no problems, other than I may not have all of the latex
tools installed.
>> which failed, so to start fresh, my thought was that:
>>
>> make cleandocs
>>
>> would be the next step before anything else. But, this resulted in:
>>
>> rm -rf /output
>
> That's not good...
>
>> as $(obj) for some reason was empty.
>
> *This* would appear to be the real problem. If you could do some
> digging to figure out why that happened, I suspect that would be
> useful.
>
>> Makefile for Documentation has:
>>
>> BUILDDIR = $(obj)/output
>>
>> cleandocs:
>> $(Q)rm -rf $(BUILDDIR)
>>
>>
>> This should (at least?!) be:
>>
>> BUILDDIR = ./$(obj)/output
>> or:
>> $(Q)rm -rf ./$(BUILDDIR)
>
> These would break builds for a lot of people and are not the right
> solution.
--
~Randy
next prev parent reply other threads:[~2021-07-25 20:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-24 19:56 make cleandocs issue: rm -rf /output when obj not defined pioneer695
2021-07-25 20:11 ` Jonathan Corbet
2021-07-25 20:53 ` Randy Dunlap [this message]
2021-07-27 11:25 ` Matthew Wilcox
2021-08-17 21:23 ` pioneer695
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=5e93f77f-79a5-7dc9-287e-a48865afd133@infradead.org \
--to=rdunlap@infradead.org \
--cc=corbet@lwn.net \
--cc=linux-doc@vger.kernel.org \
--cc=pioneer695@protonmail.com \
/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).