All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Marek <mmarek@suse.cz>
To: Randy Dunlap <rdunlap@infradead.org>,
	linux-kbuild@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Cc: linux-media <linux-media@vger.kernel.org>
Subject: Re: MANY errors while building media docbooks
Date: Tue, 17 Jun 2014 17:32:26 +0200	[thread overview]
Message-ID: <53A05F8A.6060108@suse.cz> (raw)
In-Reply-To: <539F2926.4020004@infradead.org>

On 2014-06-16 19:28, Randy Dunlap wrote:
> on Linux v3.16-rc1, building docbooks to a separate build directory
> (mkdir DOC; make O=DOC htmldocs) gives me more than 12,000 lines like this:
> 
> grep: ./Documentation/DocBook//vidioc-subdev-g-fmt.xml: No such file or directory
> grep: ./Documentation/DocBook//vidioc-subdev-g-frame-interval.xml: No such file or directory
> grep: ./Documentation/DocBook//vidioc-subdev-g-selection.xml: No such file or directory
> grep: ./Documentation/DocBook//vidioc-subscribe-event.xml: No such file or directory
> grep: ./Documentation/DocBook//media-ioc-device-info.xml: No such file or directory
> grep: ./Documentation/DocBook//media-ioc-enum-entities.xml: No such file or directory
> grep: ./Documentation/DocBook//media-ioc-enum-links.xml: No such file or directory
> grep: ./Documentation/DocBook//media-ioc-setup-link.xml: No such file or directory


Seems to be another fallout of the relative path patches, I'll have a look.

Thanks,
Michal


  reply	other threads:[~2014-06-17 15:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-16 17:28 MANY errors while building media docbooks Randy Dunlap
2014-06-17 15:32 ` Michal Marek [this message]
2014-06-18 15:27 ` [PATCH] Documentation: Fix DocBook build with relative $(srctree) Michal Marek
2014-06-18 16:12   ` Randy Dunlap

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=53A05F8A.6060108@suse.cz \
    --to=mmarek@suse.cz \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.