From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] How to build a gcc-3.3 toolchain
Date: Mon, 03 Nov 2008 15:37:38 +0100 [thread overview]
Message-ID: <87iqr4c1u5.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1225722832.28602.1282706045@webmail.messagingengine.com> (Adam McLaurin's message of "Mon\, 03 Nov 2008 09\:33\:52 -0500")
>>>>> "Adam" == Adam McLaurin <buildroot@irotas.net> writes:
Adam> On Sun, 02 Nov 2008 14:55:55 +0100, "Peter Korsgaard"
Adam> <jacmet@uclibc.org> said:
>> You could probably change the existing 3.4.6 support (remember to
>> enable BR2_DEPRECATED) to compile a 3.3 gcc instead.
Adam> Thanks for the response.
Adam> Should I start by copying everything in 'toolchain/gcc/3.4.6' to
Adam> 'toolchain/gcc/3.3.6', or create the 3.3.6 directory clean and add
Adam> patches as necessary? I'm not sure how well those patches will backport
Adam> to 3.3.6.
I don't quite know either, but my guess is that they will more-or-less
apply.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2008-11-03 14:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-31 14:33 [Buildroot] How to build a gcc-3.3 toolchain Adam McLaurin
2008-11-02 13:55 ` Peter Korsgaard
2008-11-03 14:33 ` Adam McLaurin
2008-11-03 14:37 ` Peter Korsgaard [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=87iqr4c1u5.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