From: Samuel Martin <s.martin49@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] legacy: marked BR2_PACKAGE_GCC_TARGET and BR2_HAVE_DEVFILES as removed
Date: Fri, 30 Aug 2013 06:08:59 +0200 [thread overview]
Message-ID: <1377835739-2249-1-git-send-email-s.martin49@gmail.com> (raw)
These 2 symbols were removed when the gcc has been converted to the
Buildroot package infrastructures.
Signed-off-by: Samuel Martin <s.martin49@gmail.com>
Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
---
Config.in.legacy | 17 +++++++++++++++++
1 file changed, 17 insertions(+)
diff --git a/Config.in.legacy b/Config.in.legacy
index 763f16c..30a44c6 100644
--- a/Config.in.legacy
+++ b/Config.in.legacy
@@ -96,6 +96,23 @@ config BR2_VFP_FLOAT
been replaced with a choice of options that allows to select
between various VFP versions/capabilities.
+config BR2_PACKAGE_GCC_TARGET
+ bool "gcc on the target filesystem has been removed"
+ select BR2_LEGACY
+ help
+ The support for gcc in the target filesystem was deprecated
+ since a while, and has been removed completely from Buildroot.
+ See Buildroot's documentation for more explanations.
+
+config BR2_HAVE_DEVFILES
+ bool "development files in target filesystem has been removed"
+ select BR2_LEGACY
+ help
+ The installation of the development files in the target
+ filesystem was deprecated since a while, and has been removed
+ completely from Buildroot.
+ See Buildroot's documentation for more explanations.
+
###############################################################################
comment "Legacy options removed in 2013.05"
--
1.8.4
next reply other threads:[~2013-08-30 4:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-30 4:08 Samuel Martin [this message]
2013-08-30 7:33 ` [Buildroot] [PATCH] legacy: marked BR2_PACKAGE_GCC_TARGET and BR2_HAVE_DEVFILES as removed Thomas Petazzoni
2013-09-02 20:39 ` Peter Korsgaard
2013-09-02 20:46 ` Thomas Petazzoni
2013-09-02 20:38 ` Peter Korsgaard
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=1377835739-2249-1-git-send-email-s.martin49@gmail.com \
--to=s.martin49@gmail.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