[OE-core] [PATCH v2] ghostscript: Define COMPATIBLE_HOST with supported platforms

Nathan Rossi nathan at nathanrossi.com
Thu Nov 8 13:48:47 UTC 2018


On Thu, 8 Nov 2018 at 23:44, Burton, Ross <ross.burton at intel.com> wrote:
>
> On Thu, 8 Nov 2018 at 13:30, Khem Raj <raj.khem at gmail.com> wrote:
> > > --- a/meta/recipes-extended/ghostscript/ghostscript_9.25.bb
> > > +++ b/meta/recipes-extended/ghostscript/ghostscript_9.25.bb
> > > @@ -121,5 +121,4 @@ do_install_class-native () {
> > >
> > >  BBCLASSEXTEND = "native"
> > >
> > > -# ghostscript does not supports "arc"
> > > -COMPATIBLE_HOST = "^(?!arc).*"
> > > +COMPATIBLE_HOST = "(aarch64|arm|i.86|microblaze|mips|nios2|powerpc|x86_64).*"
> >
> > this ignores riscv now. since you wsnt to
> > ignore for just one arch you can use
> >
> > COMPATIBLE_HOST_arc = "(none)"
> >
> > or somesuch mechanism.
>
> How is that different to the original assignment?
>
> The real point here is that all of these variations have flaws.
> Listing the architectures which don't work means the list isn't
> complete, but listing the working architectures means that layers
> which provide a bbappend instead of submitting to oe-core [1] will
> then refuse to build ghostscript unless they also do something clever
> with COMPATIBLE_HOST.

Ross beat me to it. But I was making this change as inverting due to
the desire to remove the warning and disable the package for at least
three architectures (or1k, riscv32 and lm32).

Regards,
Nathan

>
> Ross
>
> [1] meta-riscv, I'm looking at you
> https://github.com/riscv/meta-riscv/tree/master/recipes-extended/ghostscript



More information about the Openembedded-core mailing list