From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] gcc/gcc-initial: fix build of the AVR32 toolchain
Date: Thu, 09 Oct 2014 15:27:55 +0200 [thread overview]
Message-ID: <87zjd59xus.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <1412803235-23147-1-git-send-email-thomas.petazzoni@free-electrons.com> (Thomas Petazzoni's message of "Wed, 8 Oct 2014 23:20:35 +0200")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
> Since we switched to a two stage gcc build process, the AVR32
> toolchain stopped building. This is because with such an old gcc
> version, we cannot use the all-target-libgcc and install-target-libgcc
> targets.
> Before the two stage gcc, libgcc was only built in gcc-intermediate,
> which carried a similar logic. This commit basically restores in
> gcc-initial the logic that used to be in gcc-intermediate, which
> consists in using the all-target-libcc and install-target-libgcc
> targets only for gcc versions others than the AVR32 one.
> Using the BR2_GCC_SUPPORTS_FINEGRAINEDMTUNE option has a way of
> distinguishing the old AVR32 compiler from the other gcc versions is a
> bit ugly, but it's what was done in gcc-intermediate before. And since
> the AVR32 support is due to go away at some point in the hopefully
> near future, we don't care that much.
> This will fix the build of the two AVR32 defconfig that have been
> constantly failing since switching to the two stage gcc process.
> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Committed, thanks.
--
Bye, Peter Korsgaard
prev parent reply other threads:[~2014-10-09 13:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-08 21:20 [Buildroot] [PATCH] gcc/gcc-initial: fix build of the AVR32 toolchain Thomas Petazzoni
2014-10-09 13:27 ` 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=87zjd59xus.fsf@dell.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