From: Phil Blundell <pb@pbcl.net>
To: Khem Raj <raj.khem@gmail.com>
Cc: "openembedded-core@lists.openembedded.org"
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] pam: Add libtirpc to build dependencies
Date: Tue, 14 May 2013 17:24:53 +0100 [thread overview]
Message-ID: <1368548693.6920.70.camel@phil-desktop.brightsign> (raw)
In-Reply-To: <CAMKF1srAGRK=9BP5VrqhH50VrtWb+PFL5G5P-EEBPefb16xxTA@mail.gmail.com>
On Tue, 2013-05-14 at 07:33 -0700, Khem Raj wrote:
>
>
> On Tuesday, May 14, 2013, RicharPurdie
> <richard.purdie@linuxfoundation.org> wrote:
> > 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?
>
>
> When building from sstate the build of libpam would fail during
> configure if the machine who populated sstate had libtirpc staged
> before building libpam and with high parallelism its quite often
Does this mean that every image which uses pam will also drag in tirpc?
What's the cost in space and time for that?
p.
next prev parent reply other threads:[~2013-05-14 16:43 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
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 [this message]
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=1368548693.6920.70.camel@phil-desktop.brightsign \
--to=pb@pbcl.net \
--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