From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] external-toolchain: Detect linux/version.h via cross compiler
Date: Tue, 3 Nov 2020 21:43:44 +0100 [thread overview]
Message-ID: <20201103214344.65ac36cf@windsurf.home> (raw)
In-Reply-To: <CAMKF1sodESjxJAwwJ9i5tFuU1j5dzL0cNx42FB97SSQYwEzpYA@mail.gmail.com>
On Tue, 3 Nov 2020 12:25:25 -0800
Khem Raj <raj.khem@gmail.com> wrote:
> > - Buildroot does not officially support distributions' cross
> > toolchains, as they may contain extra libraries that are not
> > accoutned for by Buildroot,
>
> yes that's fine, this patch does not claim to support all of them
> either, it just
> makes the situation a bit better without regressing the supported usecases
> I think it helps lowering the build times on such distros for
> developers and improve
> first time experience
This has not clarified things for me. Most distributions allow extra
libraries to be installed in their cross-toolchains, i.e on Debian, you
can install libxml2, zlib, and zillions of other libraries
cross-compiled into your cross-compilation toolchain.
Then things are confusing for Buildroot: when it copies the sysroot, it
already contains more than just the C library... potentially libraries
that will conflict with libraries that Buildroot will build.
I don't see how this can work reliably.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-11-03 20:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-23 9:36 [Buildroot] [PATCH] external-toolchain: Detect linux/version.h via cross compiler Khem Raj
2020-11-03 20:00 ` Thomas Petazzoni
2020-11-03 20:19 ` Khem Raj
2020-11-03 20:16 ` Yann E. MORIN
2020-11-03 20:25 ` Khem Raj
2020-11-03 20:43 ` Thomas Petazzoni [this message]
2020-11-04 3:24 ` Khem Raj
2022-01-08 23:03 ` Thomas Petazzoni
2022-01-13 17:02 ` Khem Raj
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=20201103214344.65ac36cf@windsurf.home \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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;
as well as URLs for NNTP newsgroup(s).