From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] support/testing: build a glibc toolchain for docker / docker-compose tests
Date: Tue, 12 Feb 2019 15:27:39 +0100 [thread overview]
Message-ID: <20190212152739.4e96f968@windsurf> (raw)
In-Reply-To: <874l99w0wo.fsf@dell.be.48ers.dk>
On Tue, 12 Feb 2019 15:12:55 +0100
Peter Korsgaard <peter@korsgaard.com> wrote:
> >> runc (which is a reverse dependency of docker-engine) is about to gain a
> >> !uclibc dependency, so move to a glibc toolchain instead.
> >>
> >> There are currently no prebuilt x86_64 / core2 / glibc toolchains available,
> >> so instead use the internal toolchain backend to build one.
>
> > One option would be to use:
>
> > https://toolchains.bootlin.com/downloads/releases/toolchains/x86-64-core-i7/tarballs/x86-64-core-i7--glibc--stable-2018.11-1.tar.bz2
>
> Yes, I can change it to that. Do we want to use bootlin toolchains for
> our tests?
Not necessarily, I was just stating another possibility. I'm fine
either way.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2019-02-12 14:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-12 13:15 [Buildroot] [PATCH 1/2] support/testing: build a glibc toolchain for docker / docker-compose tests Peter Korsgaard
2019-02-12 13:15 ` [Buildroot] [PATCH 2/2] package/runc: add upstream security fix for CVE-2019-5736 Peter Korsgaard
2019-02-12 19:04 ` Peter Korsgaard
2019-02-12 13:31 ` [Buildroot] [PATCH 1/2] support/testing: build a glibc toolchain for docker / docker-compose tests Thomas Petazzoni
2019-02-12 14:12 ` Peter Korsgaard
2019-02-12 14:27 ` Thomas Petazzoni [this message]
2019-02-12 19:04 ` Peter Korsgaard
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=20190212152739.4e96f968@windsurf \
--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 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.