From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] setting up buildroot for using OLD gcc / binutils
Date: Tue, 13 Oct 2009 20:17:58 +0200 [thread overview]
Message-ID: <877huz2m5l.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <4AD4C1BB.5000304@wp.pl> (W. P.'s message of "Tue\, 13 Oct 2009 20\:06\:51 +0200")
>>>>> "W" == W P <laurentp@wp.pl> writes:
W> Heeelllp. Where may I find buildroot-0.9.28(29)? I mean later than
W> 0.9.27 and earlier than 2009.09.
I take it you mean 2009.02. There is no such thing, there were no
releases between 0.9.27 in 2005 and 2009.02.
W> Why am I asking: in buildroot 0.9.27 I have found patches for gcc 3.4.3
W> and I need 3.4.4 (google at linux-2.6.12.6-venus to see why).
W> And in 2009.02 earliest version of patches for gcc is 3.4.6. So there is
W> a "gap" between files available on buildroot download site.
3.4.6 patches most likely apply to 3.4.4.
W> For binutils i need version 2.15.94 which i may find in 0.9.27.
W> The rest (if I understand well the build process) is relatively simple:
W> patching config.in with versions i need?
yes.
Have you tried the oldest versions supported by 2009.02 before you do
all this work? Chances are that they'll work.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2009-10-13 18:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-12 19:55 [Buildroot] setting up buildroot for using OLD gcc / binutils W.P.
2009-10-12 20:04 ` Peter Korsgaard
2009-10-12 20:28 ` W.P.
[not found] ` <20091012203645.GX2266@mx.loc>
2009-10-12 22:50 ` W.P.
2009-10-13 11:10 ` Bernhard Reutner-Fischer
2009-10-13 18:06 ` W.P.
2009-10-13 18:17 ` Peter Korsgaard [this message]
2009-10-13 18:32 ` W.P.
2009-10-13 19:41 ` W.P.
[not found] ` <4AD4E640.2030103@arcor.de>
2009-10-13 22:13 ` W.P.
2009-10-14 20:40 ` Sebastian
2009-10-16 17:37 ` W.P.
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=877huz2m5l.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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