On May 14, 2013, at 9:24 AM, Phil Blundell <[email protected]> wrote: > On Tue, 2013-05-14 at 07:33 -0700, Khem Raj wrote: >> >> >> On Tuesday, May 14, 2013, RicharPurdie >> <[email protected]> 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 <[email protected]> >>>> --- >>>> 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?
yes. > What's the cost in space and time for that? > 142K - libtirpc.so.1.0.10 Time I can't quantify, depends on your build system e.g. on my system built from scratch with and without dependency showed few (20+) seconds difference. It might vary for you. > p. > > _______________________________________________ Openembedded-core mailing list [email protected] http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
