Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Martin Jansa <martin.jansa@gmail.com>
Cc: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [meta-oe][warrior][PATCH 03/11] oprofile: make MACHINE_ARCH
Date: Tue, 11 Jun 2019 23:31:28 +0300	[thread overview]
Message-ID: <20190611203128.GA32661@localhost> (raw)
In-Reply-To: <CA+chaQe8r6WkwAmMTXk6bd9SPGxymV_AhUOzMvNFai37FYiDQQ@mail.gmail.com>

On Tue, Jun 11, 2019 at 10:04:03PM +0200, Martin Jansa wrote:
> fair point, I'll try to remove the dependency and see what breaks, it was
> added couple years ago in:
> https://git.openembedded.org/openembedded-core/commit/?id=16bc366877a2e02d96adb91b90e30710777e6f09
> are you sure that the explanation from back then is no longer valid?
>...

As far as I am aware this is the /usr/include/linux/perf_event.h
userspace kernel header.

Loking at configure.ac it seems more likely that any problems would come 
from there than a fundamental dependency on a specific kernel.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed



  reply	other threads:[~2019-06-11 20:31 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-06-11 16:54 [meta-oe][warrior][PATCH 01/11] gtkwave: add distro_features_check Martin Jansa
2019-06-11 16:54 ` [meta-oe][warrior][PATCH 02/11] ndctl: make MACHINE_ARCH and ignore from libblockdev Martin Jansa
2019-06-11 16:54 ` [meta-oe][warrior][PATCH 03/11] oprofile: make MACHINE_ARCH Martin Jansa
2019-06-11 19:33   ` Adrian Bunk
2019-06-11 20:04     ` Martin Jansa
2019-06-11 20:31       ` Adrian Bunk [this message]
2019-06-11 16:54 ` [meta-oe][warrior][PATCH 04/11] umip: " Martin Jansa
2019-06-11 16:54 ` [meta-oe][warrior][PATCH 05/11] mscgen: fix SRC_URI for multilib Martin Jansa
2019-06-11 16:54 ` [meta-oe][warrior][PATCH 06/11] triggerhappy: fix issues Martin Jansa
2019-06-11 16:55 ` [meta-oe][warrior][PATCH 07/11] python-cassandra-driver.inc: fix DEPENDS Martin Jansa
2019-06-11 16:55 ` [meta-oe][warrior][PATCH 08/11] opencv: use the same package name in PACKAGES and RDEPENDS Martin Jansa
2019-06-11 16:55 ` [meta-oe][warrior][PATCH 09/11] igmpproxy: remove 0001-src-igmpproxy.h-Include-sys-types.h-for-u_short-u_in.patch and _GNU_SOURCE Martin Jansa
2019-06-11 16:55 ` [meta-oe][warrior][PATCH 10/11] libvncserver: set PV in the recipe Martin Jansa
2019-06-11 16:55 ` [meta-oe][warrior][PATCH 11/11] ccid: fix SRC_URI Martin Jansa
2019-06-11 17:28 ` [meta-oe][warrior][PATCH 01/11] gtkwave: add distro_features_check akuster808
2019-06-11 19:29   ` Martin Jansa

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=20190611203128.GA32661@localhost \
    --to=bunk@stusta.de \
    --cc=martin.jansa@gmail.com \
    --cc=openembedded-devel@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