All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Müller" <schnitzeltony@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: meta-freescale Mailing List <meta-freescale@yoctoproject.org>
Subject: Re: [PATCH v2 2/2] wayland-protocols: Fix PACKAGE_ARCH for i.MX-specific version
Date: Tue, 11 Sep 2018 17:12:10 +0200	[thread overview]
Message-ID: <CALbNGRQrPesvvSv8VDtibyK8Smq5uJQvWfJWm573uOUFRaA0Yg@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKq8HDFNN9bPKUc9e_VqqS3WatKQA4X+fpfQ+b4LiK3geQ@mail.gmail.com>

On Tue, Sep 11, 2018 at 4:40 PM, Otavio Salvador
<otavio.salvador@ossystems.com.br> wrote:
> On Tue, Sep 11, 2018 at 8:15 AM Andreas Müller <schnitzeltony@gmail.com> wrote:
>> On Tue, Sep 11, 2018 at 1:03 PM, Gary Bisson
>> <gary.bisson@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


  reply	other threads:[~2018-09-11 15:12 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-10 21:21 [PATCH v2 1/2] wayland-protocols: Fix fetcher error Tom Hochstein
2018-09-10 21:21 ` [PATCH v2 2/2] wayland-protocols: Fix PACKAGE_ARCH for i.MX-specific version Tom Hochstein
2018-09-11  7:44   ` Andreas Müller
2018-09-11 11:03     ` Gary Bisson
2018-09-11 11:14       ` Andreas Müller
2018-09-11 14:40         ` Otavio Salvador
2018-09-11 15:12           ` Andreas Müller [this message]
2018-09-11 16:55             ` Otavio Salvador
2018-09-12  9:17               ` Andreas Müller
2018-09-12 12:47                 ` Otavio Salvador
2018-09-12 13:54                   ` Andreas Müller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CALbNGRQrPesvvSv8VDtibyK8Smq5uJQvWfJWm573uOUFRaA0Yg@mail.gmail.com \
    --to=schnitzeltony@gmail.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.