linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Randy Dunlap <rdunlap@infradead.org>
Cc: Jonathan Corbet <corbet@lwn.net>,
	pioneer695 <pioneer695@protonmail.com>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>
Subject: Re: make cleandocs issue: rm -rf /output when obj not defined
Date: Tue, 27 Jul 2021 12:25:34 +0100	[thread overview]
Message-ID: <YP/tLnwb86RTTiRf@casper.infradead.org> (raw)
In-Reply-To: <5e93f77f-79a5-7dc9-287e-a48865afd133@infradead.org>

On Sun, Jul 25, 2021 at 01:53:30PM -0700, Randy Dunlap wrote:
> 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.

Perhaps we should rename Documentation/Makefile to Documentation/Kbuild
to prevent this confusion?

  reply	other threads:[~2021-07-27 11:28 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
2021-07-27 11:25     ` Matthew Wilcox [this message]
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=YP/tLnwb86RTTiRf@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=corbet@lwn.net \
    --cc=linux-doc@vger.kernel.org \
    --cc=pioneer695@protonmail.com \
    --cc=rdunlap@infradead.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).