linux-modules.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Lucas De Marchi <lucas.de.marchi@gmail.com>
To: Bryan Henderson <bryanh@giraffe-data.com>
Cc: linux-modules <linux-modules@vger.kernel.org>
Subject: Re: Build fails when Xsltproc not present
Date: Thu, 23 Feb 2017 19:13:59 -0800	[thread overview]
Message-ID: <CAKi4VA+dom7PwCkfCNrWH-1sEo5sLjOOuBNRKhH+cFRjvefr1g@mail.gmail.com> (raw)
In-Reply-To: <CAKi4VAKo=LP783aZcCuwmq3ubzaJL7S9FdmCOrv8UPr+vgAGPw@mail.gmail.com>

On Thu, Feb 23, 2017 at 2:16 PM, Lucas De Marchi
<lucas.de.marchi@gmail.com> wrote:
> On Mon, Dec 19, 2016 at 4:50 PM, Bryan Henderson
> <bryanh@giraffe-data.com> wrote:
>>
>> I believe in that case, it should just skip building the man pages.
>
> We don't do auto-enabling/disabling.
>
>> Or make 'configure' fail and suggest --disable-manpages.
>>
>> Or make the make fail gracefully, telling you you don't have the tools
>> necessary to create man pages and suggesting --disable-manpages.
>
> Failing on configure phase would be the desired solution. I'll take a
> look on this for next release, but if  you have a patch ready it would
> be appreciated.

Actually I did it on make because man pages are  with the distributed tarball

Lucas De Marchi

  reply	other threads:[~2017-02-24  3:13 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 [this message]
2017-02-24  3:17     ` Bryan Henderson
2017-02-24  4:03       ` Lucas De Marchi
2017-02-24 16:32         ` Bryan Henderson
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=CAKi4VA+dom7PwCkfCNrWH-1sEo5sLjOOuBNRKhH+cFRjvefr1g@mail.gmail.com \
    --to=lucas.de.marchi@gmail.com \
    --cc=bryanh@giraffe-data.com \
    --cc=linux-modules@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).