From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] alsa-utils: disable manpages generation from reStructured text
Date: Wed, 04 Jan 2017 17:11:42 +0100 [thread overview]
Message-ID: <87k2aa24ap.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <aa4954d6b24aa8262aa80964c01abe78de42b9d0.1483265273.git.baruch@tkos.co.il> (Baruch Siach's message of "Sun, 1 Jan 2017 12:07:53 +0200")
>>>>> "Baruch" == Baruch Siach <baruch@tkos.co.il> writes:
> The alsaucm man page rst source file is missing in the tarball. When rst2man
> is detected on the host, build fails:
> make[2]: *** No rule to make target 'alsaucm.1', needed by 'all-am'. Stop.
> Upstream added[1] the missing file to the tarball to fix this issue. But since
> we don't need the manpage to begin with, just disable rst2man to shorten build
> time by a few milliseconds.
> [1] http://git.alsa-project.org/?p=alsa-utils.git;a=commitdiff;h=c6bdde171e1532f7b37333a5a746b6e662f12c53
> Signed-off-by: Baruch Siach <baruch@tkos.co.il>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2017-01-04 16:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-01 10:07 [Buildroot] [PATCH] alsa-utils: disable manpages generation from reStructured text Baruch Siach
2017-01-01 10:38 ` Bernd Kuhls
2017-01-04 16:11 ` Peter Korsgaard [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=87k2aa24ap.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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