Upstream will (and do) argue that $datadir is the right location as
these headers are architecture-independent.

Would the package manager do the right thing if the files didn't have
the libdir line in, so where bit-identical?

Ross

On 10 June 2018 at 20:01, Jeremy Puhlman <jpuhl...@mvista.com> wrote:
> * --data dir config option is only used to install pkgconfig
> * Installing into ${datadir} causes mutlilib conficts on install
>
>   file /usr/share/pkgconfig/applewmproto.pc conflicts between attempted
> installs of lib32-xorgproto-dev-2018.4-r0.i586 and
> xorgproto-dev-2018.4-r0.corei7_64
>   file /usr/share/pkgconfig/bigreqsproto.pc conflicts between attempted
> installs of lib32-xorgproto-dev-2018.4-r0.i586 and
> xorgproto-dev-2018.4-r0.corei7_64
>
> and so on.
>
> Signed-off-by: Jeremy Puhlman <jpuhl...@mvista.com>
> ---
>  meta/recipes-graphics/xorg-proto/xorg-proto-common.inc | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc 
> b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> index 7a417c9..7377283 100644
> --- a/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> +++ b/meta/recipes-graphics/xorg-proto/xorg-proto-common.inc
> @@ -14,7 +14,7 @@ S = "${WORKDIR}/${XORG_PN}-${PV}"
>  DEPENDS = "util-macros"
>
>  inherit autotools pkgconfig
> -EXTRA_OECONF = "--without-fop"
> +EXTRA_OECONF = "--without-fop --datadir=${libdir}"
>
>  UNKNOWN_CONFIGURE_WHITELIST += "--without-fop --without-xmlto --with-xmlto"
>
> --
> 2.6.2
>
> --
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/openembedded-core
-- 
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-core

Reply via email to