[meta-freescale] [PATCH v2 2/2] wayland-protocols: Fix PACKAGE_ARCH for i.MX-specific version

Andreas Müller schnitzeltony at gmail.com
Tue Sep 11 08:12:10 PDT 2018


On Tue, Sep 11, 2018 at 4:40 PM, Otavio Salvador
<otavio.salvador at ossystems.com.br> wrote:
> On Tue, Sep 11, 2018 at 8:15 AM Andreas Müller <schnitzeltony at gmail.com> wrote:
>> On Tue, Sep 11, 2018 at 1:03 PM, Gary Bisson
>> <gary.bisson at boundarydevices.com> wrote:
> ...
>> > However I wonder why we need such recipe, wouldn't a bbappend to the
>> > wayland protocol recipe be sufficient?
>> If yes: same - please make sure other boards are not affected.
>
> NXP needs to suffer from their bad decisions in not upstreaming stuff
> so using their own for puts on their side the need to upgrade.
>
> Andreas, I did check here and I belive your tmp directory is messed up
> due the previous package being built as allarch.
>
> From a clean sstate, I built for a mainline machine and for sabresd. I got:
>
> % ye pv wayland-protocols
> [0] ~/.../deploy/ipk/all/wayland-protocols_1.15-r0.0_all.ipk [0]
> [1] ~/.../deploy/ipk/armv7ahf-neon-mx6qdl/wayland-protocols_1.13.imx-r0.0_armv7ahf-neon-mx6qdl.ipk
> [1]
> Option (ENTER to cancel):
>
>
Hmm - as far as I can remember I did ccleansstate for
wayland-protocols before applying the last patch series.

Is sstate involved in the decision which version is selected at all?

The fact that it failed for me does not make me feel comfortable...

Cannot test with fresh rootfs and switch machines back and forth
currently - that is a time consuming business and nobody gives me that
time...

Andreas


More information about the meta-freescale mailing list