<div dir="ltr">On 21 February 2018 at 09:13, Maxin B. John <span dir="ltr"><<a href="mailto:maxin.john@intel.com" target="_blank">maxin.john@intel.com</a>></span> wrote:<br><div class="gmail_extra"><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Feb 21, 2018 at 12:09:36AM +0000, Burton, Ross wrote:<br>
<br>
>>On 19 February 2018 at 08:37, Maxin B. John <<a href="mailto:maxin.john@intel.com">maxin.john@intel.com</a>> wrote:<br>
>><br>
>> After moving to pkgconf, kmod package qa test fails without it.<br>
><br>
>Is this failing because pkgconf returns a full path (/path/to/my/build/usr/share/<wbr>bash-completion) instead of the path in the pc (/usr/share/bash-completion)? In the context of a target path in a makefile, the latter is correct and the former is very wrong.<br>
<br>
</span>Due to this line in <a href="http://configure.ac" rel="noreferrer" target="_blank">configure.ac</a>:<br>
with_bashcompletiondir=$($PKG_<wbr>CONFIG --variable=completionsdir bash-completion)<br>
<br>
combined with this:<br>
$(INSTALL_DATA) $$files "$(DESTDIR)$(<wbr>bashcompletiondir)"<span class=""><br></span></blockquote><div><br></div><div>Which you have to admit seems like the right thing to do... I'd argue that pkgconf is doing the wrong thing here.</div><div><br></div><div>Ross</div></div></div></div>