Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 00/12] RFC: ARC port
Date: Thu, 2 May 2013 17:12:45 +0200	[thread overview]
Message-ID: <20130502171245.5f3f7f02@skate> (raw)
In-Reply-To: <E6BF041E97966E4DB955F0DF883AD2D6339FE6A5@de02wembxa.internal.synopsys.com>

Dear Mischa Jonker,

On Thu, 2 May 2013 14:03:53 +0000, Mischa Jonker wrote:

[...]

> But this doesn't work for several architectures, such as
> BR2_sparc_sparcsfleon, that do have GCC 4.4, but no 4.5 for instance.
> 
> The reverse logic helps in the sense that the BR2_HAS_NO_GCC_x_y
> lines will go away over time when old GCC versions get deprecated.
> 
> I will send both variants later today.

As I suggested in an earlier e-mail, I think you should just not care
about this problem for now, and add the multiple 'depends on !BR2_arc'
as you were doing in your first version of the patch set. Your patch
set already has a good number of patches, so let's merge it, and
improve on top of that.

Thanks!

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2013-05-02 15:12 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
2013-04-30 22:09         ` Thomas Petazzoni
2013-05-02 14:03           ` Mischa Jonker
2013-05-02 15:12             ` Thomas Petazzoni [this message]
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=20130502171245.5f3f7f02@skate \
    --to=thomas.petazzoni@free-electrons.com \
    --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