Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Daniel Díaz" <daniel.diaz@linaro.org>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] ltp: Bump to 20190115
Date: Mon, 25 Feb 2019 14:50:13 +0000	[thread overview]
Message-ID: <2fc2b224301582b31e6494a4b2d3df7e4f83d585.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAEUSe7_En46Ji=GjU3EmRBvocfiZz5YQO9XcOeK9+9Hf+9SCug@mail.gmail.com>

On Mon, 2019-02-25 at 08:00 -0600, Daniel Díaz wrote:
> Hello!
> On Sat, 23 Feb 2019 at 10:07, Richard Purdie
> <richard.purdie@linuxfoundation.org> wrote:
> > I think there was already a previous version of this upgrade which
> > also
> > didn't work:
> > 
> > http://errors.yoctoproject.org/Errors/Latest/?filter=480efd388db578106a8a2129c0382b7e56a1ee36&type=commit&limit=150
> > From the -Wformat-security -Werror=format-security security flags.
> 
> I thought the problems were with MUSL and Glibc 2.29 (for which I
> built). Let me look at these problems, then.

Yes, thanks for looking at those.

For now I tweaked the recipe to disable the string security flags for
ltp as I wanted to get the upgrade in. As soon as we get a patchset
which builds, we can remove that workaround. I'm hoping we can get
something upstream for this too...

Cheers,

Richard



      reply	other threads:[~2019-02-25 14:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-21 18:21 [PATCH] ltp: Bump to 20190115 Daniel Díaz
2019-02-23 16:07 ` Richard Purdie
2019-02-25 14:00   ` Daniel Díaz
2019-02-25 14:50     ` Richard Purdie [this message]

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=2fc2b224301582b31e6494a4b2d3df7e4f83d585.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=daniel.diaz@linaro.org \
    --cc=openembedded-core@lists.openembedded.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox