All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Reinoud Koornstra <sockstat@hotmail.com>
Cc: "buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] Error msg while using toolchain compiler
Date: Wed, 1 Jun 2022 14:26:11 +0200	[thread overview]
Message-ID: <20220601142611.4de82268@windsurf> (raw)
In-Reply-To: <BY5PR02MB6914D9F3E09E2720D4DEDC41C9DF9@BY5PR02MB6914.namprd02.prod.outlook.com>

Hello Reinoud,

On Wed, 1 Jun 2022 02:09:21 +0000
Reinoud Koornstra <sockstat@hotmail.com> wrote:

> Hello Everyone,
> I did configure a toolchain to be built (make sdk) and copied and extracted the tar ball to another machine.
> On there I did run relocate-sdk.sh
> 
> As this toolchain is another one compared to the default gcc installed on that machine I specific it by CC= and then make bla bla
> The error is get is:
> x86_64-buildroot-linux-gnu-gcc: /lib64/libc.so.6: version `GLIBC_2.14' not found (required by x86_64-buildroot-linux-gnu-gcc)

Could you provide more details on how you're using the toolchain?
Indeed, if incorrect flags are passed to the toolchain, it may cause it
to look for libraries in /lib.

But if you don't provide more details, we unfortunately can't really
comment :-/

Thomas
-- 
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot

       reply	other threads:[~2022-06-01 12:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BY5PR02MB6914D9F3E09E2720D4DEDC41C9DF9@BY5PR02MB6914.namprd02.prod.outlook.com>
2022-06-01 12:26 ` Thomas Petazzoni via buildroot [this message]
2022-06-01 19:17   ` [Buildroot] Error msg while using toolchain compiler Richard Ash via buildroot

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=20220601142611.4de82268@windsurf \
    --to=buildroot@buildroot.org \
    --cc=sockstat@hotmail.com \
    --cc=thomas.petazzoni@bootlin.com \
    /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.