mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <randy.dunlap@oracle.com>
To: Mauro Carvalho Chehab <mchehab@infradead.org>
Cc: lkml <linux-kernel@vger.kernel.org>, linux-media@vger.kernel.org
Subject: Re: docbooks fatal build error (v4l & dvb)
Date: Tue, 22 Sep 2009 14:47:49 -0700	[thread overview]
Message-ID: <20090922144749.3b968984.randy.dunlap@oracle.com> (raw)
In-Reply-To: <20090922143601.f5953a04.randy.dunlap@oracle.com>

On Tue, 22 Sep 2009 14:36:01 -0700 Randy Dunlap wrote:

> On Tue, 22 Sep 2009 18:28:27 -0300 Mauro Carvalho Chehab wrote:
> 
> > Hi Randy,
> > 
> > Em Tue, 22 Sep 2009 12:42:48 -0700
> > Randy Dunlap <randy.dunlap@oracle.com> escreveu:
> > 
> > > 2.6.31-git11:  this prevents other docbooks from being built.
> > > 
> > > mkdir -p /linux-2.6.31-git11/Documentation/DocBook/media/
> > > cp /linux-2.6.31-git11/Documentation/DocBook/dvb/*.png /linux-2.6.31-git11/Documentation/DocBook/v4l/*.gif /linux-2.6.31-git11/Documentation/DocBook/media/
> > > cp: cannot stat `/linux-2.6.31-git11/Documentation/DocBook/dvb/*.png': No such file or directory
> > > cp: cannot stat `/linux-2.6.31-git11/Documentation/DocBook/v4l/*.gif': No such file or directory
> > > make[1]: *** [media] Error 1
> > 
> > 
> > Hmm... here, it is working fine. I've did it on a newer tree, cloned from Linus
> > one. This is the last patch on it:
> 
> OK, it's probably just because I used a git snapshot (-git11).
> Sorry for the noise.

Confirmed, linus.git works fine.

---
~Randy

      reply	other threads:[~2009-09-22 21:48 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-22 19:42 Randy Dunlap
2009-09-22 21:28 ` Mauro Carvalho Chehab
2009-09-22 21:36   ` Randy Dunlap
2009-09-22 21:47     ` Randy Dunlap [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=20090922144749.3b968984.randy.dunlap@oracle.com \
    --to=randy.dunlap@oracle.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@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

all inboxes | Powered by JetHome®