All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tobias Andresen <tobiasarp@gmx.de>
To: buildroot@busybox.net
Subject: [Buildroot] Add different glibc
Date: Wed, 2 Mar 2016 07:11:05 +0100	[thread overview]
Message-ID: <56D683F9.3060507@gmx.de> (raw)
In-Reply-To: <20160228222254.62d8af48@free-electrons.com>

Hello Thomas,

i just want to replace the glibc on an old embedded system with glibc 
2.23 without rebuilding it completely.
Just wanted to find a simple way to do this for someone who cannot 
crosscompile glibc without
a tool like buildroot.

Regards
Tobias
Am 28.02.2016 um 22:22 schrieb Thomas Petazzoni:
> Hello Tobias,
>
> On Sun, 28 Feb 2016 21:25:41 +0100, Tobias Andresen wrote:
>
>> can someone give me a hint how to add a different glibc as a package
>> which will be copied into the rootfs instead of the
>> glibc which is part of the toolchain?
> Why would you want to do this?
>
> In any case, you can customize whatever is in your root filesystem by
> creating a post-build script.
>
> Best regards,
>
> Thomas

      reply	other threads:[~2016-03-02  6:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-28 20:25 [Buildroot] Add different glibc Tobias Andresen
2016-02-28 21:22 ` Thomas Petazzoni
2016-03-02  6:11   ` Tobias Andresen [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=56D683F9.3060507@gmx.de \
    --to=tobiasarp@gmx.de \
    --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.