All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Egger <chegger@amazon.de>
To: Ian Campbell <Ian.Campbell@citrix.com>
Cc: xen-devel <xen-devel@lists.xen.org>
Subject: Re: [PATCH v2] docs: make 'gmake dist-docs' work
Date: Mon, 13 May 2013 14:11:57 +0200	[thread overview]
Message-ID: <5190D88D.2020005@amazon.de> (raw)
In-Reply-To: <1368444872.537.78.camel@zakaz.uk.xensource.com>

On 13.05.13 13:34, Ian Campbell wrote:
> On Mon, 2013-05-13 at 12:25 +0100, Christoph Egger wrote:
>> On 13.05.13 12:44, Ian Campbell wrote:
>>> On Fri, 2013-05-10 at 15:07 +0100, Christoph Egger wrote:
>>>> doc: buildsystem fixes
>>>>
>>>> - use correct pathes (make gmake dist-docs from toplevel directory work)
>>>
>>> This ("make dist-docs") seems to work for me, how does it fail for you?
>>
>> On the toplevel directory '../xen' and '../config' point to
>> non-existent directories.
>> On the toplevel directory './gen-html-index' does not exist.
> 
> I'm confused. By toplevel you mean "xen.git" and not "xen.git/docs",
> right?

Yes.

> make dist-docs turns into "make -C docs install" (with DESTDIR set) so
> at the time ../xen or ../config are evaluated you should be in
> xen.git/docs.
>
> Or are you saying that you are extracting the docs subdir out to
> elsewhere? Perhaps you are doing an out of tree build or something else
> complex?

No.
My build procedure is:

- run configure
- gmake -jN dist-xen
- gmake -jN dist-tools
- gmake dist-docs

> I'm not suggesting your changes are wrong. I'd just like to understand
> the breakage...

I retried w/o my patch to get the error message:

xen.git$ gmake dist-docs
[...]
./xen-headers -O html/hypercall \
        -T 'arch-x86_64 - Xen public headers' \
        -X arch-x86_32 -X xen-x86_32 -X arch-arm \
        ../xen include/public include/xen/errno.h
gmake[1]: ./xen-headers: Command not found
gmake[1]: *** [html/hypercall/index.html] Error 127
gmake[1]: Leaving directory `/home/chegger/xen.git/docs'
gmake: *** [install-docs] Error 2
xen.git$

Since I am on the toplevel directory (or the shell at least)
calling ./xen-headers can't be found, of course. That's my thinking.

I also made general cleanup to make 'docs' consistent with the
other parts of the buildsystem.

Christoph

  reply	other threads:[~2013-05-13 12:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-10 14:07 [PATCH v2] docs: make 'gmake dist-docs' work Christoph Egger
2013-05-13 10:44 ` Ian Campbell
2013-05-13 11:25   ` Christoph Egger
2013-05-13 11:34     ` Ian Campbell
2013-05-13 12:11       ` Christoph Egger [this message]
2013-05-13 12:23         ` Ian Campbell
2013-05-13 12:59           ` Christoph Egger
2013-05-13 12:30         ` Tim Deegan

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=5190D88D.2020005@amazon.de \
    --to=chegger@amazon.de \
    --cc=Ian.Campbell@citrix.com \
    --cc=xen-devel@lists.xen.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.