From: tochansky at tochlab.net <tochansky@tochlab.net>
To: buildroot@busybox.net
Subject: [Buildroot] version `GLIBC_2.27' not found
Date: Thu, 15 Nov 2018 19:07:43 +0000 [thread overview]
Message-ID: <d58e4fe6a02db152b13723aa730b9768@tochlab.net> (raw)
In-Reply-To: <20181115162037.6a4f2208@windsurf>
15 ?????? 2018 ?., 18:20, "Thomas Petazzoni" <thomas.petazzoni@bootlin.com> ???????:
> It depends on the glibc symbols they use. You need to build your
> toolchain on a system that has a glibc <= 2.23.
I found that glibc was updated on gentoo to 2.27 few days ago, that's why I haven't see this problem before. Thanks for clarification, I was afraid that something goes wrong.
> You can also have a look at the pre-built toolchains available at
> https://toolchains.bootlin.com, we build them in chroots with old
> system, specifically to make them as compatible as possible. The
> "stable" toolchains are currently built inside a Debian Squeeze chroot,
> while the "bleeding-edge" toolchains are built inside a Debian Jessie
> chroot, because gdb 8.0 requires a C++11 capable compiler.
Thanks for useful link, Thomas.
--
D
prev parent reply other threads:[~2018-11-15 19:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 14:21 [Buildroot] version `GLIBC_2.27' not found tochansky at tochlab.net
2018-11-15 15:20 ` Thomas Petazzoni
2018-11-15 19:07 ` tochansky at tochlab.net [this message]
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=d58e4fe6a02db152b13723aa730b9768@tochlab.net \
--to=tochansky@tochlab.net \
--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