Re: [OE-core] [PATCH] linux-libc-headers: Check for asm/bpf_perf_event.h before multilibbing

["Phil Blundell" <pb@pbcl.net>]

On Thu, May 28, 2020 at 12:30:13PM -0700, Andre McCurdy wrote:
> What I was trying to get at is why you felt that bringing up the fact
> the kernel 4.1 was released at around the time gcc 5 was current is
> important?

Agreed, I think this is a red herring.  One of my current targets is
in fact still using Linux 4.9, which I think was roughly contemporary
with GCC 6, and it still builds just fine with at least GCC 8.
Although I think some of our old-timers still carry the emotional
scars associated with gcc 2.8, in reality the days when a compiler
upgrade ought to be expected to break the kernel in anything other
than a trivial way (i.e. new warning or error that's easy to patch)
are long gone.

And, all that said, there is plenty of precedent for OE users
keeping older versions of GCC around in order to support particular
pieces of software that didn't work with newer compilers for
whatever reason.  It's not generally all that difficult, and
anybody who was sufficiently interested could keep the old gcc
version around in a separate layer even after it's deleted from
oe-core.  In fact oe-core did at one point even have an explicit
KERNEL_CCSUFFIX variable which users could set if they wanted
a specific gcc version to go with their kernel, but this was
deleted in 2013 with the justification "kernel compiler is not 
special".

p.