Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: OE-core <openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 6/7] oprofile: update to 1.2.0
Date: Fri, 11 Aug 2017 14:25:31 +0300	[thread overview]
Message-ID: <7cec3a5a-e514-5730-47ce-1604ab4fc1a3@linux.intel.com> (raw)
In-Reply-To: <CAJTo0La5aPZ711UmGoXpvLxoQ3cJPQ1aPjD8EtBdyVaaoeyv5A@mail.gmail.com>

On 08/09/2017 11:47 PM, Burton, Ross wrote:
> Breaks with musl:
> 
> http://errors.yoctoproject.org/Errors/Details/150200/

Should we just remove oprofile? From git log I understood that it has 
been deprecated in favour of perf, and this musl failure is non-trivial 
to fix (necessary version of basename() is not provided by musl on 
purpose, and so needs to be manually reimplemented).

I'll send the patches :)

Alex


  reply	other threads:[~2017-08-11 11:28 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-07 11:44 [PATCH 1/7] dnf: update to 2.6.3 Alexander Kanavin
2017-08-07 11:44 ` [PATCH 2/7] libdnf: update to 0.9.3 Alexander Kanavin
2017-08-07 11:45 ` [PATCH 3/7] btrfs-tools: update to 4.12 Alexander Kanavin
2017-08-07 12:59   ` Burton, Ross
2017-08-07 12:59     ` Alexander Kanavin
2017-08-07 13:05       ` Burton, Ross
2017-08-08 15:48   ` Khem Raj
2017-08-08 17:19     ` Alexander Kanavin
2017-08-08 17:24       ` Khem Raj
2017-08-07 11:45 ` [PATCH 4/7] ffmpeg: update to 3.3.3 Alexander Kanavin
2017-08-07 11:45 ` [PATCH 5/7] babeltrace: update to 1.5.3 Alexander Kanavin
2017-08-07 11:45 ` [PATCH 6/7] oprofile: update to 1.2.0 Alexander Kanavin
2017-08-09 20:47   ` Burton, Ross
2017-08-11 11:25     ` Alexander Kanavin [this message]
2017-08-07 11:45 ` [PATCH 7/7] gptfdisk: update to 1.0.3 Alexander Kanavin

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=7cec3a5a-e514-5730-47ce-1604ab4fc1a3@linux.intel.com \
    --to=alexander.kanavin@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ross.burton@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox