From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] Buildroot 2013.05 + uClibc 0.9.30.2
Date: Sat, 08 Jun 2013 21:27:38 +0200 [thread overview]
Message-ID: <51B385AA.6040606@mind.be> (raw)
In-Reply-To: <CACQMp4D5y1PQ8cBZa1esk=zuv_zgmU8eYwTVYE8=b5Ln39k-dw@mail.gmail.com>
On 05/06/13 11:12, David Kochner wrote:
> I am looking for a way to build the latest buildroot environment for
> powerpc e500v2. It actually works pretty well for me. But I would like to
> use a (much) older uClibc (0.9.30.2) as I need to compile binaries to run
> on an old system that I can't upgrade.
> I tried forcing the uClibc from 2010.02 to the latest 2013.05 release, it
> works (sort of) but I need to fix a lot of compilation issues along the
> build (not finished yet...) and I still didn't manage to successfully
> compile it.
There have been many infrastructural changes since then so it's not
really a surprise that this may be hard...
> Sicne tools like crosstool-ng are able to use older uClibc I assume there
> should be a way to do it.
> I was wondering if there is an "official" or "recommended" way to do this.
Yes: build your toolchain with crosstool-NG, and import it as an
external toolchain in buildroot.
> When I try to statically build binaries using a newer uClibc and put it
> on my target machine they crash.
That is weird... Does the binary really not use any shared library
(check with readelf)? How/why does it crash? Can you get a backtrace in
a debugger?
Regards,
Arnout
>
> Right now I am facing 3 options:
> 1. Use old buildroot (2010.02) that support uClibc 0.9.30.2 but cannot
> build e500v2 binaries (can I just build generic ppc and get it over with?)
> 2. Use the newer buildroot (2013.05) and test my applications thoroughly
> to make sure the the old uClibc on my target doesn't cause me any issues
> 3. Force the older uClibc on the newer buildroot...
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
prev parent reply other threads:[~2013-06-08 19:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-05 9:12 [Buildroot] Buildroot 2013.05 + uClibc 0.9.30.2 David Kochner
2013-06-08 19:27 ` Arnout Vandecappelle [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=51B385AA.6040606@mind.be \
--to=arnout@mind.be \
--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