linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bryan Henderson <bryanh@giraffe-data.com>
To: Lucas De Marchi <lucas.de.marchi@gmail.com>
Cc: linux-modules@vger.kernel.org
Subject: Re: Build fails when Xsltproc not present
Date: 24 Feb 2017 16:32:20 +0000	[thread overview]
Message-ID: <35934.bryanh@giraffe-data.com> (raw)
In-Reply-To: <CAKi4VAJ178U+Zx1SRsqROcPpEDiZmOckiRDOnNg==XnW=FZ5YA@mail.gmail.com> (lucas.de.marchi@gmail.com)

>They are already built on the distributed tarball, those coming from
>https://www.kernel.org/pub/linux/utils/kernel/kmod/
>If you are building from the git repository then yes, you need
>xsltproc. I pushed this patch:

Well, I built from the tarball, which I still have and see contains
e.g. man/kmod.8, and yet the build failed on me.  I will try to reproduce it
and see what happened, but looking at my local patch to the package, I see
that I 1) used --disable-manpages and 2) modified libkmod/docs/Makefile.in to
prevent that directory from building.  There are no man pages in libkmod/docs/
.

Your change is still right, of course.  The make files should be able to
tolerate these null values.

-- 
Bryan Henderson                                   San Jose, California

  reply	other threads:[~2017-02-24 16:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-20  0:50 Build fails when Xsltproc not present Bryan Henderson
2017-02-23 22:16 ` Lucas De Marchi
2017-02-24  3:13   ` Lucas De Marchi
2017-02-24  3:17     ` Bryan Henderson
2017-02-24  4:03       ` Lucas De Marchi
2017-02-24 16:32         ` Bryan Henderson [this message]
2017-02-26 23:09           ` Bryan Henderson

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=35934.bryanh@giraffe-data.com \
    --to=bryanh@giraffe-data.com \
    --cc=linux-modules@vger.kernel.org \
    --cc=lucas.de.marchi@gmail.com \
    /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).