All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otavio Salvador <otavio.salvador@ossystems.com.br>
To: Khem Raj <raj.khem@gmail.com>
Cc: Otavio Salvador <otavio@ossystems.com.br>,
	Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] cmake: Update 3.11.4 -> 3.12.1
Date: Wed, 5 Sep 2018 10:42:30 -0300	[thread overview]
Message-ID: <CAP9ODKpfrTs+vQQcG=TyTO6nPZHR8U3xHyg4i_xsn17eOKc41A@mail.gmail.com> (raw)
In-Reply-To: <CAMKF1sr9+bzRBVfV5J=ad4v_m1kQ5hLg=qDqX_dyEUWcFeocAQ@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 539 bytes --]

On Tue, Sep 4, 2018 at 8:43 PM Khem Raj <raj.khem@gmail.com> wrote:

> Here is one failiure that is seen in meta-oe with updates cmake
>
> http://errors.yoctoproject.org/Errors/Details/190510/


I am looking at it...

Seems not related. I built poco using cmake bump and OE master.

Seems related to the musl update on master-next.

-- 
Otavio Salvador                             O.S. Systems
http://www.ossystems.com.br        http://code.ossystems.com.br
Mobile: +55 (53) 9 9981-7854          Mobile: +1 (347) 903-9750

[-- Attachment #2: Type: text/html, Size: 1184 bytes --]

  reply	other threads:[~2018-09-05 13:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-30 23:26 [PATCH] cmake: Update 3.11.4 -> 3.12.1 Otavio Salvador
2018-08-31 16:19 ` Khem Raj
2018-08-31 18:13   ` Otavio Salvador
2018-08-31 19:54     ` Khem Raj
2018-08-31 20:54       ` Otavio Salvador
2018-09-04 23:43         ` Khem Raj
2018-09-05 13:42           ` Otavio Salvador [this message]
2018-09-05 15:17             ` Khem Raj
2018-09-05 22:38               ` Otavio Salvador
2018-09-05 23:18                 ` Khem Raj
2018-09-06  1:00                   ` Otavio Salvador
2018-09-06  3:14                     ` Khem Raj

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='CAP9ODKpfrTs+vQQcG=TyTO6nPZHR8U3xHyg4i_xsn17eOKc41A@mail.gmail.com' \
    --to=otavio.salvador@ossystems.com.br \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio@ossystems.com.br \
    --cc=raj.khem@gmail.com \
    /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.