From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/6 v3] pacakge/freerdp: disable building the manpages
Date: Sun, 7 Dec 2014 21:30:51 +0100 [thread overview]
Message-ID: <20141207213051.25f3d85d@free-electrons.com> (raw)
In-Reply-To: <80f81c6f8018e94d43c0a7ed7eec3ea3c50110ee.1417952276.git.yann.morin.1998@free.fr>
Dear Yann E. MORIN,
On Sun, 7 Dec 2014 12:39:27 +0100, Yann E. MORIN wrote:
> Building the manpages requires xsltproc, which might not be available.
> Also, who needs the manpages on the target anyway? ;-)
>
> Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr>
> Acked-by: Samuel Martin <s.martin49@gmail.com>
> ---
> package/freerdp/freerdp.mk | 2 ++
> 1 file changed, 2 insertions(+)
Applied, thanks.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2014-12-07 20:30 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-07 11:39 [Buildroot] [PATCH 0/6 v3] weston: new freerdp backend (branch yem/freerdp) Yann E. MORIN
2014-12-07 11:39 ` [Buildroot] [PATCH 1/6 v3] pacakge/freerdp: disable building the manpages Yann E. MORIN
2014-12-07 20:30 ` Thomas Petazzoni [this message]
2014-12-07 11:39 ` [Buildroot] [PATCH 2/6 v3] package/freerdp: do not forcibly depend on X.Org Yann E. MORIN
2014-12-07 11:39 ` [Buildroot] [PATCH 3/6 v3] package/freerdp: add options to enable/disable server and/or client Yann E. MORIN
2014-12-07 11:39 ` [Buildroot] [PATCH 4/6 v3] package/freerdp: also install to staging Yann E. MORIN
2014-12-07 11:39 ` [Buildroot] [PATCH 5/6 v3] package/freerdp: install server key and certificate Yann E. MORIN
2014-12-08 22:17 ` Samuel Martin
2014-12-07 11:39 ` [Buildroot] [PATCH 6/6 v3] package/weston: add support for the RDP compositor Yann E. MORIN
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=20141207213051.25f3d85d@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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