From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot for older uClibc
Date: Thu, 25 Feb 2010 15:42:02 +0100 [thread overview]
Message-ID: <20100225154202.53c82f09@surf> (raw)
In-Reply-To: <fa63ee051002250621t4e0c2cbdk94c9dfa165a297d8@mail.gmail.com>
On Thu, 25 Feb 2010 14:21:02 +0000
daniel wilson <daniel.a.wilson@gmail.com> wrote:
> I'm working with a legacy embedded platform which has some closed
> binaries that are linked against uClibc 0.9.28. Much as I would like
> to bring this platform up-to-date, I'm reliant on these utilities for
> the correct operation of various bits of hardware. To cut a long
> story short, I think I'm going to have to build myself a toolchain
> which links against uClibc 0.9.28 to produce software for this
> platform.
>
> I've downloaded various older versions of buildroot, but none of them
> seem to have this version of uClibc as an option.
In the current version of Buildroot, we still offer 0.9.28.3 as a
choice, but you have to enable BR2_DEPRECATED to see it.
However, be warned that the version of uClibc is not the only thing.
You have to create a uClibc with a configuration that is similar to the
uClibc that was used by the binaries at the time they were generated.
Depending on the configuration, the uClibc API/ABI changes.
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2010-02-25 14:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-25 14:21 [Buildroot] buildroot for older uClibc daniel wilson
2010-02-25 14:42 ` Thomas Petazzoni [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=20100225154202.53c82f09@surf \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox