From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] pam: Add libtirpc to build dependencies
Date: Tue, 14 May 2013 13:05:12 +0300 [thread overview]
Message-ID: <1368525912.25898.15.camel@ted> (raw)
In-Reply-To: <1368513918-16448-1-git-send-email-raj.khem@gmail.com>
On Mon, 2013-05-13 at 23:45 -0700, Khem Raj wrote:
> libtirpc is looked for by configure and if found
> its enabled. So lets make it consistent and enable
> it always
>
> Signed-off-by: Khem Raj <raj.khem@gmail.com>
> ---
> meta/recipes-extended/pam/libpam_1.1.6.bb | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
What is the benefit of this dependency?
Cheers,
Richard
next prev parent reply other threads:[~2013-05-14 10:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 6:45 [PATCH] pam: Add libtirpc to build dependencies Khem Raj
2013-05-14 10:05 ` Richard Purdie [this message]
2013-05-14 14:33 ` Khem Raj
2013-05-14 14:41 ` Paul Eggleton
2013-05-14 15:49 ` Khem Raj
2013-05-14 16:24 ` Phil Blundell
2013-05-14 21:10 ` Khem Raj
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=1368525912.25898.15.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.org \
--cc=raj.khem@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