From: "Khem Raj" <raj.khem@gmail.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: Denys Dmytriyenko <denis@denix.org>,
Patches and discussions about the oe-core layer
<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 14:46:24 -0700 [thread overview]
Message-ID: <CAMKF1spMw=6ZfkBWy3=+rSiHknxLvVC6uPH3Q8z_UiGdOECVdw@mail.gmail.com> (raw)
In-Reply-To: <765f3daeb6ce5f28c2d1e258dd303f5707363678.camel@linuxfoundation.org>
On Wed, May 27, 2020 at 2:25 PM Richard Purdie
<richard.purdie@linuxfoundation.org> 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 :(
building products doesn't mean you are on the latest kernels sadly,
that's just the reality of world
and building userspace against way newer kernel-headers with older
kernel underneath has unintended
consequences. So its always better to use matching UAPIs to the kernel
version to avoid these mismatches
>
> Cheers,
>
> Richard
>
next prev parent reply other threads:[~2020-05-27 21:46 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 [this message]
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
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='CAMKF1spMw=6ZfkBWy3=+rSiHknxLvVC6uPH3Q8z_UiGdOECVdw@mail.gmail.com' \
--to=raj.khem@gmail.com \
--cc=denis@denix.org \
--cc=openembedded-core@lists.openembedded.org \
--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 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.