<br><br>On Tuesday, May 14, 2013, Paul Eggleton <<a href="mailto:paul.eggleton@linux.intel.com">paul.eggleton@linux.intel.com</a>> wrote:<br>> On Tuesday 14 May 2013 07:33:49 Khem Raj wrote:<br>>> On Tuesday, May 14, 2013, RicharPurdie <<a href="mailto:richard.purdie@linuxfoundation.org">richard.purdie@linuxfoundation.org</a>><br>
>> wrote:<br>>> > On Mon, 2013-05-13 at 23:45 -0700, Khem Raj wrote:<br>>> >> libtirpc is looked for by configure and if found<br>>> >> its enabled. So lets make it consistent and enable<br>
>> >> it always<br>>> >><br>>> >> Signed-off-by: Khem Raj <<a href="mailto:raj.khem@gmail.com">raj.khem@gmail.com</a>><br>>> >> ---<br>>> >><br>>> >> meta/recipes-extended/pam/<a href="http://libpam_1.1.6.bb">libpam_1.1.6.bb</a> | 2 +-<br>
>> >> 1 file changed, 1 insertion(+), 1 deletion(-)<br>>> ><br>>> > What is the benefit of this dependency?<br>>><br>>> When building from sstate the build of libpam would fail during configure<br>
>> if the machine who populated sstate had libtirpc staged before building<br>>> libpam and with high parallelism its quite often<br>><br>> Understood, but the question was what is the benefit of the added dependency on<br>
> libtirpc; i.e. should we really be explicitly enabling this or explicitly<br>> disabling it?<br><br>There is no knob to disable/disable it. Adding one would be ideal but for another day<br>><br>> Cheers,<br>
> Paul<br>><br>> --<br>><br>> Paul Eggleton<br>> Intel Open Source Technology Centre<br>>