From: Randy Dunlap <rdunlap@xenotime.net>
To: <pefoley2@verizon.net>
Cc: <linux-kernel@vger.kernel.org>, <linux-kbuild@vger.kernel.org>,
Michal Marek <mmarek@suse.cz>
Subject: Re: [PATCH V2 0/7] kbuild: move scripts/basic/docproc.c to scripts/docproc.c
Date: Fri, 29 Apr 2011 15:59:15 -0700 [thread overview]
Message-ID: <20110429155915.f9059777.rdunlap@xenotime.net> (raw)
In-Reply-To: <4DBB3DD4.9000000@verizon.net>
On Fri, 29 Apr 2011 18:38:12 -0400 Peter Foley wrote:
> This patchset moves scripts/basic/docproc to scripts/docproc.
> This causes docproc to only be built for *doc targets rather than every
> time the kernel is compiled.
>
> Patches also attached as requested by Michal Marek.
Please test & fix when using O=output_dir.
$ mkdir DOC1
$ make -j4 O=DOC1 htmldocs
gives:
for dep in dvb media-entities.tmpl media-indices.tmpl v4l; do \
rm -f lnx-2639-rc5/DOC1/Documentation/DocBook/$dep \
&& ln -s lnx-2639-rc5/Documentation/DocBook/$dep lnx-2639-rc5/DOC1/Documentation/DocBook/ \
|| exit; \
done
DOCPROC Documentation/DocBook/80211.xml
DOCPROC Documentation/DocBook/alsa-driver-api.xml
DOCPROC Documentation/DocBook/debugobjects.xml
/bin/sh: lnx-2639-rc5/DOC1/scripts/docproc: No such file or directory
/bin/sh: lnx-2639-rc5/DOC1/scripts/docproc: No such file or directory
make[2]: *** [Documentation/DocBook/alsa-driver-api.xml] Error 1
make[2]: *** Waiting for unfinished jobs....
DOCPROC Documentation/DocBook/device-drivers.xml
make[2]: *** [Documentation/DocBook/debugobjects.xml] Error 1
/bin/sh: lnx-2639-rc5/DOC1/scripts/docproc: No such file or directory
make[2]: *** [Documentation/DocBook/device-drivers.xml] Error 1
/bin/sh: lnx-2639-rc5/DOC1/scripts/docproc: No such file or directory
make[2]: *** [Documentation/DocBook/80211.xml] Error 1
make[1]: *** [htmldocs] Error 2
make: *** [sub-make] Error 2
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-04-29 22:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 22:38 Peter Foley
2011-04-29 22:46 ` Randy Dunlap
2011-04-29 23:00 ` Michal Marek
2011-04-29 23:02 ` Randy Dunlap
2011-04-29 23:15 ` Peter Foley
2011-04-29 23:09 ` Peter Foley
2011-04-29 23:18 ` Randy Dunlap
2011-04-30 0:30 ` Peter Foley
2011-04-29 23:22 ` Arnaud Lacombe
2011-04-29 22:59 ` Randy Dunlap [this message]
2011-04-29 23:00 ` Randy Dunlap
2011-04-29 23:04 ` Randy Dunlap
2011-05-02 20:55 ` Michal Marek
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=20110429155915.f9059777.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=linux-kbuild@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mmarek@suse.cz \
--cc=pefoley2@verizon.net \
/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
all inboxes | Powered by JetHome®