From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 00/12] RFC: ARC port
Date: Tue, 30 Apr 2013 18:06:27 +0200 [thread overview]
Message-ID: <517FEC03.1010709@mind.be> (raw)
In-Reply-To: <20130429224541.6f46b3b4@skate>
On 29/04/13 22:45, Thomas Petazzoni wrote:
> * I am not entirely happy with 'toolchain/gcc: Introduce
> BR2_ARCH_HAS_NO_GCC_x_y' using a reverted logic. I haven't thought
> too much about it, but wouldn't it be possible to instead do
> something like BR2_ARCH_NEEDS_GCC_4_6_PLUS, and then do something
> like depends !BR2_ARCH_NEEDS_GCC_4_6_PLUS on all gcc versions <
> 4.6 ? Hum, the problem is that it works with architecture that are
> supported starting from a given upstream gcc version, but not
> architecture that are supported only in 4.2-avr, or in 4.4-arc, etc.
>
> Maybe others will have a suggestion on this point?
Not entirely clean either, but what about the following:
[toolchain/gcc/Config.in]
config BR2_ARCH_HAS_ALL_GCC
bool
config BR2_ARCH_HAS_GCC_4_4
bool
default y if BR2_ARCH_HAS_ALL_GCC
[arch/Config.in]
config BR2_mips
select BR2_ARCH_HAS_ALL_GCC
...
[arch/Config.in.arm]
config BR2_arm1176jzf_s
select BR2_ARCH_HAS_ALL_GCC
...
config BR2_cortex_a8
select BR2_ARCH_HAS_GCC_4_4
...
Regards,
Arnout
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2013-04-30 16:06 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-24 10:13 [Buildroot] [PATCH v2 00/12] RFC: ARC port Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 01/12] arc: Add ARC and ARC BE architecture Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 02/12] arc: Add option for ARC-specific download site Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 03/12] arc: Add support for ARC-specific binutils Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 04/12] arc: Add arc, arcbe to gnuconfig Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 05/12] arc: disable Crosstool-NG for ARC Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 06/12] arc: add gcc " Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 07/12] arc: Add support for ARC-specific uClibc Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 08/12] arc: Make sure that libgcc doesn't get included when it doesn't exist yet Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 09/12] kernel-headers: Use ../testing URL for kernel release candidates Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 10/12] kernel-headers: Add 3.9-rc8 headers to make ARC work Mischa Jonker
2013-04-24 19:41 ` Peter Korsgaard
2013-04-24 10:13 ` [Buildroot] [PATCH v2 11/12] toolchain/gcc: Only enable --with-float when it makes sense Mischa Jonker
2013-04-24 10:13 ` [Buildroot] [PATCH v2 12/12] toolchain/gcc: Introduce BR2_ARCH_HAS_NO_GCC_x_y Mischa Jonker
2013-04-25 3:02 ` [Buildroot] [PATCH v2 00/12] RFC: ARC port Thomas Petazzoni
2013-04-25 11:01 ` Mischa Jonker
2013-04-29 20:45 ` Thomas Petazzoni
2013-04-30 16:06 ` Arnout Vandecappelle [this message]
2013-04-30 22:09 ` Thomas Petazzoni
2013-05-02 14:03 ` Mischa Jonker
2013-05-02 15:12 ` Thomas Petazzoni
2013-05-02 15:18 ` Mischa Jonker
2013-05-02 16:30 ` Thomas Petazzoni
2013-05-02 16:32 ` Arnout Vandecappelle
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=517FEC03.1010709@mind.be \
--to=arnout@mind.be \
--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