Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Adam McLaurin <buildroot@irotas.net>
To: buildroot@busybox.net
Subject: [Buildroot] How to build a gcc-3.3 toolchain
Date: Mon, 03 Nov 2008 09:33:52 -0500	[thread overview]
Message-ID: <1225722832.28602.1282706045@webmail.messagingengine.com> (raw)
In-Reply-To: <87ej1uz0yc.fsf@macbook.be.48ers.dk>

On Sun, 02 Nov 2008 14:55:55 +0100, "Peter Korsgaard"
<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.

Thanks for the response.

Should I start by copying everything in 'toolchain/gcc/3.4.6' to
'toolchain/gcc/3.3.6', or create the 3.3.6 directory clean and add
patches as necessary? I'm not sure how well those patches will backport
to 3.3.6.

Thanks,
Adam

  reply	other threads:[~2008-11-03 14:33 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 [this message]
2008-11-03 14:37     ` Peter Korsgaard

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=1225722832.28602.1282706045@webmail.messagingengine.com \
    --to=buildroot@irotas.net \
    --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