All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
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 16:18:25 -0700	[thread overview]
Message-ID: <CAMKF1sp0rF18CtGd3NZigqtqAnrpot+kgNzd2zWQ1LQezzBVUw@mail.gmail.com> (raw)
In-Reply-To: <CAP9ODKom3jT=M_X6wrz5WKRat3yRxtukm5Hrg3FnEtJUiis_vA@mail.gmail.com>

On Wed, Sep 5, 2018 at 3:38 PM Otavio Salvador
<otavio.salvador@ossystems.com.br> wrote:
>
> On Wed, Sep 5, 2018 at 12:18 PM Khem Raj <raj.khem@gmail.com> wrote:
> >
> > On Wed, Sep 5, 2018 at 6:42 AM Otavio Salvador
> > <otavio.salvador@ossystems.com.br> wrote:
> > >
> > >
> > >
> > > 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.
> > >
> >
> > here is glibc failure log
> > http://errors.yoctoproject.org/Errors/Details/190886/
>
> I did build against master and master-next and couldn't reproduce it.
> I saw you are using 'bec' distribution and I used 'oel' so it might be
> changing the end result.
>

did you try poky ? we now build with security flags turned on. Soon
to be propagated to nodistro in oe-core as well.

BEC distro policies are same as poky with few additions
see

distro
https://github.com/cbrake/meta-bec/blob/master/conf/distro/bec.conf

local.conf
https://github.com/cbrake/oe-build/blob/master/conf/local.conf

> Any idea what might be causing the problem?
>
> --
> 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


  reply	other threads:[~2018-09-05 23:18 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
2018-09-05 15:17             ` Khem Raj
2018-09-05 22:38               ` Otavio Salvador
2018-09-05 23:18                 ` Khem Raj [this message]
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=CAMKF1sp0rF18CtGd3NZigqtqAnrpot+kgNzd2zWQ1LQezzBVUw@mail.gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=otavio@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.