Re: [PATCH] Explicitly set CHECKPOLICY path to native sysroot.

[Philip Tricca <flihp@twobit.us>]

Probably should add that I'm not very fond of having the path hard coded
like this. Makes for a dependency on the install location from the
checkpolicy recipe. For the short term this fixes the immediate issue
though. Feedback on the "right way" to reference / find this binary
would be appreciated.

Regards,
- Philip

On 10/04/2013 12:39 PM, Philip Tricca wrote:
> This prevents the Xen 'configure' script from using the
> checkpolicy binary from the host system if it's installed.
> ---
>  recipes-extended/xen/xen_4.3.0.bb |    3 +++
>  1 file changed, 3 insertions(+)
> 
> diff --git a/recipes-extended/xen/xen_4.3.0.bb b/recipes-extended/xen/xen_4.3.0.bb
> index 2e1a29f..5d26000 100644
> --- a/recipes-extended/xen/xen_4.3.0.bb
> +++ b/recipes-extended/xen/xen_4.3.0.bb
> @@ -557,6 +557,9 @@ export CROSS_COMPILE="${TARGET_PREFIX}"
>  # overide LDFLAGS to allow xen to build without: "x86_64-oe-linux-ld: unrecognized option '-Wl,-O1'"
>  export LDFLAGS=""
>  
> +# use checkpolicy from  sysroot
> +export CHECKPOLICY="${STAGING_DIR_NATIVE}${bindir}/checkpolicy"
> +
>  do_configure() {
>      # fixup qemu-xen-traditional pciutils check hardcoded to test ${includedir}/pci
>      sed -i 's/\/usr\/include\/pci/$(STAGING_INCDIR)\/pci/g' ${S}/tools/qemu-xen-traditional/xen-hooks.mak