Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mischa Jonker <Mischa.Jonker@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 2/7] arc: Add option for ARC-specific download site
Date: Mon, 22 Apr 2013 13:37:26 +0200	[thread overview]
Message-ID: <1366630651-6857-3-git-send-email-mjonker@synopsys.com> (raw)
In-Reply-To: <1366630651-6857-1-git-send-email-mjonker@synopsys.com>

As ARC support is not yet in all upstream packages, a different location is
required to download the packages from. This adds an option to specify a
site for ARC-specific versions of packages such as binutils, gcc.

When ARC support has been upstreamed for all packages, this option can be
removed again.

Signed-off-by: Mischa Jonker <mjonker@synopsys.com>
---
 Config.in |    9 +++++++++
 1 files changed, 9 insertions(+), 0 deletions(-)

diff --git a/Config.in b/Config.in
index bbb9885..c365b38 100644
--- a/Config.in
+++ b/Config.in
@@ -141,6 +141,15 @@ config BR2_PRIMARY_SITE
 	  NOTE: This works for all packages using the central package
 	  infrastructure (generic, autotools, cmake, ...)
 
+config BR2_ARC_SITE
+	string "Download site for ARC specific packages"
+	default "http://www.synopsys.com/apps/arc-developer/"
+	depends on BR2_arc || BR2_arceb
+	help
+	  This download site is used for packages that require specific
+	  support for ARC, while this support is not yet pushed to the
+	  respective open source project.
+
 config BR2_PRIMARY_SITE_ONLY
 	bool "Only allow downloads from primary download site"
 	depends on BR2_PRIMARY_SITE != ""
-- 
1.7.0.4

  parent reply	other threads:[~2013-04-22 11:37 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-22 11:37 [Buildroot] [PATCH 0/7] RFC: ARC port Mischa Jonker
2013-04-22 11:37 ` [Buildroot] [PATCH 1/7] arc: Add ARC and ARC BE architecture Mischa Jonker
2013-04-22 15:47   ` Thomas Petazzoni
2013-04-22 18:40   ` Arnout Vandecappelle
2013-04-22 11:37 ` Mischa Jonker [this message]
2013-04-22 15:48   ` [Buildroot] [PATCH 2/7] arc: Add option for ARC-specific download site Thomas Petazzoni
2013-04-22 18:25     ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 3/7] arc: Add support for ARC-specific binutils Mischa Jonker
2013-04-22 15:49   ` Thomas Petazzoni
2013-04-22 18:35   ` Arnout Vandecappelle
2013-04-22 18:36   ` Arnout Vandecappelle
2013-04-22 11:37 ` [Buildroot] [PATCH 4/7] arc: Add ARC specific kernel headers Mischa Jonker
2013-04-22 15:52   ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 5/7] arc: Add support for ARC-specific GCC Mischa Jonker
2013-04-22 15:56   ` Thomas Petazzoni
2013-04-24 12:44     ` Mischa Jonker
2013-04-24 14:27       ` Thomas Petazzoni
2013-04-24 15:19         ` Mischa Jonker
2013-04-24 21:19           ` Yann E. MORIN
2013-04-22 11:37 ` [Buildroot] [PATCH 6/7] arc: Add support for ARC-specific uClibc Mischa Jonker
2013-04-22 15:56   ` Thomas Petazzoni
2013-04-22 11:37 ` [Buildroot] [PATCH 7/7] arc: Make sure that libgcc doesn't get included when it doesn't exist yet Mischa Jonker
2013-04-22 15:57   ` Thomas Petazzoni
2013-04-22 15:46 ` [Buildroot] [PATCH 0/7] RFC: ARC port Thomas Petazzoni
2013-04-22 16:01 ` [Buildroot] Plan of libffi support? Thomas Petazzoni
2013-04-24  6:38   ` Mischa Jonker
2013-04-24 14:38     ` Thomas Petazzoni

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=1366630651-6857-3-git-send-email-mjonker@synopsys.com \
    --to=mischa.jonker@synopsys.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