All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] version `GLIBC_2.27' not found
Date: Thu, 15 Nov 2018 16:20:37 +0100	[thread overview]
Message-ID: <20181115162037.6a4f2208@windsurf> (raw)
In-Reply-To: <a59aa43d9d9f5a8e734185c9efd73c75@tochlab.net>

Hello,

On Thu, 15 Nov 2018 14:21:36 +0000, tochansky at tochlab.net wrote:

> I have a strange behavior of toolchain built by buildroot.
> 
> I made a toolchain on pc with gentoo linux and took it to kubuntu 16.04 LTS and ld reports:
> 
> /opt/moonshine/bin/x86_64-moonshine-linux-gnu-ld: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.27' not found (required by /opt/moonshine/bin/x86_64-moonshine-linux-gnu-ld)
> 
> same time /opt/moonshine/bin/x86_64-moonshine-linux-gnu-gcc works fine.
> 
> As I can see, there is glibc 2.27 on gentoo and 2.23 on kubuntu. Thing I can't understand is why other tools(gcc for example) works normal.

It depends on the glibc symbols they use. You need to build your
toolchain on a system that has a glibc <= 2.23.

You can also have a look@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.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2018-11-15 15:20 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 [this message]
2018-11-15 19:07   ` tochansky at tochlab.net

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=20181115162037.6a4f2208@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.