From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] gcc 4.2.4 toolchain
Date: Wed, 23 May 2012 15:03:41 +0200 [thread overview]
Message-ID: <871umbqcb6.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <CACDP-tcryHMzAjQ2iw+pRcGavZamDSHStABz5NFxfVrK3-iYzw@mail.gmail.com> (Andrew Chambers's message of "Wed, 23 May 2012 10:50:11 +1200")
>>>>> "Andrew" == Andrew Chambers <andrewchamberss@gmail.com> writes:
Andrew> Hello,
Andrew> Recently ive tried to build a custom mips linux kernel version
Andrew> 2.6.28 under the buildroot-2012.02. However all gcc versions
Andrew> listed do not support some deprecated gcc inline assembly
Andrew> syntax being used extensively.
Andrew> Is it possible to use gcc 4.2.4 with buildroot-2012.02 . I
Andrew> manually added it to the buildroot menu but when attempting a
Andrew> mips build the toolchain i recieve the following errors while
Andrew> building the cross compiler ...?
4.2 support got removed back in Dec 2011, so perhaps give
buildroot-2011.11 a try?
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-05-23 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-22 22:50 [Buildroot] gcc 4.2.4 toolchain Andrew Chambers
2012-05-23 13:03 ` Peter Korsgaard [this message]
2012-05-23 13:09 ` Will Newton
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=871umbqcb6.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.