Openembedded Core Discussions
 help / color / mirror / Atom feed
From: "Denys Dmytriyenko" <denis@denix.org>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] linux-libc-headers: Check for asm/bpf_perf_event.h before multilibbing
Date: Wed, 27 May 2020 19:11:45 -0400	[thread overview]
Message-ID: <20200527231145.GO17660@denix.org> (raw)
In-Reply-To: <765f3daeb6ce5f28c2d1e258dd303f5707363678.camel@linuxfoundation.org>

On Wed, May 27, 2020 at 10:25:31PM +0100, Richard Purdie wrote:
> On Wed, 2020-05-27 at 11:59 -0400, Denys Dmytriyenko wrote:
> > On Wed, May 27, 2020 at 08:50:11AM -0700, Khem Raj wrote:
> > > asm/bpf_perf_event.h does not exist in older kernels e.g. ( 4.1 )
> > > this helps in using common header across multiple versions of
> > > kernel
> > > going back
> > 
> > This check should have been there from the beginning and for every
> > header 
> > file. It's big PITA to sync this list up, especially when dealing
> > with 
> > different glibc or kernel than OE-Core, e.g. external toolchains,
> > etc.
> > 
> > Any objections to making this check more generic for every entry in
> > the list?
> 
> Yes, a strong objection. We don't want to support or encourage every
> kernel version out there. 
> 
> I also don't understand why people need to change the libc-headers
> anyway :(

Richard,

I already explained my use-case with external toolchains - those usually come 
with specific set of libc-headers. And when those don't match the list from 
OE-Core, it causes problems, trying to support some resemblance of multilib. 
I believe that got disabled completely now for external-toolchains anyway...

-- 
Denys

  parent reply	other threads:[~2020-05-27 23:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-27 15:50 [PATCH] linux-libc-headers: Check for asm/bpf_perf_event.h before multilibbing Khem Raj
2020-05-27 15:59 ` [OE-core] " Denys Dmytriyenko
2020-05-27 20:45   ` Khem Raj
2020-05-27 20:56     ` Andre McCurdy
2020-05-27 21:25   ` Richard Purdie
2020-05-27 21:46     ` Khem Raj
2020-05-27 21:50       ` Richard Purdie
2020-05-27 21:52       ` Phil Blundell
2020-05-27 22:42         ` Andre McCurdy
2020-05-27 22:57           ` Khem Raj
2020-05-28  0:02             ` Khem Raj
2020-05-28  9:01               ` Phil Blundell
2020-05-28 18:37                 ` Khem Raj
2020-05-27 23:11     ` Denys Dmytriyenko [this message]
2020-05-28 13:20       ` Richard Purdie
2020-05-28 13:39         ` Adrian Bunk
2020-05-28 17:38           ` Andre McCurdy
2020-05-28 19:04             ` Adrian Bunk
2020-05-28 19:30               ` Andre McCurdy
2020-05-28 21:10                 ` Phil Blundell
2020-05-28 21:33             ` Phil Blundell
2020-05-28 18:31           ` Khem Raj
2020-05-28 18:33         ` Khem Raj
2020-05-28 20:10           ` Adrian Bunk
2020-05-27 21:20 ` Richard Purdie

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=20200527231145.GO17660@denix.org \
    --to=denis@denix.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    --cc=richard.purdie@linuxfoundation.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