From: "Adrian Bunk" <bunk@stusta.de>
To: Khem Raj <raj.khem@gmail.com>
Cc: Richard Purdie <richard.purdie@linuxfoundation.org>,
Denys Dmytriyenko <denis@denix.org>,
openembedded-core@lists.openembedded.org
Subject: Re: [OE-core] [PATCH] linux-libc-headers: Check for asm/bpf_perf_event.h before multilibbing
Date: Thu, 28 May 2020 23:10:20 +0300 [thread overview]
Message-ID: <20200528201020.GB996@localhost> (raw)
In-Reply-To: <7f778511-3aff-016c-4c54-10990ba2b033@gmail.com>
On Thu, May 28, 2020 at 11:33:45AM -0700, Khem Raj wrote:
>
> this is not a freestanding toolchain, but hosted one, so they need to
> provide OS (linux) headers. think of case where apps are build just by
> using this toolchain outside OE, app devs are not expected to provide these
> headers.
Various gcc libraries like libgcc or libstdc++ might be used on the target.
What C library was used for building these gcc libraries?
What kernel headers are used by this C library in the toolchain?
cu
Adrian
next prev parent reply other threads:[~2020-05-28 20:10 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
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 [this message]
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=20200528201020.GB996@localhost \
--to=bunk@stusta.de \
--cc=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 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.