NetCube-Systems-Austria/kumquat-buildroot
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
2a026ca501
kumquat-buildroot/Config.in.legacy

5495 lines
165 KiB
Plaintext
Raw Normal View History

pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
#
# Config.in.legacy - support for backward compatibility
#
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
# When an existing Config.in symbol is removed, it should be added again in
# this file, and take appropriate action to approximate backward compatibility.
# This will make the transition for the user more convenient.
pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
#
# When adding legacy symbols to this file, add them to the front. The oldest
# symbols will be removed again after about two years.
#
# The symbol should be copied as-is from the place where it was previously
# defined, but the help text should be removed or replaced with something that
# explains how to fix it.
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# For bool options, the old symbol should select BR2_LEGACY, so that the user
# is informed at build-time about selected legacy options.
# If there is an equivalent (set of) new symbols, these should be select'ed by
# the old symbol for backwards compatibility.
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# It is not possible to select an option that is part of a choice. In that
# case, the new option should use the old symbol as default. This requires a
# change outside of Config.in.legacy, and this should be clearly marked as such
# in a comment, so that removal of legacy options also include the removal of
# these external references.
#
# [Example: renaming a bool option that is part of a choice from FOO to BAR]
# original choice:
# choice
# prompt "Choose foobar"
# config BR2_FOO_1
# bool "foobar 1"
# config BR2_FOO_2
# bool "foobar 2"
# endchoice
#
# becomes:
# choice
# prompt "Choose foobar"
# default BR2_BAR_1 if BR2_FOO_1 # legacy
# default BR2_BAR_2 if BR2_FOO_2 # legacy
# config BR2_BAR_1
# bool "foobar 1"
# config BR2_BAR_2
# bool "foobar 2"
# endchoice
#
# and in Config.in.legacy:
# config BR2_FOO_1
# bool "foobar 1 has been renamed"
# help
# <suitable help text>
# # Note: BR2_FOO_1 is still referenced from package/foo/Config.in
# config BR2_FOO_2
# bool "foobar 2 has been renamed"
# help
# <suitable help text>
# # Note: BR2_FOO_2 is still referenced from package/foo/Config.in
#
# [End of example]
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# For string options, it is not possible to directly select another symbol. In
# this case, a hidden wrap bool option has to be added, that defaults to y if
# the old string is not set at its default value. The wrap symbol should select
# BR2_LEGACY.
# If the original symbol has been renamed, the new symbol should use the value
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# of the old symbol as default. Like for choice options, a comment should be
# added to flag that the symbol is still used in another file.
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# [Example: renaming a string option from FOO to BAR]
# original symbol:
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# config BR2_FOO_STRING
# string "Some foo string"
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# becomes:
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# config BR2_BAR_STRING
# string "Some bar string"
# default BR2_FOO_STRING if BR2_FOO_STRING != "" # legacy
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# and in Config.in.legacy:
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# config BR2_FOO_STRING
# string "The foo string has been renamed"
# help
# <suitable help text>
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# config BR2_FOO_STRING_WRAP
# bool
# default y if BR2_FOO_STRING != ""
# select BR2_LEGACY
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
Config.in.legacy: document how to handle renaming choice options When a choice option is renamed, it is not possible to select the new option. Instead, the default for the new option should be set in the choice itself. So let's document this. While we're at it, also reformat the whitespace in the example so a tab is used at the appropriate place. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 00:52:03 +01:00
# # Note: BR2_FOO_STRING is still referenced from package/foo/Config.in
Config.in.legacy: update description for developers The existing comments in Config.in.legacy are not entirely in-line with current practice. The comments implies that BR2_LEGACY should not be set when the conversion from old-to-new symbol can be done automatically using the appropriate 'select' statements. However, none of the existing legacy options does it this way. Moreover, I think it's intentional that the user is notified of the change, so that the removal of the legacy options in later buildroot versions no longer poses a problem. Additionally, the comments now describe how to handle string options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:50 +02:00
#
# [End of example]
pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
*config: improve handling of BR2_LEGACY In 8a46d4bf1f the randpackageconfig and allpackageyesconfig were extended with disabling all the legacy options, otherwise the resulting config couldn't be built. However, that didn't work for randconfig and allyesconfig. This commit reverts 8a46d4bf1f and replaces it with a different approach: skipping of the legacy config options is passed explicitly through the environment variable SKIP_LEGACY, which forces BR2_SKIP_LEGACY to y. The new option BR2_SKIP_LEGACY completely disables the legacy handling, which effectively removes all the legacy options from the .config. However, in that case no values are set for the legacy options so a subsequent oldconfig will query them. Therefore, run an additional olddefconfig. [Peter: fix s/BR2_LEGACY/SKIP_LEGACY/ typo] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [yann.morin.1998@free.fr: do not rely on a user-visible option, works perfectly well with only blind options set from the environment] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-04-11 01:49:02 +02:00
config BR2_SKIP_LEGACY
bool
option env="SKIP_LEGACY"
if !BR2_SKIP_LEGACY
pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
config BR2_LEGACY
bool
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
This option is selected automatically when your old .config
uses an option that no longer exists in current buildroot. In
that case, the build will fail. Look for config options which
are selected in the menu below: they no longer exist and
should be replaced by something else.
pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
# This comment fits exactly in a 80-column display
comment "Legacy detected: check the content of the menu below"
depends on BR2_LEGACY
Legacy: make the menu a normal menu. The help text is moved to comments. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 06:34:32 +01:00
menu "Legacy config options"
if BR2_LEGACY
Config.in.legacy: add separator to description for users When legacy symbols are selected, the menuconfig shows the explanation for users, immediately followed by the line "Legacy options removed in 2013.08". In order to visually keep these apart, we introduce a separator. Note that a line with all spaces is not correctly shown by menuconfig (the width will not be kept at 80 characters, so the output is '*** ***'). A dashed line seemed a logical alternative, and with another dashed line on top, the description becomes a block. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:52 +02:00
comment "----------------------------------------------------"
Legacy: make the menu a normal menu. The help text is moved to comments. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 06:34:32 +01:00
comment "Your old configuration uses legacy options that no "
Config.in.legacy: update description for users This patch clarifies the message shown to users in the legacy menu. It explicitly mentions the need to save the configuration before disabling the legacy options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:51 +02:00
comment "longer exist in buildroot, as indicated in the menu "
comment "below. As long as these options stay selected, or in"
comment "case of string options are non-empty, the build "
Legacy: make the menu a normal menu. The help text is moved to comments. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 06:34:32 +01:00
comment "will fail. "
Config.in.legacy: update description for users This patch clarifies the message shown to users in the legacy menu. It explicitly mentions the need to save the configuration before disabling the legacy options. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:51 +02:00
comment "* "
comment "Where possible, an automatic conversion from old to "
comment "new symbols has been performed. Before making any "
comment "change in this legacy menu, make sure to exit the "
comment "configuration editor a first time and save the "
comment "configuration. Otherwise, the automatic conversion "
comment "of symbols will be lost. "
comment "* "
comment "After this initial save, reopen the configuration "
comment "editor, inspect the options selected below, read "
comment "their help texts, and verify/update the new "
comment "configuration in the corresponding configuration "
comment "menus. When everything is ok, you can disable the "
comment "legacy options in the menu below. Once you have "
comment "disabled all legacy options, this text will "
comment "disappear and you will be able to start the build. "
comment "* "
Config.in.legacy: update comment that old entries have been removed Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-12-27 00:39:04 +01:00
comment "Note: legacy options older than 5 years have been "
comment "removed, and configuration files that still have "
comment "those options set, will fail to build, or run in "
comment "unpredictable ways. "
Config.in.legacy: add separator to description for users When legacy symbols are selected, the menuconfig shows the explanation for users, immediately followed by the line "Legacy options removed in 2013.08". In order to visually keep these apart, we introduce a separator. Note that a line with all spaces is not correctly shown by menuconfig (the width will not be kept at 80 characters, so the output is '*** ***'). A dashed line seemed a logical alternative, and with another dashed line on top, the description becomes a block. Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2013-09-02 22:07:52 +02:00
comment "----------------------------------------------------"
Legacy: make the menu a normal menu. The help text is moved to comments. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 06:34:32 +01:00
endif
pkg-infra: introduce errors for legacy API As discussed in the BR developer days, we want to be more strict about API changes in buildroot. I.e., we want to make it less likely that a user's customizations break down after upgrading buildroot. A first step is to make sure that the user is warned about API changes. This patch introduces Makefile.legacy and Config.in.legacy, which will issue clear error messages for such situations. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2012-11-12 11:08:28 +01:00
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
###############################################################################
system cfg: remove mkpasswd MD5 format option As SHA256 is now default, removing weak MD5 option. C libraries now all support the SHA methods. glibc 2.7+ uclibc (bdd8362a88 package/uclibc: defconfig: enable sha-256...) musl 1.1.14+ One issue this would prevent, is a host tool issue with a FIPS enabled system where weak ciphers/methods are disabled. It seems the crypt(3) call is impacted by /proc/sys/crypto/fips_enabled (per crypt(3) man page). It results in mkpasswd returning "(EPERM) crypt failed." Rather then create a Buildroot host dependency check, this patch removes the potential corner case from being selected. Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-12-06 03:06:29 +01:00
Config.in.legacy: recent removals are for the future release A few package or config removals have been introduced after the 2023.11 release, but there entries were still added to the list of options removed in 2023.11. The affected commits are: 64a5831679 package/libmpd: remove package f93380ab1a package/gmpc: remove package 6d8c7aecbb package/flickcurl: remove package f6acde11ab package/onevpl: rename package to libvpl fffb245f66 package/linux-headers: drop 6.5.x option Introduce the 2024.02 section and move the 2023.11 one to where it belongs. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-27 22:22:52 +01:00
comment "Legacy options removed in 2024.02"
package/binutils: drop 2.37.x series Now that 2.40.x has been added, that 2.39.x is the default version, drop support for 2.37.x. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-06-11 15:16:31 +02:00
toolchain: drop codescape mips toolchains Codescape mips toolchains are old (2018) and use glibc 2.20 which is not compatible with 64-bit time_t raising the following build failure with libselinux since commit 1c2dbcdcf0bb589d325c379246acaa39bb07b7be: In file included from selinux_restorecon.c:17:0: /home/buildroot/autobuild/instance-1/output-1/host/mipsel-buildroot-linux-gnu/sysroot/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" # error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" ^~~~~ Fixes: 1c2dbcdcf0bb589d325c379246acaa39bb07b7be - http://autobuild.buildroot.org/results/a4d38af627a42a2c55d60129787c51353d5883bf Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be> (cherry picked from commit 33605ea6d9b370d052dbf6b06d89e7b2a16d4275) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-17 13:51:32 +01:00
config BR2_TOOLCHAIN_EXTERNAL_CODESCAPE_IMG_MIPS
bool "Codescape IMG GNU Linux Toolchain 2018.09 has been removed"
select BR2_LEGACY
help
The Codescape IMG GNU Linux toolchain has been removed, use a
Bootlin toolchain instead.
config BR2_TOOLCHAIN_EXTERNAL_CODESCAPE_MTI_MIPS
bool "Codescape MTI GNU Linux Toolchain 2018.09 has been removed"
select BR2_LEGACY
help
The Codescape MTI GNU Linux toolchain has been removed, use a
Bootlin toolchain instead.
toolchain: drop codesourcery arm/aarch64 toolchains codesourcery arm/aarch64 toolchains are old (2014) and use glibc 2.18/2.20 which are not compatible with 64-bit time_t raising the following build failure with libcgroup since commit 1c2dbcdcf0bb589d325c379246acaa39bb07b7be: In file included from ./libcgroup-internal.h:25:0, from parse.y:21: /home/buildroot/autobuild/run/instance-3/output-1/host/arm-buildroot-linux-gnueabi/sysroot/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" # error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" ^ Fixes: 1c2dbcdcf0bb589d325c379246acaa39bb07b7be - http://autobuild.buildroot.org/results/e28f955f2b360f6e7bb231a5a3800cfbd17a23d7 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Peter: add Config.in.legacy entries] Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 53a8c5150e5eeeb6dbbead0275dbf9141f507511) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-09 17:49:46 +01:00
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_AARCH64
toolchain: drop codescape mips toolchains Codescape mips toolchains are old (2018) and use glibc 2.20 which is not compatible with 64-bit time_t raising the following build failure with libselinux since commit 1c2dbcdcf0bb589d325c379246acaa39bb07b7be: In file included from selinux_restorecon.c:17:0: /home/buildroot/autobuild/instance-1/output-1/host/mipsel-buildroot-linux-gnu/sysroot/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" # error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" ^~~~~ Fixes: 1c2dbcdcf0bb589d325c379246acaa39bb07b7be - http://autobuild.buildroot.org/results/a4d38af627a42a2c55d60129787c51353d5883bf Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be> (cherry picked from commit 33605ea6d9b370d052dbf6b06d89e7b2a16d4275) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-17 13:51:32 +01:00
bool "CodeSourcery AArch64 2014.11 has been removed"
toolchain: drop codesourcery arm/aarch64 toolchains codesourcery arm/aarch64 toolchains are old (2014) and use glibc 2.18/2.20 which are not compatible with 64-bit time_t raising the following build failure with libcgroup since commit 1c2dbcdcf0bb589d325c379246acaa39bb07b7be: In file included from ./libcgroup-internal.h:25:0, from parse.y:21: /home/buildroot/autobuild/run/instance-3/output-1/host/arm-buildroot-linux-gnueabi/sysroot/usr/include/fts.h:41:3: error: #error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" # error "<fts.h> cannot be used with -D_FILE_OFFSET_BITS==64" ^ Fixes: 1c2dbcdcf0bb589d325c379246acaa39bb07b7be - http://autobuild.buildroot.org/results/e28f955f2b360f6e7bb231a5a3800cfbd17a23d7 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Peter: add Config.in.legacy entries] Signed-off-by: Peter Korsgaard <peter@korsgaard.com> (cherry picked from commit 53a8c5150e5eeeb6dbbead0275dbf9141f507511) Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-09 17:49:46 +01:00
select BR2_LEGACY
help
The Sourcery CodeBench AArch64 toolchain has been removed,
use an ARM/Bootlin/Linaro toolchain instead.
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_ARM
bool "Sourcery CodeBench ARM 2014.05 has been removed"
select BR2_LEGACY
help
The Sourcery CodeBench ARM toolchain has been removed, use
an ARM/Bootlin/Linaro toolchain instead.
package/mysql: drop virtual package Now that oracle-mysql is dropped there isn't any need for the mysql virtual package. Adjust the other packages to directly use the mariadb symbols. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-03 21:46:41 +01:00
config BR2_PACKAGE_MYSQL
bool "mysql virtual package removed"
select BR2_LEGACY
help
The mysql virtual package has been removed as mariadb is the
only supported mysql variant. Use the mariadb package
instead.
package/oracle-mysql: drop package The package has not seen any updates for ~10 years, E.G. latest version bump was in commit 42c56751fc55 (mysql: bump to version 5.1.73) and the version contains multiple known vulnerabilities, so drop the package. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-03 21:46:40 +01:00
config BR2_PACKAGE_ORACLE_MYSQL
bool "oracle mysql removed"
select BR2_LEGACY
help
Oracle mysql has been removed as the package was
unmaintained. Consider using mariadb instead.
package/strongswan: drop BR2_PACKAGE_STRONGSWAN_SCEP scepclient is unrecognized since bump to version 5.9.8 in commit b79d735139282ecf052dc89d4c221bbd16447112 and https://github.com/strongswan/strongswan/commit/8716f7c03c6193b1cb53837243177f36280ff4f7: configure: WARNING: unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html, --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6, --disable-nls, --enable-scepclient Fixes: b79d735139282ecf052dc89d4c221bbd16447112 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-03-03 18:26:22 +01:00
config BR2_PACKAGE_STRONGSWAN_SCEP
bool "strongswan SCEP client tool removed"
select BR2_LEGACY
help
"ipsec scepclient" tool has been removed and replaced by the
pki subcommands "pki --scep" and "pki --scepca" which
implement the new SCEP RFC 8894 standard that was released in
September 2020 and which supports trusted "certificate
renewal" based on the existing client certificate.
package/shadow: drop BR2_PACKAGE_SHADOW_UTMPX utmpx is not available since bump to version 4.14.3 in commit 8a01774d9897310c00a0945865f5a6d5167dfca3 and https://github.com/shadow-maint/shadow/commit/3be7b9d75a6b73fe24394d7ac1e315d60d45b5ee: configure: WARNING: unrecognized options: --disable-gtk-doc, --disable-gtk-doc-html, --disable-doc, --disable-docs, --disable-documentation, --with-xmlto, --with-fop, --enable-ipv6, --enable-utmpx Fixes: 8a01774d9897310c00a0945865f5a6d5167dfca3 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
2024-02-11 22:47:51 +01:00
config BR2_PACKAGE_SHADOW_UTMPX
bool "shadow utmpx removed"
select BR2_LEGACY
help
UTMPX has been dropped by upstream.
package/tinymembench: drop package As advised by Thomas Petazzoni in [1], drop tinymembench which is abandonned (last commit in 2017). Moreover, it raises the following build failure in Thumb mode: /tmp/ccaZHrla.s:40: Error: instruction not supported in Thumb16 mode -- `subs r1,r1,#16' /tmp/ccaZHrla.s:43: Error: instruction not supported in Thumb16 mode -- `subs r1,r1,#16' main.c:45: Error: selected processor does not support `mla r2,r10,r2,r5' in Thumb mode main.c:46: Error: unshifted register required -- `and r8,r7,r2,lsr#16' main.c:47: Error: selected processor does not support `mla r2,r10,r2,r5' in Thumb mode main.c:48: Error: unshifted register required -- `and r9,r6,r2,lsr#8' main.c:49: Error: selected processor does not support `mla r2,r10,r2,r5' in Thumb mode [1]: https://patchwork.ozlabs.org/project/buildroot/patch/20240114135446.1156025-1-fontaine.fabrice@gmail.com/ Fixes: - http://autobuild.buildroot.org/results/1e359c294a8d71fb1833e5d04a6bc7d4fd533510 - http://autobuild.buildroot.org/results/c06010d7a2bdb33a1707266133a3880e14be7657 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2024-02-08 20:54:38 +01:00
config BR2_PACKAGE_TINYMEMBENCH
bool "tinymembench removed"
select BR2_LEGACY
help
tinymembench has been removed due to being abandoned.
package/davinci-bootcount: rename to uboot-bootcount Born as a project to read/write the bootcount on the TI am3xx platform, over time it has introduced bootcount management on EEPROM and for the stm32mp1 platform. As a result, the project removed the 'davinci' tag from its name and GitHub link. The patch aligns the package name in Buildroot with the current one on GitHub. Signed-off-by: Dario Binacchi <dario.binacchi@amarulasolutions.com> [Peter: extend/rework legacy handling] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-02-07 10:24:46 +01:00
config BR2_PACKAGE_DAVINCI_BOOTCOUNT
bool "davinci-bootcount has been renamed"
select BR2_LEGACY
select BR2_PACKAGE_UBOOT_BOOTCOUNT
help
The davinci-bootcount package has been renamed to
uboot-bootcount.
package/python-crossbar: drop package The current package has not recieved an update since Sat Oct 9 2021 33ece2446e25e20929d1c7eefa9f3244a3b79a92 and is not python 3.12 compatible. Furthermore, the current version requires at least 42 new packages worth of depedencies of which several require patches to be python 3.12 compatible. As nobody has stepped up to maintain the package and its ever-growing list of dependencies, along with the other problems, it is time to drop the package. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-12-18 23:04:55 +01:00
config BR2_PACKAGE_PYTHON_CROSSBAR
bool "python-crossbar removed"
select BR2_LEGACY
help
python-crossbar has been removed. The current package has
not received an update since Sat Oct 9 13:55:06 2021 commit:
33ece2446e25e20929d1c7eefa9f3244a3b79a92 and is not python
3.12.0 compatible.
Furthermore, the current version requires at least 42 new
packages worth of depedencies of which several require
patches to be python 3.12.0 compatible. As nobody has
stepped up to maintain the package and its ever-growing list
of dependencies, along with the other problems, it was time
to drop the package.
package/python-pygame: drop package The python-pygame package has not recieved any update since Sun May 1 22:15:17 2016 (commit: a9ec96e545102ae5ccd4280323d35360b0a5072d) Also, this package no longer builds properly against python 3.12.0. Receiving the following error when building: ``` src/surface.c:2812:14: error: invalid type argument of unary ‘*’ (have ‘int’) 2812 | ch = *PyUnicode_AS_UNICODE (obj); | ^~~~~~~~~~~~~~~~~~~~~~~~~~~ src/surface.c: In function ‘PySurface_Blit’: ``` If someone wants to re-introduce this package at a later date they are more than welcome to do so! Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-12-18 23:04:54 +01:00
config BR2_PACKAGE_PYTHON_PYGAME
bool "python-pygame removed"
select BR2_LEGACY
help
python-pygame has been removed due to being abandoned and
the old version no longer building with python 3.12.0.
package/linux-headers: drop 4.14.x option The 4.14.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2024-01-13 17:26:47 +01:00
config BR2_KERNEL_HEADERS_4_14
bool "kernel headers version 4.14.x are no longer supported"
select BR2_LEGACY
help
Version 4.14.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/libcamera: pipeline option 'raspberrypi' changed to 'rpi/vc4' With upstram commit [1] (since version v0.1.0) the pipeline option 'raspberrypi' was renamed to 'rpi/vc4'. Change the buildroot option name from BR2_PACKAGE_LIBCAMERA_PIPELINE_RASPBERRYPI to BR2_PACKAGE_LIBCAMERA_PIPELINE_RPI_VC4 (and add Config.in.legacy entry accordingly) and move handling in Config.in/libcamer.mk to follow alphabetic ordering. Fixes: .../build/libcamera-v0.1.0/meson.build:3:0: ERROR: Options "raspberrypi" are not in allowed choices: "all, auto, imx8-isi, ipu3, rkisp1, rpi/vc4, simple, uvcvideo, vimc" [1] https://git.libcamera.org/libcamera/libcamera.git/commit/?id=726e9274ea95fa46352556d340c5793a8da51fcd Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-09 22:28:58 +01:00
config BR2_PACKAGE_LIBCAMERA_PIPELINE_RASPBERRYPI
bool "libcamera pipeline 'raspberrypi' was renamed to 'rpi/vc4'"
depends on BR2_arm || BR2_aarch64
depends on BR2_USE_WCHAR
select BR2_LEGACY
select BR2_PACKAGE_LIBCAMERA_PIPELINE_RPI_VC4
help
Config.in.legacy: fix check-package errors Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-27 23:18:04 +01:00
Since version 0.1.0, the pipeline option 'raspberrypi' was
package/libcamera: pipeline option 'raspberrypi' changed to 'rpi/vc4' With upstram commit [1] (since version v0.1.0) the pipeline option 'raspberrypi' was renamed to 'rpi/vc4'. Change the buildroot option name from BR2_PACKAGE_LIBCAMERA_PIPELINE_RASPBERRYPI to BR2_PACKAGE_LIBCAMERA_PIPELINE_RPI_VC4 (and add Config.in.legacy entry accordingly) and move handling in Config.in/libcamer.mk to follow alphabetic ordering. Fixes: .../build/libcamera-v0.1.0/meson.build:3:0: ERROR: Options "raspberrypi" are not in allowed choices: "all, auto, imx8-isi, ipu3, rkisp1, rpi/vc4, simple, uvcvideo, vimc" [1] https://git.libcamera.org/libcamera/libcamera.git/commit/?id=726e9274ea95fa46352556d340c5793a8da51fcd Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-09 22:28:58 +01:00
renamed to 'rpi/vc4'.
package/gdb: remove support for GDB 11.x After adding GDB 14.x and making GDB 13.x the new default, let's drop support for GDB 11.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-24 17:08:29 +01:00
config BR2_GDB_VERSION_11
bool "gdb 11.x removed"
select BR2_LEGACY
help
GDB 11.x has been removed, use a newer version.
package/libmpd: remove package Following the removal of gmpc, we can drop libmpd as well, which was apparently developed/maintained by the same group of people. The URL in Config.in, http://gmpcwiki.sarine.nl/index.php?title=Libmpd, no longer works, and no new alternative upstream was found. The reference MPD client library is libmpdclient, which is still maintained. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-26 14:59:40 +01:00
config BR2_PACKAGE_LIBMPD
bool "libmpd package was removed"
select BR2_LEGACY
help
The libmpd package was only used by gmpc, both of which are
no longer maintained upstream.
package/gmpc: remove package This package is unmaintained upstream: - The URL in our Config.in, http://gmpcwiki.sarine.nl/index.php?title=GMPC, no longer works - https://github.com/DaveDavenport/gmpc says it's unmaintained - The official lists of MPD clients at https://www.musicpd.org/clients/ says it's maintained, and points at http://gmpclient.org/, which is no longer owned by the developers of GMPC. - It still uses libsoup (2) which we want to get rid of at some point. - It was added by Gustavo Zacarias, and no version bumped occurred since 2011. So let's kill this package. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-26 14:59:39 +01:00
config BR2_PACKAGE_GMPC
bool "gmpc package was removed"
select BR2_LEGACY
help
The gmpc package was removed because it was unmaintained,
and still using the old libsoup2 library.
package/flickcurl: remove package This package is causing some build issues, which are probably due to the recent libxml2 upgrade: http://autobuild.buildroot.net/results/34d6f6c02f884ab9a2578a38ee8646e14632d6ff/ There has been no new commit upstream for the past 8 years: https://github.com/dajobe/flickcurl, and the last release, 1.26 is from 2014. So let's kill the package. Fixes: http://autobuild.buildroot.net/results/34d6f6c02f884ab9a2578a38ee8646e14632d6ff/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-26 14:18:04 +01:00
config BR2_PACKAGE_FLICKCURL
bool "flickcurl package was removed"
select BR2_LEGACY
help
The flickcurl package was removed because it was
unmaintained upstream and causing build failures.
package/onevpl: rename package to libvpl Upstream changed the package name and its github repo: https://github.com/intel/libvpl/commit/44df6e08cc836ed65725ed344e7ec9ded5193874 Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-12-24 09:13:19 +01:00
config BR2_PACKAGE_ONEVPL
bool "onevpl package was renamed"
select BR2_LEGACY
select BR2_PACKAGE_LIBVPL
package/linux-headers: drop 6.5.x option The 6.5.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> [Peter: drop option from linux-headers/Config.host.in] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-12-17 18:18:20 +01:00
config BR2_KERNEL_HEADERS_6_5
bool "kernel headers version 6.5.x are no longer supported"
select BR2_LEGACY
help
Version 6.5.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/watchdogd: bump to version 4.0 For details, see https://github.com/troglobit/watchdogd/releases/tag/4.0 - Major feature upgrade, command line and .conf files compatible - LICENSE hash update due to update in copyright years - Enabling system monitor plugins have changed syntax upstream. The `--with-foo=SECONDS` is now just `--with-foo` This last upstream change require converting affected Config.in options from int -> bool. Legacy _WRAP:ers have been added to Config.legacy.in, modeled on BR2_TARGET_ROOTFS_EXT2_BLOCKS. Forcibly disable new monitors; they'll be enabled in a followup commit. Signed-off-by: Joachim Wiberg <troglobit@gmail.com> [yann.morin.1998@free.fr: - forcibly disable new monitors - minor tweaks in Config.in.legacy ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2024-01-30 22:56:24 +01:00
config BR2_PACKAGE_WATCHDOGD_GENERIC_POLL
int "watchdogd generic poll has been replaced"
default 0
help
The generic script poll interval has been replaced upstream
with a boolean on/off. Your configuration has been migrated.
Set this legacy option to 0 here to remove the warning.
# Note: BR2_PACKAGE_WATCHDOGD_*_POLL_WRAP referenced in package/watchdogd/Config.in
config BR2_PACKAGE_WATCHDOGD_GENERIC_POLL_WRAP
bool
default y if BR2_PACKAGE_WATCHDOGD_GENERIC_POLL != 0
select BR2_LEGACY
config BR2_PACKAGE_WATCHDOGD_LOADAVG_POLL
int "watchdogd loadavg poll has been replaced"
default 0
help
The CPU load average poll interval has been replaced upstream
with a boolean on/off. Your configuration has been migrated.
Set this legacy option to 0 here to remove the warning.
# Note: BR2_PACKAGE_WATCHDOGD_*_POLL_WRAP referenced in package/watchdogd/Config.in
config BR2_PACKAGE_WATCHDOGD_LOADAVG_POLL_WRAP
bool
default y if BR2_PACKAGE_WATCHDOGD_LOADAVG_POLL != 0
select BR2_LEGACY
config BR2_PACKAGE_WATCHDOGD_FILENR_POLL
int "watchdogd filenr poll has been replaced"
default 0
help
The file descriptor leak poll has been replaced upstream with
a boolean on/off. Your configuration has been migrated.
Set this legacy option to 0 here to remove the warning.
# Note: BR2_PACKAGE_WATCHDOGD_*_POLL_WRAP referenced in package/watchdogd/Config.in
config BR2_PACKAGE_WATCHDOGD_FILENR_POLL_WRAP
bool
default y if BR2_PACKAGE_WATCHDOGD_FILENR_POLL != 0
select BR2_LEGACY
config BR2_PACKAGE_WATCHDOGD_MEMINFO_POLL
int "watchdogd meminfo poll has been replaced"
default 0
help
The memleak detector poll interval has been replaced upstream
with a boolean on/off. Your configuration has been migrated.
Set this legacy option to 0 here to remove the warning.
# Note: BR2_PACKAGE_WATCHDOGD_*_POLL_WRAP referenced in package/watchdogd/Config.in
config BR2_PACKAGE_WATCHDOGD_MEMINFO_POLL_WRAP
bool
default y if BR2_PACKAGE_WATCHDOGD_MEMINFO_POLL != 0
select BR2_LEGACY
Config.in.legacy: recent removals are for the future release A few package or config removals have been introduced after the 2023.11 release, but there entries were still added to the list of options removed in 2023.11. The affected commits are: 64a5831679 package/libmpd: remove package f93380ab1a package/gmpc: remove package 6d8c7aecbb package/flickcurl: remove package f6acde11ab package/onevpl: rename package to libvpl fffb245f66 package/linux-headers: drop 6.5.x option Introduce the 2024.02 section and move the 2023.11 one to where it belongs. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-12-27 22:22:52 +01:00
comment "Legacy options removed in 2023.11"
package/python-pyxb: Drop package The last time python-pyxb was updated according to pypi.org is in 2017. As there are no maintainers listed for the package, and the package uses distutils which has been removed in Python 3.12.0, remove the package. Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-11-05 21:25:49 +01:00
config BR2_PACKAGE_PYTHON_PYXB
bool "python-pyxb removed"
select BR2_LEGACY
help
python-pyxb has been removed due to being abandoned and
distutils no longer being supported in python 3.12.0.
package/openjdk{-bin}: drop OpenJDK11 and add OpenJDK21 OpenJDK 21 is out and with it, OpenJDK11 is now EOL. See: https://endoflife.date/oracle-jdk As such, drop support for 11 and do the following: - The 0001-Add-ARCv2-ISA-processors-support-to-Zero.patch patch now applies to both 17 and 21. Move it out of the version-specific directoriy. - BR2_OPENJDK_VERSION_LTS is now set to 17. - BR2_OPENJDK_VERSION_LATEST is now set to 21. - Drop --disable-hotspot-gtest as it has been removed, and was ignored in 17. - Add two separate HOST_OPENJDK_BIN_VERSION defines in openjdk-bin.mk as there is not a point release yet for OpenJDK 21. - Update the expectedVersion variable in JniTest.java from 0x000A0000 to 0x00150000 Tested with: ./support/testing/run-tests tests.package.test_openjdk.TestOpenJdk.test_run Signed-off-by: Adam Duskett <adam.duskett@amarulasolutions.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-10-17 19:36:11 +02:00
config BR2_PACKAGE_OPENJDK_VERSION_11
bool "openjdk 11 has been removed"
select BR2_LEGACY
help
Version 11 of OpenJDK is no longer supported, version 17
should now be used as the new LTS release.
package/linux-headers: drop 6.4.x option The 6.4.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-09-23 19:32:52 +02:00
config BR2_KERNEL_HEADERS_6_4
bool "kernel headers version 6.4.x are no longer supported"
select BR2_LEGACY
help
Version 6.4.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/google-material-design-icons: drop package Newer versions of Google's Material Design icon package are structured differently, making a version bump no so trivial. While work can be done to support this, considering this package is using v2.2.3 and the most recent version is v4.0, it is most likely that this package is not being used. Environments which desire Material icons/fonts/etc. will most likely achieve better results be managing their own custom package to have an explicit selection/filter of design styles (e.g. standard, Android, etc.), variants (basic, outlined, rounds, etc.), display resolutions and scale selection desired. Signed-off-by: James Knight <james.d.knight@live.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-04-29 21:52:24 +02:00
config BR2_PACKAGE_GOOGLE_MATERIAL_DESIGN_ICONS
bool "google-material-design-icons removed"
select BR2_LEGACY
help
The google-material-design-icons package has been removed.
package/gdb: remove gdb 10.x Now that gdb 13.x has been added, and 12.x made the default, follow our usual logic of dropping the oldest gdb version: 10.x. Only the special ARC release still needs some special handling of the GMP dependency. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-08-02 23:49:48 +02:00
config BR2_GDB_VERSION_10
bool "gdb 10.x removed"
select BR2_LEGACY
help
gdb 10.x has been removed, use a newer version.
package/binutils: drop 2.37.x series Now that 2.40.x has been added, that 2.39.x is the default version, drop support for 2.37.x. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-06-11 15:16:31 +02:00
comment "Legacy options removed in 2023.08"
boot/lpc32xxcdl: remove package This package has dubious licensing conditions (not even documented in the .mk file), and is a bootloader for very old platforms. The defconfigs making use of it have been removed in Buildroot in 2014, in commit c6a410964bee6b4c57801c363384778f6908e6a2 ("configs: remove lpc32xx defconfigs"), so let's get rid of the package. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: Alexandre Belloni <alexandre.belloni@bootlin.com> [yann.morin.1998@free.fr: remove reference in test] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-08-09 23:48:05 +02:00
config BR2_TARGET_LPC32XXCDL
bool "lpc32xxcdl has been removed"
select BR2_LEGACY
help
lpc32xxcdl has been removed, due to licensing concerns.
package/binutils: drop 2.38.x series Now that 2.41.x has been added, that 2.40.x is the default version, drop support for 2.38.x. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-08-01 22:21:40 +02:00
config BR2_BINUTILS_VERSION_2_38_X
bool "binutils 2.38.x has been removed"
select BR2_LEGACY
help
binutils 2.38 has been removed, use a newer version.
package/gcc: remove gcc 10.x gcc 13.2 is around, gcc 12.3 is the default version, so drop 10.4 in order to reduce the gcc choice. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-28 00:25:44 +02:00
config BR2_GCC_VERSION_10_X
bool "gcc 10.x support removed"
select BR2_LEGACY
help
Support for gcc version 10.x has been removed. The current
default version (12.x or later) has been selected instead.
package/linux-headers: drop 6.3.x option The 6.3.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-20 07:39:15 +02:00
config BR2_KERNEL_HEADERS_6_3
bool "kernel headers version 6.3.x are no longer supported"
select BR2_LEGACY
help
Version 6.3.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/tovid: remove package Build is broken: "It seems that you are using `distutils.command.build` to add new subcommands. Using `distutils` directly is considered deprecated, please use `setuptools.command.build`. By 2023-Dec-13, you need to update your project and remove deprecated calls or your builds will no longer be supported." The last commit for this package occured on May, 30th, 2016. The last issue was opened Jan, 31st, 2017 and was unanswered. Fixes: http://autobuild.buildroot.net/results/b57/b571d7838950e0b5ca67106cbcd9ba61b4f04a48/ Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-14 22:54:31 +02:00
config BR2_PACKAGE_TOVID
bool "tovid removed"
select BR2_LEGACY
help
tovid was removed
package/libasplib: remove package Added in 2015 to be used by Kodi ADSP addons these efforts have stopped: https://forum.kodi.tv/showthread.php?tid=252871&pid=3053658#pid3053658 so this package is no longer needed. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-02 09:04:30 +02:00
config BR2_PACKAGE_LIBASPLIB
bool "libasplib removed"
select BR2_LEGACY
help
libasplib is no longer needed.
package/ocf-linux: remove package Fixes: http://autobuild.buildroot.net/results/88b/88b5d14b315af1669fff04f8c11c321cc4c107c7/ The package seems to be unmaintainted, asking for support of kernels >= 5.6 a year ago was unanswered: https://sourceforge.net/p/ocf-linux/mailman/message/37662698/ This patch follow Thomas' suggestion to remove the package: https://lists.buildroot.org/pipermail/buildroot/2022-November/654688.html Remove the virtual package cryptodev which is not needed anymore. Signed-off-by: Bernd Kuhls <bernd@kuhls.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-07-06 22:46:10 +02:00
config BR2_PACKAGE_OCF_LINUX
bool "ocf-linux has been removed"
select BR2_LEGACY
help
ocf-linux is incompatible with newer kernels.
package/binutils: drop 2.37.x series Now that 2.40.x has been added, that 2.39.x is the default version, drop support for 2.37.x. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-06-11 15:16:31 +02:00
config BR2_BINUTILS_VERSION_2_37_X
bool "binutils 2.37.x has been removed"
select BR2_LEGACY
help
binutils 2.37 has been removed, use a newer version.
package/openfpgaloader: fix typos Fix a typo in the name of two configuration options. This repairs the selection of libgpiod support. Signed-off-by: Vincent Stehlé <vincent.stehle@laposte.net> Cc: Jean Burgat <jeanburgat33@gmail.com> Acked-by: Gwenhael Goavec-merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-03-06 22:16:46 +01:00
comment "Legacy options removed in 2023.05"
package/linux-headers: drop 6.2.x option The 6.2.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-05-24 22:56:29 +02:00
config BR2_KERNEL_HEADERS_6_2
bool "kernel headers version 6.2.x are no longer supported"
select BR2_LEGACY
help
Version 6.2.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/atk: remove package atk has been merged into at-spi2-core with version 2.45.1. https://gitlab.gnome.org/GNOME/at-spi2-core/-/blob/AT_SPI2_CORE_2_45_1/NEWS https://gitlab.gnome.org/GNOME/at-spi2-core/-/merge_requests/78 Signed-off-by: Daniel Lang <d.lang@abatec.at> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com> Tested-by: Adrian Perez de Castro <aperez@igalia.com> Reviewed-by: Adrian Perez de Castro <aperez@igalia.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-04-28 09:59:18 +02:00
config BR2_PACKAGE_ATK
bool "atk removed"
select BR2_LEGACY
help
atk is now part of at-spi2-core.
package/at-spi2-atk: remove package at-spi2-atk has been merged into at-spi2-core with version 2.45.1. https://gitlab.gnome.org/GNOME/at-spi2-core/-/blob/AT_SPI2_CORE_2_45_1/NEWS https://gitlab.gnome.org/GNOME/at-spi2-core/-/merge_requests/78 Signed-off-by: Daniel Lang <d.lang@abatec.at> Signed-off-by: Thomas Devoogdt <thomas.devoogdt@barco.com> Tested-by: Adrian Perez de Castro <aperez@igalia.com> Reviewed-by: Adrian Perez de Castro <aperez@igalia.com> [yann.morin.1998@free.fr: regenerate .checkpackageignore] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-04-28 09:59:17 +02:00
config BR2_PACKAGE_AT_SPI2_ATK
bool "at-spi2-atk removed"
select BR2_LEGACY
help
at-spi2-atk is now part of at-spi2-core.
Config.in.legacy: add entry for optee-benchmark Commit cf39b596e7a8 (package/optee-benchmark: remove deprecated package) forgot to add a legacy entry. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-05-07 23:34:43 +02:00
config BR2_PACKAGE_OPTEE_BENCHMARK
bool "optee-benchmark has been removed"
select BR2_LEGACY
help
optee-benchmark is no longer maintained upstream.
package/openfpgaloader: fix typos Fix a typo in the name of two configuration options. This repairs the selection of libgpiod support. Signed-off-by: Vincent Stehlé <vincent.stehle@laposte.net> Cc: Jean Burgat <jeanburgat33@gmail.com> Acked-by: Gwenhael Goavec-merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-03-06 22:16:46 +01:00
config BR2_PACAKGE_OPENFPGALOADER_CMSIS
bool "openfpgaloader cmsis option name fixed"
select BR2_LEGACY
help
A typo on BR2_PACAKGE_OPENFPGALOADER_CMSIS was fixed by
renaming the option to BR2_PACKAGE_OPENFPGALOADER_CMSIS.
Merge branch 'next' Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-05 10:01:26 +01:00
comment "Legacy options removed in 2023.02"
package/gdb: remove support for 9.2 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-08-13 10:35:18 +02:00
package/pugixml: drop header-only option Header-only option raises the following build failure with gerbera since commit cc3a4a7b1de7b158354c650d234339e8a969a730: /home/thomas/autobuild/instance-2/output-1/host/lib/gcc/nios2-buildroot-linux-gnu/10.4.0/../../../../nios2-buildroot-linux-gnu/bin/ld: CMakeFiles/gerbera.dir/src/main.cc.o: in function `ConfigGenerator::~ConfigGenerator()': /home/thomas/autobuild/instance-2/output-1/build/gerbera-1.10.0/src/config/config_generator.h:33: undefined reference to `pugi::xml_document::~xml_document()' This build failure can't be fixed by adding a !BR2_PACKAGE_PUGIXML_HEADER_ONLY dependency as it will create the following recursive dependency: package/gerbera/Config.in:1:error: recursive dependency detected! package/gerbera/Config.in:1: symbol BR2_PACKAGE_GERBERA depends on BR2_PACKAGE_PUGIXML_HEADER_ONLY package/pugixml/Config.in:42: symbol BR2_PACKAGE_PUGIXML_HEADER_ONLY depends on BR2_PACKAGE_PUGIXML package/pugixml/Config.in:1: symbol BR2_PACKAGE_PUGIXML is selected by BR2_PACKAGE_GERBERA Moreover, commit 48b2e50eb8df36e3e3ab18692bd9e0dde3b38702 stated that "Compact and header-only modes are not strictly needed for our use case, but we did the work anyway and may be useful for someone else." So dropping header-only seems to be the right approach Fixes: - http://autobuild.buildroot.org/results/800537a1ef5f48d24c20aad7a9c96c56dfdc77f5 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-28 23:16:24 +01:00
config BR2_PACKAGE_PUGIXML_HEADER_ONLY
bool "pugixml header-only removed"
select BR2_LEGACY
help
The header-only version raises a build failure with gerbera.
package/uccp420wlan: drop package uccp420wlan is not maintained anymore (no commit since 2017) and fails to build with any "recent" kernel (e.g. >= 4.7 which includes https://github.com/torvalds/linux/commit/57fbcce37be7c1d2622b56587c10ade00e96afa3 or https://github.com/torvalds/linux/commit/8552a434b6a05cc38006733afe6a239ad4d600a2): /home/thomas/autobuild/instance-1/output-1/build/uccp420wlan-6.9.1/./src/tx.c: In function ‘uccp420wlan_tx_free_buff_req’: /home/thomas/autobuild/instance-1/output-1/build/uccp420wlan-6.9.1/./src/tx.c:1142:49: error: ‘IEEE80211_BAND_2GHZ’ undeclared (first use in this function); did you mean ‘IEEE80211_CHAN_2GHZ’? 1142 | if (ets_band == IEEE80211_BAND_2GHZ) | ^~~~~~~~~~~~~~~~~~~ | IEEE80211_CHAN_2GHZ [...] /home/thomas/autobuild/instance-1/output-1/build/uccp420wlan-6.9.1/./src/core.c:428:29: error: implicit declaration of function ‘ieee80211_csa_is_complete’; did you mean ‘ieee80211_scan_completed’? [-Werror=implicit-function-declaration] 428 | if (ieee80211_csa_is_complete(uvif->vif)) | ^~~~~~~~~~~~~~~~~~~~~~~~~ | ieee80211_scan_completed Fixes: - http://autobuild.buildroot.org/results/7cd7151e390b8f7a0df3e647fe4cd5d6319a830b Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-02-26 18:23:28 +01:00
config BR2_PACKAGE_UCCP420WLAN
bool "uccp420wlan removed"
select BR2_LEGACY
help
The uccp420wlan package is unmaintained and doesn't build
with any "recent" kernel (e.g. >= 4.7).
package/freescale-imx/imx-gpu-g2d: drop BR2_PACKAGE_IMX_GPU_G2D_EXAMPLES Arm and aarch64 packages don't contain examples anymore so drop the config option to install them to prevent build failure when selected: >>> imx-gpu-g2d 6.4.3.p4.4-arm Installing to target mkdir -p /home/sszy/br-test-pkg/bootlin-armv7-glibc/target/usr/share/examples/ cp -a /home/sszy/br-test-pkg/bootlin-armv7-glibc/build/imx-gpu-g2d-6.4.3.p4.4-arm/gpu-demos/opt/* /home/sszy/br-test-pkg/bootlin-armv7-glibc/target/usr/share/examples/ cp: cannot stat '/home/sszy/br-test-pkg/bootlin-armv7-glibc/build/imx-gpu-g2d-6.4.3.p4.4-arm/gpu-demos/opt/*': No such file or directory make: *** [package/pkg-generic.mk:384: /home/sszy/br-test-pkg/bootlin-armv7-glibc/build/imx-gpu-g2d-6.4.3.p4.4-arm/.stamp_target_installed] Error 1 Fixes: b84557b588b3 ("package/freescale-imx/imx-gpu-g2d: bump version to 6.4.3.p4.4") Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-02-24 11:53:15 +01:00
config BR2_PACKAGE_IMX_GPU_G2D_EXAMPLES
bool "imx-gpu-g2d examples removed"
select BR2_LEGACY
help
The examples are not provided by NXP anymore.
package/linux-headers: drop 6.0.x option The 6.0.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-13 12:58:11 +01:00
config BR2_KERNEL_HEADERS_6_0
bool "kernel headers version 6.0.x are no longer supported"
select BR2_LEGACY
help
Version 6.0.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop 4.9.x option The 4.9.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-13 12:58:10 +01:00
config BR2_KERNEL_HEADERS_4_9
bool "kernel headers version 4.9.x are no longer supported"
select BR2_LEGACY
help
Version 4.9.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/docker-proxy: drop package The docker-proxy binary (libnetwork) has been merged into the docker-engine source (moby). Drop the docker-proxy package and add cmd/docker-proxy as a build target of docker-engine instead. https://github.com/moby/libnetwork/commit/563fe8e248f3afac75a270f693f38bdc3eea7bf3 Signed-off-by: Christian Stewart <christian@paral.in> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2023-02-07 05:30:09 +01:00
config BR2_PACKAGE_DOCKER_PROXY
bool "docker-proxy removed"
select BR2_LEGACY
select BR2_PACKAGE_DOCKER_ENGINE
help
docker-proxy has been dropped by upstream since version
563fe8. it has been merged into docker-engine (moby).
package/python-bunch: remove package Since the python3 bump to version 3.11 in commit 738500c296c8b1206f20e94ca3e7c5932a6a0486 python-bunch has failed to build. This is due to open() which no longer accepts 'U' (“universal newline”) in the file mode. Remove this package as it has not had a release since 2011 and is unmaintained upstream. Details: https://docs.python.org/3.11/whatsnew/3.11.html#porting-to-python-3-11 Fixes: - http://autobuild.buildroot.net/results/2ba/2ba72fc9837605a36ea63bbd3e6e181a40cdf360 Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Reviewed-by: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-12 16:41:11 +01:00
config BR2_PACKAGE_PYTHON_BUNCH
bool "python-bunch removed"
select BR2_LEGACY
help
The python-bunch package is unmaintained and is replaced
by the python-munch package.
boot/gummiboot: remove package The gummiboot package currently fails to build due to incompatibilies with recent versions of the gnu-efi code. It turns out that gummiboot has been marked deprecated/obsolete by its maintainer since July 2015: https://cgit.freedesktop.org/gummiboot/commit/?id=55df1539c9d330732e88bd196afee386db6e4a1d&utm_source=anzwix Indeed, gummiboot ended up being integrated as part of systemd as systemd-boot. While it made sense for a while to keep it as a separate standalone package, it is not possible to maintain it in Buildroot without an active upstream, and there are other options for simple EFI bootloaders these days. Therefore, let's retire this package. Fixes: http://autobuild.buildroot.net/results/5929104a868d2f69ec1b71e5e897b6d1ebf347cf/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-20 08:44:20 +02:00
config BR2_TARGET_GUMMIBOOT
bool "gummiboot removed"
select BR2_LEGACY
help
gummiboot has been deprecated since 2015, with no further
updates. It became integrated into the systemd project as
systemd-boot.
package/iputils: bump version to 20221126 This release removed: ninfod, rarpd, rdisc => add entries to Config.in.legacy. LICENSE file got updated (just to use SPDX) => update checksum. Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Reviewed-by: Heiko Thiery <heiko.thiery@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-11-26 01:38:07 +01:00
config BR2_PACKAGE_IPUTILS_NINFOD
bool "iputils 20221126 removed ninfod"
select BR2_LEGACY
help
iputils 20221126 removed ninfod.
config BR2_PACKAGE_IPUTILS_RARPD
bool "iputils 20221126 removed rarpd"
select BR2_LEGACY
help
iputils 20221126 removed rarpd.
config BR2_PACKAGE_IPUTILS_RDISC
bool "iputils 20221126 removed rdisc"
select BR2_LEGACY
help
iputils 20221126 removed rdisc.
config BR2_PACKAGE_IPUTILS_RDISC_SERVER
bool "iputils 20221126 removed rdisc"
select BR2_LEGACY
help
iputils 20221126 removed rdisc.
package/gst1-plugins-ugly: bump version to 1.22.0 Remove xingmux config option which has been moved to the gst1-plugins-good package. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-01 06:16:51 +01:00
config BR2_PACKAGE_GST1_PLUGINS_UGLY_PLUGIN_XINGMUX
bool "xingmux moved"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_GOOD_PLUGIN_XINGMUX
help
The xingmux option has been moved to gst1-plugins-good.
package/gst1-plugins-base: bump version to 1.22.0 The videoconvert and videoscale plugins have been combined into the new videoconvertscale plugin. Rework config options using videoconvert/videoscale to use the new videoconvertscale option. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-01 06:16:48 +01:00
config BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_VIDEOSCALE
bool "videoscale removed"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_VIDEOCONVERTSCALE
help
The videoscale option has been combined with videoconvert.
config BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_VIDEOCONVERT
bool "videoconvert removed"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_VIDEOCONVERTSCALE
help
The videoconvert option has been combined with videoscale.
package/freescale-imx/imx-gpu-viv: drop X11 output Since e8df0f7 (package/freescale-imx/imx-gpu-viv: bump to version 6.4.3.p4.4) the X11 folder is no longer included in the archive. Signed-off-by: Daniel Lang <d.lang@abatec.at> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2023-01-10 10:32:43 +01:00
config BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11
bool "imx-gpu-viv X11 output has been removed"
select BR2_LEGACY
help
The X11 output was dropped by NXP.
package/xdriver_xf86-video-imx-viv: drop package Commit 424f53ac0730 (package/freescale-imx/imx-gpu-viv: drop X11 output) dropped BR2_PACKAGE_IMX_GPU_VIV_OUTPUT_X11 which xdriver_xf86-video-imx-viv depends on, so the package is no longer selectable. So drop the package and add a legacy symbol for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-06 15:51:29 +01:00
config BR2_PACKAGE_XDRIVER_XF86_VIDEO_IMX_VIV
bool "xf86-video-imx-viv has been removed"
select BR2_LEGACY
help
The X11 output was dropped by NXP.
package/qemu: refactor target emulator selection The current mechanism to select emulation targets works this way: - BR2_PACKAGE_QEMU_SYSTEM selects the "system" (softmmu) targets. It selects FDT and creates a dependency on the "dtc" package but this is not always necessary. Only 14 system targets, out of 31, actually require FDT. - BR2_PACKAGE_QEMU_LINUX_USER selects the "linux-user" targets. It does not select FDT, which is not required by linux-user emulators. - Alternatively, we fill BR2_PACKAGE_QEMU_CUSTOM_TARGETS with a list of emulators (e.g. "x86_64-softmmu x86_64-linux-user"). Then we pass "--enable-system --enable-linux-user --target-list="..." to the configure script, so QEMU builds its list of default targets, from which it checks if the specified subset is valid. Since CUSTOM_TARGETS does not select FDT, we can get build errors like this: ../meson.build:2778:2: ERROR: Problem encountered: fdt not available but required by targets x86_64-softmmu We could select FDT when CUSTOM_TARGETS is set, but this would force an unnecessary dependency on dtc, as BR2_PACKAGE_QEMU_SYSTEM does. In order to fix these problems, refactor the package configuration: - Keep BR2_PACKAGE_QEMU_SYSTEM and BR2_PACKAGE_QEMU_LINUX_USER, which by default build all corresponding target emulators. - Add a BR2_PACKAGE_QEMU_CHOOSE_TARGETS config, to permit choosing the desired emulators. - Add configs for each supported target. They select FDT, when needed. - Move QEMU to a separate menu, since the number of configuration itens became too large. - Select BR2_LEGACY if BR2_PACKAGE_QEMU_CUSTOM_TARGETS is set, because this situation requires user intervention to reconfigure the package. - Reorganize the make file accordingly. Selecting CHOOSE_TARGETS without choosing at least one emulator is considered an error. Notes about the list of enabled targets: - when the user enables both system and user emulation, we provide no way to be able to build all system bt only parts of user (or the other way around), because the qemu build system does not allow that: when a list of target is passed, it applies to both system and user emulation; - as a consequence and in the same spirit, we also do not sanity-check that at least one system, resp. user, target is enabled when system, resp. user, emulation is enabled; we only require that one target is enabled, so that the list is not empty. Signed-off-by: Carlos Santos <unixmania@gmail.com> [yann.morin.1998@free.fr: - always build at least user or system - add help text to BR2_PACKAGE_QEMU_CHOOSE_TARGETS - simplify prompt for BR2_PACKAGE_QEMU_CHOOSE_TARGETS - simplify list of targets with unique QEMU_TARGET_LIST_y - extend the commit log with "Notes about the list of enabled targets" ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-12-27 12:48:42 +01:00
config BR2_PACKAGE_QEMU_CUSTOM_TARGETS
string "the QEMU specific targets option has been removed"
help
This option has been replaced by a list of individual targets
for the many architectures supported by QEMU.
config BR2_PACKAGE_QEMU_CUSTOM_TARGETS_WRAP
bool
default y if BR2_PACKAGE_QEMU_CUSTOM_TARGETS != ""
select BR2_LEGACY
package/x11r7/xdriver_xf86-input-keyboard: remove package According to the upstream release notes of version 2.0.0: https://lists.x.org/archives/xorg-announce/2022-July/003180.html "This keyboard driver is primarily used with BSD, GNU Hurd, illumos, & Solaris systems. Linux systems should instead use either xf86-input- libinput or xf86-input-evdev. While versions 1.9.0 and earlier had rudimentary support for Linux as well, that has been removed in this release." Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Peter: Reword help text] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-12 22:14:28 +01:00
config BR2_PACKAGE_XDRIVER_XF86_INPUT_KEYBOARD
bool "xf86-input-keyboard removed"
Config.in.legacy: select BR2_LEGACY from _XF86_INPUT_KEYBOARD Commit 1100ead7b318 (package/x11r7/xdriver_xf86-input-keyboard: remove package) added a legacy symbol for BR2_PACKAGE_XDRIVER_XF86_INPUT_KEYBOARD, but forgot to select BR2_LEGACY. Fix that. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-02-06 14:38:23 +01:00
select BR2_LEGACY
package/x11r7/xdriver_xf86-input-keyboard: remove package According to the upstream release notes of version 2.0.0: https://lists.x.org/archives/xorg-announce/2022-July/003180.html "This keyboard driver is primarily used with BSD, GNU Hurd, illumos, & Solaris systems. Linux systems should instead use either xf86-input- libinput or xf86-input-evdev. While versions 1.9.0 and earlier had rudimentary support for Linux as well, that has been removed in this release." Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Peter: Reword help text] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-12 22:14:28 +01:00
help
The X.org keyboard input driver no longer support Linux.
boot/sun20i-d1-spl: drop package U-Boot has now gained SPL support for D1, so this temporary bootloader is no longer supported. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-12 08:17:47 +01:00
config BR2_TARGET_SUN20I_D1_SPL
bool "sun20-d1-spl removed"
select BR2_LEGACY
help
U-Boot has gained SPL support for D1, so this temporary
bootloader is no longer supported.
package/python-m2r: remove package Since the bump of python-mistune to version 2.0.4 in commit ead539c27dd61ba010b3723b26af91da0779eb98, the python-m2r package fails to build: it is no longer maintained and no longer compatible with recent versions of python-mistune. Since the only user of python-m2r, python-automat, no longer needs it, we can safely drop this package. Fixes: http://autobuild.buildroot.net/results/9041acc5be4d2b33dee9ff0ad66dcd41d4dbfba1 Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-12-11 21:17:58 +01:00
config BR2_PACKAGE_PYTHON_M2R
bool "python-m2r removed"
select BR2_LEGACY
help
The python-m2r package is unmaintained.
package/{mesa3d, mesa3d-headers}: bump version to 22.3.0 Removed xmvc support due to upstream removal: https://cgit.freedesktop.org/mesa/mesa/commit/meson.build?h=22.3&id=8cc766d8f7eac26b7c029a2fac1bdfdba4776c29 Removed comment concerning gallium-xlib due to upstream removal: https://cgit.freedesktop.org/mesa/mesa/commit/meson.build?h=22.3&id=5bed3d4ad659c30cb0ef4b40172f1aab877ccc98 Rebased patch 0004 due to upstream commit: https://cgit.freedesktop.org/mesa/mesa/commit/src/util/macros.h?h=22.3&id=c0b891ecca2b92c9ef2945440c77f45345df3290 Please note that patch 0004 can be removed when buildroot toolchains are updated to uClibc 1.0.42: https://cgit.uclibc-ng.org/cgi/cgit/uclibc-ng.git/commit/?h=v1.0.42&id=03fbd941e943976bb92cb392882c2ff7ec218704 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-12-05 19:35:04 +01:00
config BR2_PACKAGE_MESA3D_XVMC
bool "mesa Gallium XvMC state tracker removed"
select BR2_LEGACY
help
The Gallium XvMC state tracker was removed upstream.
package/linux-headers: drop 5.19.x option The 5.19.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-12-11 09:15:14 +01:00
config BR2_KERNEL_HEADERS_5_19
bool "kernel headers version 5.19.x are no longer supported"
select BR2_LEGACY
help
Version 5.19.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/x11r7/xdriver_xf86-video-tga: remove package Building this package is broken with X.org xserver 21. Fixes: http://autobuild.buildroot.net/results/de5/de5efd922edb9eb7dc9981b5f10ea402487ee431/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-12-08 23:38:17 +01:00
config BR2_PACKAGE_XDRIVER_XF86_VIDEO_TGA
bool "xf86-video-tga removed"
select BR2_LEGACY
help
The X.org xf86-video-tga package was removed.
package/x11r7/xdriver_xf86-video-glint: remove package Building this package is broken with X.org xserver 21: https://gitlab.freedesktop.org/xorg/driver/xf86-video-glint/-/issues/1 Fixes: http://autobuild.buildroot.net/results/f9d/f9d650ccb4173085cfc8873f1e52ee56caf982fa/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-12-08 23:38:16 +01:00
config BR2_PACKAGE_XDRIVER_XF86_VIDEO_GLINT
bool "xf86-video-glint removed"
select BR2_LEGACY
help
The X.org xf86-video-glint package no longer builds with
Xserver 21 and is unmaintained.
package/usbredir: bump to version 0.13.0 usbredirserver was dropped by https://gitlab.freedesktop.org/spice/usbredir/-/commit/f4ffdce329305da2803684776f7659083a530819 Add an option to enable tools (and usbredirect binary) as a replacement to usbredirserver https://gitlab.freedesktop.org/spice/usbredir/-/blob/usbredir-0.13.0/ChangeLog.md Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-10-23 10:52:51 +02:00
config BR2_PACKAGE_USBREDIR_SERVER
bool "usbredirserver removed"
select BR2_LEGACY
help
usbredirserver has been dropped by upstream since version
0.13.0. usbredir tools (which include usbredirect binary) can
be used as a replacement.
package/gdb: remove support for 9.2 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-08-13 10:35:18 +02:00
comment "Legacy options removed in 2022.11"
Config.in.legacy: add missing binutils 2.36.x entry Commit [1] removed binutils 2.36.1 but forgot to add the legacy entry. [1] d08639e6b9e5b687c21c35041bb60a941fc7edb4 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2023-04-29 01:06:17 +02:00
config BR2_BINUTILS_VERSION_2_36_X
bool "binutils 2.36.x has been removed"
select BR2_LEGACY
help
binutils 2.36 has been removed, use a newer version.
package/rabbitmq-server: drop package The packaged version has a number of security issues, newer versions require erlang 23+ and nobody has stepped up to maintain it since the issues were reported: http://lists.busybox.net/pipermail/buildroot/2022-November/656230.html So drop the package and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-12-02 20:15:19 +01:00
config BR2_PACKAGE_RABBITMQ_SERVER
bool "rabbitmq-server removed"
select BR2_LEGACY
help
Package was removed because it was unmaintained and had
known security issues.
package/libopenssl: drop useless option for rc5 Commit a83d41867c8d (package/libopenssl: add option to enable some features) added an option to enable rc5. However, since commit 1fff94121936 (Fixup non-x86 openssl build), dated 2002-12-30, rc5 has always been forcibly disabled in Buildroot. Given that it was unconditionally disabled all this time, and no one complained, it means there is virtually no-one using rc5, so we can just drop the option. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: "GAUTRON, Erwan" <erwan.gautron@bertin.fr> Cc: "Weber, Matthew L Collins" <Matthew.Weber@collins.com> Signed-off-by: Arnout Vandecappelle <arnout@mind.be>
2022-11-05 17:55:23 +01:00
config BR2_PACKAGE_LIBOPENSSL_ENABLE_RC5
bool "libopenssl rc5 was never enabled"
select BR2_LEGACY
help
The libopenssl option for rc5 never actually enabled rc5,
which had always been disabled in Buildroot.
package/libdcadec: remove package Quoting https://github.com/foo86/dcadec "This program is deprecated! This decoder has been fully integrated into FFmpeg master branch and further development will continue there. Using FFmpeg for DTS decoding is now recommended." lbdcadec has had no commit oin the past 7+ years now. Fixes: http://autobuild.buildroot.net/results/1e63586c91a2670ecac2940f6e9840e6801c32f3/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [yann.morin.1998@free.fr: amend commit log with age of last activity] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-11-05 08:51:56 +01:00
config BR2_PACKAGE_LIBDCADEC
bool "package was deprecated upstream, use ffmpeg instead"
select BR2_LEGACY
help
This decoder has been fully integrated into FFmpeg master
branch and further development will continue there. Using
FFmpeg for DTS decoding is now recommended.
package/linux-headers: drop 5.17.x option The 5.17.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-10-04 21:50:34 +02:00
config BR2_KERNEL_HEADERS_5_17
bool "kernel headers version 5.17.x are no longer supported"
select BR2_LEGACY
help
Version 5.17.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
arch/Config.in.arm: drop support for iwmmxt architecture variant This architecture variant is broken in GCC, causing build failures: ../../../libgcc/config/arm/unwind-arm.c:467:1: error: unrecognizable insn: 467 | } | ^ (insn 2 4 3 2 (set (reg/v/f:SI 118 [ p ]) (reg:SI 0 r0 [ p ])) "../../../libgcc/config/arm/unwind-arm.c":456:1 -1 (nil)) during RTL pass: vregs ../../../libgcc/config/arm/unwind-arm.c:467:1: internal compiler error: in extract_insn, at recog.c:2770 Reported to the GCC developers, the feedback was "iwmmxt support is definitely bitrotten and most likely should be removed from GCC.". See: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106972#c1 So this commit simply drops support for iwmmxt, which anyway is probably barely used nowadays: it's for old Marvell PXA cores that implemented a special SIMD instruction set. The BR2_xscale option can be used instead, it's just that it won't use this SIMD instruction set. Fixes: http://autobuild.buildroot.net/results/8e4c4512902c34d8ec0c6f8dfff92b7a198e4b4a/ and the numerous other build failures at: http://autobuild.buildroot.net/?reason=host-gcc-initial%&subarch=iwmmxt Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-25 11:44:03 +02:00
config BR2_iwmmxt
bool "ARM iwmmxt variant removed"
select BR2_LEGACY
help
Support for the ARM iwmmxt architecture variant in GCC has
bitroten and is no longer maintained. GCC maintainers
recommend to no longer use it, and suggest to use "xscale"
as a replacement architecture variant. See
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=106972
package/uhd: bump to version 4.3.0.0 - boost regex is not needed since https://github.com/EttusResearch/uhd/commit/f773cf9fb96e25d064f43cffdc893ac905d91f15 - Drop all patches (already in version) except first one which has been reverted by upstream: https://github.com/EttusResearch/uhd/commit/1a00949b19eaecb84af0f27c370400dc71a9fd84 - Add LGPL-3.0+ for fpga/usrp3: https://github.com/EttusResearch/uhd/commit/bafa9d95453387814ef25e6b6256ba8db2df612f - N230 is not supported since https://github.com/EttusResearch/uhd/commit/d94140a4129d6b2153b15860eeb2406672ebb414 - RFNoC is not supported since https://github.com/EttusResearch/uhd/commit/7d69dcdcc318ccdf87038b732acbf2bf7c087b60 https://github.com/EttusResearch/uhd/blob/v4.3.0.0/CHANGELOG Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-09-25 14:51:09 +02:00
config BR2_PACKAGE_UHD_N230
bool "uhd N230 support removed"
select BR2_LEGACY
help
uhd N230 support has been dropped by upstream since version
4.0.0.0.
config BR2_PACKAGE_UHD_RFNOC
bool "uhd RFNoC support removed"
select BR2_LEGACY
help
uhd RFNoC support has been dropped by upstream since version
4.0.0.0.
package/gpsd: remove obsolete config option The oldstyle option has been removed a while ago now: 2015-02-22 a5a123b4f3b0 Feature removal - delete last remnants of old pre-JSON protocol from libgps. Drop it from Buildroot now. Signed-off-by: Yann E. MORIN <yann.morin@orange.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-09-16 15:06:15 +02:00
config BR2_PACKAGE_GPSD_OLDSTYLE
bool "gpsd oldstyle removed"
select BR2_LEGACY
help
gpsd oldstyle option has been removed by upstream in 2015.
package/gdb: remove support for 9.2 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-08-13 10:35:18 +02:00
config BR2_GDB_VERSION_9_2
bool "gdb 9.2 removed"
Config.in.legacy: add missing select Commit 5c89b00a2052 (package/gdb: remove support for 9.2) forgot to select the legacy symbol when gdb 9.2 was previously enabled. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-09-18 09:46:41 +02:00
select BR2_LEGACY
package/gdb: remove support for 9.2 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-08-13 10:35:18 +02:00
help
Support for GDB 9.2 has been removed. A new version has
automatically been selected.
package/php: remove wddx extension Upstream removed the wddx extension with version 7.4: https://github.com/php/php-src/commit/6bbb18a0b6bef11222caaa55c00abdbcbb55d54b and moved it to pecl: https://pecl.php.net/package/wddx The pecl package is unmaintained however so we do not add it as a new package to buildroot. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-06-11 15:18:42 +02:00
comment "Legacy options removed in 2022.08"
Makefile, docs/manual, support, toolchain: remove Eclipse integration Back many years ago, we developed an Eclipse plugin that simplified the usage of Buildroot toolchains. Enabling the BR2_ECLIPSE_REGISTER=y was registering the Buildroot toolchain into a special file in your HOME folder that the Eclipse plugin would recognize to allow to directly use the Buildroot cross-compiler. This Eclipse plugin has not been maintained for years. The last commit in the repository dates back from September 2017. Since then Eclipse has moved on, and the plugin is no longer compatible with current versions of Eclipse. Also, Eclipse is probably no longer that widely used in the embedded Linux space, as other more modern IDEs have become more popular. All in all, it's time to say good bye to this Eclipse integration. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-07-27 21:05:10 +02:00
config BR2_ECLIPSE_REGISTER
bool "Eclipse integration removed"
select BR2_LEGACY
help
The Buildroot integration with the Eclipse IDE has been
removed, as the corresponding Eclipse plugin is no longer
maintained, and is no longer usable with current versions of
Eclipse.
arch/csky: drop architecture We currently have no internal and no external toolchain for csky. The website is down (no https:// available, and the http:// index page is 404). This commit removes the architecture entry; remnants will be dropped in followup changes. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Guo Ren <ren_guo@c-sky.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-07-27 12:58:04 +02:00
config BR2_csky
bool "csky architecture removed"
select BR2_LEGACY
help
The csky architecture was removed, by lack of toolchain
support.
package/{mesa3d, mesa3d-headers}: bump version to 22.1.3 Release notes for 22.0.x: https://lists.freedesktop.org/archives/mesa-announce/2022-March/000665.html https://lists.freedesktop.org/archives/mesa-announce/2022-March/000667.html https://lists.freedesktop.org/archives/mesa-announce/2022-April/000670.html https://lists.freedesktop.org/archives/mesa-announce/2022-May/000673.html https://www.phoronix.com/scan.php?page=news_item&px=Mesa-22.0-Released Release notes for 22.1.x: https://lists.freedesktop.org/archives/mesa-announce/2022-May/000675.html https://lists.freedesktop.org/archives/mesa-announce/2022-June/000678.html https://lists.freedesktop.org/archives/mesa-announce/2022-June/000681.html https://lists.freedesktop.org/archives/mesa-announce/2022-June/000682.html Removed patch 0006, upstream committed a similar fix: https://cgit.freedesktop.org/mesa/mesa/commit/?h=22.1&id=623ff4ec4295dc67bc0c99ed5336eaae1ad76cc9 While sending upstream the rebased version of patch 0007 it occured that the patched file include/c11_compat.h was removed from the main branch. Instead of keeping care of two different uClibc fixes, both for the 22.1 branch and the main branch, we backport two patches from the main branch: - patch 0007 which removes include/c11_compat.h - patch 0006 which is a pre-requisite of patch 0007 and add an upstreamable patch as 0008. Updated license hash due to upstream commits: https://cgit.freedesktop.org/mesa/mesa/commit/docs/license.rst?h=22.1&id=8bd0446d00dd1aca3cd81ddddc463738aaf3ce61 https://cgit.freedesktop.org/mesa/mesa/commit/docs/license.rst?h=22.1&id=d16263cdee95ec48864ad7a0f90275e8a4fd374b Removed all DRI driver options due to upstream removal of all DRI drivers: https://cgit.freedesktop.org/mesa/mesa/commit/meson_options.txt?h=22.1&id=4d45b280bf9a1c804cea5de4d15c317b6bdebfc5 https://cgit.freedesktop.org/mesa/mesa/commit/meson_options.txt?h=22.1&id=f464871932882003e01e3459c8d126dd975d60f8 https://cgit.freedesktop.org/mesa/mesa/commit/meson_options.txt?h=22.1&id=0cad451f007f366d94e058b7c717b96723a3e6cd https://cgit.freedesktop.org/mesa/mesa/commit/meson_options.txt?h=22.1&id=cdde031ac2c8124721655532ee6f4149e20e9c61 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-07-07 07:12:57 +02:00
config BR2_PACKAGE_MESA3D_DRI_DRIVER_I915
bool "mesa DRI i915 driver removed"
select BR2_LEGACY
help
The DRI i915 driver was removed upstream.
config BR2_PACKAGE_MESA3D_DRI_DRIVER_I965
bool "mesa DRI i965 driver removed"
select BR2_LEGACY
help
The DRI i965 driver was removed upstream.
config BR2_PACKAGE_MESA3D_DRI_DRIVER_NOUVEAU
bool "mesa DRI nouveau driver removed"
select BR2_LEGACY
help
The DRI radeon nouveau was removed upstream.
config BR2_PACKAGE_MESA3D_DRI_DRIVER_RADEON
bool "mesa DRI radeon r100 driver removed"
select BR2_LEGACY
help
The DRI radeon r100 driver was removed upstream.
package/gcc: remove gcc 9.x gcc 12.1 is around, gcc 11.3 is the default version, so drop 9.5 in order to reduce the gcc choice. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-05-29 15:18:11 +02:00
config BR2_GCC_VERSION_9_X
bool "gcc 9.x support removed"
select BR2_LEGACY
help
Support for gcc version 9.x has been removed. The current
default version (11.x or later) has been selected instead.
package/php: remove wddx extension Upstream removed the wddx extension with version 7.4: https://github.com/php/php-src/commit/6bbb18a0b6bef11222caaa55c00abdbcbb55d54b and moved it to pecl: https://pecl.php.net/package/wddx The pecl package is unmaintained however so we do not add it as a new package to buildroot. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-06-11 15:18:42 +02:00
config BR2_PACKAGE_PHP_EXT_WDDX
bool "php wddx removed"
select BR2_LEGACY
help
The WDDX extension was removed from php.
Remove support for the NDS32 architecture The support for this architecture has been removed from the upstream Linux kernel, as of commit: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=aec499c75cf8e0b599be4d559e6922b613085f8f Which states: The nds32 architecture, also known as AndeStar V3, is a custom 32-bit RISC target designed by Andes Technologies. Support was added to the kernel in 2016 as the replacement RISC-V based V5 processors were already announced, and maintained by (current or former) Andes employees. As explained by Alan Kao, new customers are now all using RISC-V, and all known nds32 users are already on longterm stable kernels provided by Andes, with no development work going into mainline support any more. There has also been little to no maintenance done in Buildroot for this architecture in recent times, so let's follow the Linux kernel community decision and drop support for this CPU architecture. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: Yu Chien Peter Lin <peterlin@andestech.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-06-07 22:59:20 +02:00
config BR2_nds32
bool "nds32 architecture removed"
select BR2_LEGACY
help
Support for the nds32 architecture has been removed, due to
its support being removed from the upstream Linux kernel,
and its lack of maintenance in Buildroot.
package/rtl8723bs: drop package Drop package as it doesn't build with latest kernel and project is not maintained anymore: code has been removed in 2017 as driver is available in the linux-next tree (cf. https://github.com/hadess/rtl8723bs/commit/3bb1d33ad98c1d77b5e17a1b707e137b35e6d0a5): In file included from /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/drv_types.h:25, from /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./core/rtw_cmd.c:17: /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/autoconf.h:27:2: error: #error CONFIG_WIRELESS_EXT needs to be enabled for this driver to work 27 | #error CONFIG_WIRELESS_EXT needs to be enabled for this driver to work | ^~~~~ In file included from /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/osdep_service.h:23, from /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/drv_types.h:27, from /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./core/rtw_cmd.c:17: /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/osdep_service_linux.h: In function ‘_init_timer’: /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/osdep_service_linux.h:97:8: error: ‘_timer’ {aka ‘struct timer_list’} has no member named ‘data’ 97 | ptimer->data = (unsigned long)cntx; | ^~ /home/autobuild/autobuild/instance-3/output-1/build/rtl8723bs-11ab92d8ccd71c80f0102828366b14ef6b676fb2/./include/osdep_service_linux.h:98:2: error: implicit declaration of function ‘init_timer’; did you mean ‘_init_timer’? [-Werror=implicit-function-declaration] 98 | init_timer(ptimer); | ^~~~~~~~~~ | _init_timer Fixes: - http://autobuild.buildroot.org/results/7a473e83d4a3d1e2228f4ee1282e85697de4ae5d Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-05-30 23:08:46 +02:00
config BR2_PACKAGE_RTL8723BS
bool "rtl8723bs removed"
select BR2_LEGACY
help
Package was removed because it is not compatible with latest
kernels and is not maintained anymore: code has been removed
in 2017 as driver is available in the linux-next tree.
Config.in.legacy: fix 2022.08 entries Commit 7763ba7007172ceb5e928ae5902735d727aaa90d wrongly added BR2_PACKAGE_RTL8723BS below 2022.05 entry instead of 2022.08 Commit 793ee1011e84bd79fa3d146dbe6c14c7fba39648 wrongly duplicated 2022.08 entry Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-06-20 23:16:06 +02:00
comment "Legacy options removed in 2022.05"
package/ktap: drop package ktap doesn't build with recent kernels (e.g. 5.10.104-cip3 or 5.15.37) and is not maintained anymore (latest release in 2013 and latest commit more than 5 years ago): In file included from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:21: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c:30:6: warning: "CONFIG_EVENT_TRACING" is not defined, evaluates to 0 [-Wundef] 30 | #if !CONFIG_EVENT_TRACING | ^~~~~~~~~~~~~~~~~~~~ /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c:31:2: error: #error "Please enable CONFIG_EVENT_TRACING before compile ktap" 31 | #error "Please enable CONFIG_EVENT_TRACING before compile ktap" | ^~~~~ In file included from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:21: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c: In function ‘gettimeofday_ns’: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c:56:18: error: storage size of ‘now’ isn’t known 56 | struct timespec now; | ^~~ /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c:58:2: error: implicit declaration of function ‘getnstimeofday’; did you mean ‘gettimeofday_ns’? [-Werror=implicit-function-declaration] 58 | getnstimeofday(&now); | ^~~~~~~~~~~~~~ | gettimeofday_ns /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/ktap.c:56:18: warning: unused variable ‘now’ [-Wunused-variable] 56 | struct timespec now; | ^~~ In file included from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:22: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_obj.c: In function ‘kp_obj_kstack2str’: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_obj.c:243:21: error: storage size of ‘trace’ isn’t known 243 | struct stack_trace trace; | ^~~~~ /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_obj.c:253:2: error: implicit declaration of function ‘save_stack_trace’ [-Werror=implicit-function-declaration] 253 | save_stack_trace(&trace); | ^~~~~~~~~~~~~~~~ /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_obj.c:243:21: warning: unused variable ‘trace’ [-Wunused-variable] 243 | struct stack_trace trace; | ^~~~~ In file included from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:27: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_transport.c: In function ‘trace_empty’: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_transport.c:105:39: error: passing argument 1 of ‘ring_buffer_empty_cpu’ from incompatible pointer type [-Werror=incompatible-pointer-types] 105 | if (!ring_buffer_empty_cpu(ktap_iter->buffer, cpu)) | ~~~~~~~~~^~~~~~~~ | | | struct ring_buffer * In file included from ./include/linux/trace_events.h:6, from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/trace_events.h:5, from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_events.h:4, from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_str.c:35, from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:24: ./include/linux/ring_buffer.h:162:49: note: expected ‘struct trace_buffer *’ but argument is of type ‘struct ring_buffer *’ 162 | bool ring_buffer_empty_cpu(struct trace_buffer *buffer, int cpu); | ~~~~~~~~~~~~~~~~~~~~~^~~~~~ In file included from /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/amalg.c:27: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_transport.c: In function ‘trace_consume’: /home/autobuild/autobuild/instance-6/output-1/build/ktap-23bc7a4a94bd9e4e1b8b7c06632e61c041d57b5f/./runtime/kp_transport.c:116:31: error: passing argument 1 of ‘ring_buffer_consume’ from incompatible pointer type [-Werror=incompatible-pointer-types] 116 | ring_buffer_consume(ktap_iter->buffer, iter->cpu, &iter->ts, | ~~~~~~~~~^~~~~~~~ | | | struct ring_buffer * Fixes: - http://autobuild.buildroot.org/results/9067192962b4011e0da27ac2b2dc53eb1e31582c Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-05-19 18:51:49 +02:00
config BR2_PACKAGE_KTAP
bool "ktap removed"
select BR2_LEGACY
help
Package was removed because it is not compatible with latest
kernels and is not maintained anymore (no release since 2013).
package/linux-headers: drop 5.16.x option The 5.16.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-05-13 19:55:39 +02:00
config BR2_KERNEL_HEADERS_5_16
bool "kernel headers version 5.16.x are no longer supported"
select BR2_LEGACY
help
Version 5.16.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop 4.4.x option The 4.4.x series is now EOL upstream, so drop the linux-headers option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-05-04 10:21:56 +02:00
config BR2_KERNEL_HEADERS_4_4
bool "kernel headers version 4.4.x are no longer supported"
select BR2_LEGACY
help
Version 4.4.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/binutils: drop version 2.32 Now that recent versions of binutils work with FLAT binaries, we can drop the old 2.32 version, which was kept only to keep support FLAT binaries. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-04-28 22:55:47 +02:00
config BR2_BINUTILS_VERSION_2_32_X
bool "binutils 2.32.x has been removed"
select BR2_LEGACY
help
binutils 2.32 has been removed, use a newer version.
arch: drop support for SH2A Until commit "arch/Config.in.sh: fixup MMU selection" in this series, SH2A could either be used with BR2_USE_MMU disabled or BR2_USE_MMU enabled. The later made absolutely no sense, since SH2A does not have a MMU: MMU support was introduced starting from SH3 according to https://en.wikipedia.org/wiki/SuperH#SH-3 Also, since commit 22d5501e03b019218b718b5de7ca74824a8eaf42 ("arch: tidy up binary formats config"), which was merged in Buildroot 2015.05, the architecture tuple used when BR2_sh2a=y and BR2_USE_MMU disabled is sh2a-buildroot-uclinux-uclibc, and this was already unsupported back in the days of Buildroot 2015.08 and binutils 2.24, causing the build to fail with: *** BFD does not support target sh2a-buildroot-uclinux-uclibc. just like it fails to build today with recent version of binutils. So, this has been broken since 2015.08, and nobody complained. SH2A is seldom used, so it's time to kill it. It is worth mentioning that there had been an attempt at resurrecting SH2 support around 2015 (see https://lwn.net/Articles/647636/) as part of the J2 core. This effort led to the addition of FDPIC support for SH2A in the musl C library (and therefore proper ELF binaries, with shared libraries), but that was never supported in Buildroot. Now that the J2 project is essentially dead, there is no reason to bother with this. Fixes: http://autobuild.buildroot.net/results/63d01d33ae30f86b63b9f42a9fea116f2f3e9005/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-04-19 23:34:48 +02:00
config BR2_sh2a
bool "sh2a architecture support removed"
select BR2_LEGACY
help
The SuperH 2A (SH2A) architecture was not maintained, and
broken, so its support was dropped.
package/binutils: remove 2.35.2 Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-02-23 18:58:17 +01:00
config BR2_BINUTILS_VERSION_2_35_X
bool "binutils 2.35.x has been removed"
select BR2_LEGACY
help
binutils 2.35 has been removed, use a newer version.
package/boost: drop tagged layout Drop boost tagged layout which raises the following build failure with botan or libcpprestsdk: /nvmedata/autobuild/instance-31/output-1/host/opt/ext-toolchain/bin/../lib/gcc/m68k-buildroot-linux-uclibc/11.2.0/../../../../m68k-buildroot-linux-uclibc/bin/ld: cannot find -lboost_system CMake Error at /usr/share/cmake/Modules/FindPackageHandleStandardArgs.cmake:230 (message): Could NOT find Boost (missing: random system thread filesystem chrono atomic date_time regex) (found version "1.78.0") While at it: - drop BR2_PACKAGE_BOOST_LAYOUT and BR2_PACKAGE_BOOST_LAYOUT_SYSTEM - move --layout=system, --ignore-site-config, --user-config=$(@D)/user-config.jam, -j$(PARALLEL_JOBS), -q and --prefix=$(HOST_DIR) to BOOST_OPTS and HOST_BOOST_OPTS - drop parentheses to avoid spawning a useless sub-shell - use b2 everywhere instead of mixing b2 and tools/build/src/engine/bjam - drop uneeded 'echo "" >> $(@D)/user-config.jam' BR2_PACKAGE_BOOST_LAYOUT_SYSTEM is not added to Config.in.legacy since nothing changes for configs which already had it selected. Fixes: - http://autobuild.buildroot.org/results/f237c9345faf8c28f3c73f7d8acb49271fe61780 - http://autobuild.buildroot.org/results/a73225e40fa29bc3b24f36a86719e80c8e469d1f Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Arnout: don't add BR2_PACKAGE_BOOST_LAYOUT_SYSTEM to Config.in.legacy] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-04-20 14:12:02 +02:00
config BR2_PACKAGE_BOOST_LAYOUT_TAGGED
bool "boost tagged layout removed"
select BR2_LEGACY
help
Boost tagged layout isn't handled by some packages (e.g. botan
or libcpprestsdk).
package/boost: drop versioned layout boost.m4 embedded by cc-tool is not able to find boost libraries when they are versionned (e.g. libboost_program_options-gcc9-mt-sd-1_78.a): configure: error: cannot find the flags to link with Boost program_options azmq and i2pd also have the same issue: CMake Error at /nvmedata/autobuild/instance-8/output-1/host/share/cmake-3.18/Modules/FindPackageHandleStandardArgs.cmake:165 (message): Could NOT find Boost (missing: Boost_INCLUDE_DIR system date_time thread chrono random) (Required is at least version "1.48") So drop versioned layout option Fixes: - http://autobuild.buildroot.org/results/4ae98aed925fbb1d54023075deda9a864f52cee6 - http://autobuild.buildroot.org/results/de35ca0156d4b6f465e440ed9a3effd471f657fa - http://autobuild.buildroot.org/results/c3d2a066429d5f2889c2232d62e5950eb6a89311 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-04-06 19:29:34 +02:00
config BR2_PACKAGE_BOOST_LAYOUT_VERSIONED
bool "boost versioned layout removed"
select BR2_LEGACY
help
Boost versioned layout isn't handled by a number of autotools
and cmake packages (e.g. azmq, cc-tool, i2pd).
package/libmediaart: bump to version 1.9.5 - Switch to meson-package - Drop BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE which is not supported anymore - Update indentation in hash file (two spaces) https://gitlab.gnome.org/GNOME/libmediaart/-/blob/1.9.5/NEWS Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-10-26 21:56:01 +02:00
comment "Legacy options removed in 2022.02"
fs/oci: entrypoint and command are space-separated lists The prompt and variable name for the OCI "entrypoint arguments" are somewhat incorrect. Indeed, they are in fact used to set the image "command". Yet, using "command" would be confusing too, because the interplay between entrypoint and command is tricky [0]. TL-DR; when both entrrypoint and command are set, command acts as arguments passed to the entrypoint. Additionally, we currently can only pass a single item as either entrypoint or command. This precludes passing actual arguments to the entrypoint, or passing multiple arguments as command. For example: BR2_TARGET_ROOTFS_OCI_ENTRYPOINT="/bin/tini -g -p SIGTERM --" BR2_TARGET_ROOTFS_OCI_ENTRYPOINT_ARGS="/usr/bin/env sh" generates an images with (only relevant fields are included below): { "config": { "Entrypoint": [ "/bin/tini -g -p SIGTERM --" ], "Cmd": [ "/usr/bin/env sh" ] } } This is obviously incorrect, and not what one would expect: { "config": { "Entrypoint": [ "/bin/tini", "-g", "-p", "SIGTERM", "--" ], "Cmd": [ "/usr/bin/env", "sh" ] } } However, some people do want to be able to pass an actual shell scriptlet as a command, such as: { "config": { "Entrypoint": [ "/bin/sh", "-c" ], "Cmd": [ "my shell logic goes here" ] } } Handling both is obviously conflicting: we can't both split-on-spaces and not-split-on-spaces at the same time... So, we fix that in two ways: - make the current _OCI_ENTRYPOINT_ARGS a legacy option, and introduce the new _OCI_CMD option with different semantics (see below) and an appropriate prompt; - we interpret both _OCI_ENTRYPOINT and _OCI_CMD as shell strings, which we subject to the usual shell quoting [1] and token recognition [2]; Since _OCI_ENTRYPOINT_ARGS used to be interpreted as a single string, we can't easily change its meaning to be a space-separated list, as that would break existing setups, which is the reason we make it legacy and introduce a new option. Ideally, we would like to default the new option _OCI_CMD to be the quoted value of the previous _OCI_ENTRYPOINT_ARGS, but this is not possible in Kconfig. Still, users that had a _OCI_ENTRYPOINT_ARGS set will now get an early build error, and can still detect they need to do something about it. As for _OCI_ENTRYPOINT, it does not make much sense to support both cases. Indeed, without splitting on spaces, we'd end up with an entrypoint that would have a single item: { "config": { "entrypoint: [ "some string with some spaces" ] } } which in this case would try to execute the program which name is actually "some string with some spaces", so we do not expect that existing entrypoints are set with any space in them, and so the new behaviour, unlike for _OCI_ENTRYPOINT_ARGS vs. _OCI_CMD, is compatible with existing configurations, and so we do not need to make it a legacy option and introduce a new one. [0] https://docs.docker.com/engine/reference/builder/#understand-how-cmd-and-entrypoint-interact [1] https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_02 [2] https://pubs.opengroup.org/onlinepubs/9699919799/utilities/V3_chap02.html#tag_18_03 Signed-off-by: Yann E. MORIN <yann.morin@orange.com> Cc: Sergio Prado <sergio.prado@e-labworks.com> Cc: Matthew Weber <matthew.weber@collins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-05-13 15:17:45 +02:00
config BR2_TARGET_ROOTFS_OCI_ENTRYPOINT_ARGS
string "entrypoint argumetns has been changed as command"
help
The OCI image BR2_TARGET_ROOTFS_OCI_ENTRYPOINT_ARGS option
has been renamed to BR2_TARGET_ROOTFS_OCI_CMD to better
reflect its relation to the actual 'command' of the OCI
image.
The new semantic for BR2_TARGET_ROOTFS_OCI_CMD is slightly
differnt in relation to how it is interpreted, so be sure to
review the help entry for it.
Due to this breaking change, the old value here could not be
set to the new variable.
config BR2_TARGET_ROOTFS_OCI_ENTRYPOINT_ARGS_WRAP
bool
default y if BR2_TARGET_ROOTFS_OCI_ENTRYPOINT_ARGS != ""
select BR2_LEGACY
package/libcurl: bump version to 7.82.0 Changelog: https://curl.se/changes.html Updated license hash due to copyright year bump: https://github.com/curl/curl/commit/0409192b1fde6b7a4f09667e80ca5dc555eab3f1 The NSS crypto backend requires a special option now, without it configure errors out with: configure: error: NSS use must be confirmed using --with-nss-deprecated. NSS support will be dropped from curl in August 2022. See docs/DEPRECATE.md Since it will be removed entirely soon anyway, and since this version doesn't fix any CVEs so doesn't need to be backported to stable branches, drop the NSS option entirely. Since NSS is going to be removed soon, drop the --without-nss as well. It is never going to be enabled automatically. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Arnout: drop NSS option entirely, as suggested by Baruch Siach.] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-03-13 14:04:24 +01:00
config BR2_PACKAGE_LIBCURL_LIBNSS
bool "libcurl NSS removed"
select BR2_LEGACY
help
NSS was deprecated in libcurl 7.82.0.
package/weston: drop fbdev fbdev raises the following build failure since bump to version 10.0.0 in commit f67a6e9b7a7be9adbc405b3126000056120a01af and https://gitlab.freedesktop.org/wayland/weston/-/commit/6338dbd5816689b2f08f48b359a972e16ff038d8: ../output-1/build/weston-10.0.0/meson.build:133:7: ERROR: Tried to access unknown option 'backend-fbdev'. Drop fbdev to avoid this build failure as upstream is reluctant to properly fix this issue by renaming the fbdev option in stable release: https://gitlab.freedesktop.org/wayland/weston/-/merge_requests/791 Fixes: - http://autobuild.buildroot.org/results/e669a6237c19783c627169c819d7372e20daaf54 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-02-14 20:39:40 +01:00
config BR2_PACKAGE_WESTON_DEFAULT_FBDEV
bool "weston fbdev removed"
select BR2_LEGACY
help
fbdev was deprecated in weston 10.0.0.
config BR2_PACKAGE_WESTON_FBDEV
bool "weston fbdev compositor removed"
select BR2_LEGACY
help
fbdev compositor was deprecated in weston 10.0.0.
package/python-pycli: drop package Even with the two upstream patches added in commit b2e6e376a2d7551ccf146855ec4e99a65c35bd16, python-pycli still raises the following build failure since bump of python3 to version 3.10.1 in commit 25b1fc2898d68ddf2674b14c738045875fc5a2dc due to the new "Multiple Exception types without parentheses" exception (https://docs.python.org/3/whatsnew/3.10.html): error: File "/usr/lib/python3.10/site-packages/cli/test.py", line 142 except raises, e: ^^^^^^^^^ SyntaxError: multiple exception types must be parenthesized So drop the package as the last release was made 10 years ago. Fixes: - http://autobuild.buildroot.org/results/6112e1830ce608abcea4a26b659c10e5ff09a66a Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-02-22 18:49:57 +01:00
config BR2_PACKAGE_PYTHON_PYCLI
bool "python-pycli removed"
select BR2_LEGACY
help
Package was removed because it is not compatible with python
3.10 and is not maintained anymore (no release since 2012).
package/bpftool: new package Move the target bpftool build out of linux-tools so that it is up to date. This also fixes build issues due to differences between kernel versions. The latest version should be fully backwards compatible. The host bpftool is needed for enabling features such as the systemd bpf-framework (to be added in a future patch). Use the git download method to get the libbpf submodule. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-01-31 19:51:54 +01:00
config BR2_PACKAGE_LINUX_TOOLS_BPFTOOL
bool "bpftool was moved"
select BR2_LEGACY
select BR2_PACKAGE_BPFTOOL
help
The linux-tools bpftool build has been moved out
of the linux-tools package.
boot/uboot: drop host-python2 support host-python2 is gone, so drop the _NEEDS_PYTHON2 logic. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-02-11 09:17:26 +01:00
config BR2_TARGET_UBOOT_NEEDS_PYTHON2
bool "host-python 2.7 support for U-Boot was removed"
select BR2_LEGACY
help
Option was removed together with python 2.7 support.
package/gst1-plugins-bad: bump version to 1.20.0 - removed 0001-neon-Allow-building-against-neon-0-32-x.patch (from upstream [1]) - add codecalpha option (VP8/VP9 alpha support) - add qroverlay option (overlay data on top of video in the form of a QR code) with json-glib and libqrencode dependencies (omit json-glib explicit dependencies as they are the same as for gstreamer1, glib2 BR2_USE_WCHAR, BR2_TOOLCHAIN_HAS_THREADS and BR2_USE_MMU), place instead to 'plugins without external deps' section into 'plugins that need external deps' section as it clearly has dependencies (prelimary to upstream commit [2]) - add aes option (AES encryption/decryption plugin) - disable new option asio (Steinberg Audio Streaming, windows only) - disable new option gs (Google Cloud Storage, needs storage_client library) - disable new option ldac (LDAC bluetooth audio codec, needs ldacBT-enc library) - remove legacy option ofa (disabled) - disable new option onnx (ONNX neural network, needs libonnxruntime library) - disable new option isac (iSAC plugin, needs webrtc-audio-coding-1 library) - removed libmms ('Microsoft Multi Media Server streaming protocol' option, add Config.in.legacy entry - enable new gpl option ('Allow build plugins that have (A)GPL-licensed dependencies') in case gpl plugin enabled [1] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/b83e85ab677c79b46f520abebd1ee031e3a139c0.patch [2] https://gitlab.freedesktop.org/gstreamer/gstreamer/-/commit/5d70c168b356691073a0d22f7ce3ea7efb20641c.patch Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-02-10 20:28:56 +01:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_LIBMMS
bool "gst1-plugins-bad plugin libmms was removed"
depends on BR2_USE_WCHAR
depends on BR2_TOOLCHAIN_HAS_THREADS
select BR2_LEGACY
help
This plugin was removed with gst1-plugins-bad-1.20.0.
package/python-functools32: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:12 +01:00
config BR2_PACKAGE_PYTHON_FUNCTOOLS32
bool "python-functools32 removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-enum34: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:11 +01:00
config BR2_PACKAGE_PYTHON_ENUM34
bool "python-enum34 removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-enum: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:10 +01:00
config BR2_PACKAGE_PYTHON_ENUM
bool "python-enum removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-dialog: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:09 +01:00
config BR2_PACKAGE_PYTHON_DIALOG
bool "python-dialog removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-configobj: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:08 +01:00
config BR2_PACKAGE_PYTHON_CONFIGOBJ
bool "python-configobj removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-yieldfrom: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:07 +01:00
config BR2_PACKAGE_PYTHON_YIELDFROM
bool "python-yieldfrom removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-typing: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:06 +01:00
config BR2_PACKAGE_PYTHON_TYPING
bool "python-typing removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-subprocess32: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:05 +01:00
config BR2_PACKAGE_PYTHON_SUBPROCESS32
bool "python-subprocess32 removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-singledispatch: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:04 +01:00
config BR2_PACKAGE_PYTHON_SINGLEDISPATCH
bool "python-singledispatch removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-pyro: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:03 +01:00
config BR2_PACKAGE_PYTHON_PYRO
bool "python-pyro removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-pypcap: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:02 +01:00
config BR2_PACKAGE_PYTHON_PYPCAP
bool "python-pypcap removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-pathlib2: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:01 +01:00
config BR2_PACKAGE_PYTHON_PATHLIB2
bool "python-pathlib2 removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-pam: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:52:00 +01:00
config BR2_PACKAGE_PYTHON_PAM
bool "python-pam removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-nfc: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:59 +01:00
config BR2_PACKAGE_PYTHON_NFC
bool "python-nfc removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-mad: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:58 +01:00
config BR2_PACKAGE_PYTHON_MAD
bool "python-mad removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-ipaddress: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:57 +01:00
config BR2_PACKAGE_PYTHON_IPADDRESS
bool "python-ipaddress removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-ipaddr: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:56 +01:00
config BR2_PACKAGE_PYTHON_IPADDR
bool "python-ipaddr removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-id3: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:55 +01:00
config BR2_PACKAGE_PYTHON_ID3
bool "python-id3 removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-futures: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:54 +01:00
config BR2_PACKAGE_PYTHON_FUTURES
bool "python-futures removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-backports-ssl-match-hostname: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:53 +01:00
config BR2_PACKAGE_PYTHON_BACKPORTS_SSL_MATCH_HOSTNAME
bool "python-backports-ssl-match-hostname removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-backports-shutil-get-terminal-size: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:52 +01:00
config BR2_PACKAGE_PYTHON_BACKPORTS_SHUTIL_GET_TERMINAL_SIZE
bool "python-backports-shutil-get-terminal-size removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python-backports-abc: drop python2 specific package Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:51:51 +01:00
config BR2_PACKAGE_PYTHON_BACKPORTS_ABC
bool "python-backports-abc removed"
select BR2_LEGACY
help
Package was removed together with python 2.7 support.
package/python: drop target package Python 2.7 is EOL since April 2020, so drop support for the target package. https://www.python.org/dev/peps/pep-0373/ Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-02-09 17:50:28 +01:00
config BR2_PACKAGE_PYTHON
bool "python2.7 package removed"
select BR2_LEGACY
help
Python 2.7 is EOL since April 2020 and has been removed.
https://www.python.org/dev/peps/pep-0373/
package/zynq-boot-bin: drop legacy package Since commit 6dd5a33c485c (zynq_zed: bump U-Boot to xilinx-v2016.2), we have no in-tree users of zynq-boot-bin.py, as U-Boot has since v2016.01 been able to natively generate Xilinx images. zynq-boot-bin.py is python2-only and there is zero chance that upstream will move it to python3. We could carry a python3-compatible copy, but that tool is now virtually unused. 6 years have passed now; let it rest in peace at last. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: James Hilliard <james.hilliard1@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Masahiro Yamada <yamada.masahiro@socionext.com> Cc: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2022-01-11 22:17:08 +01:00
config BR2_TARGET_UBOOT_ZYNQ_IMAGE
bool "Generate image for Xilinx Zynq"
select BR2_LEGACY
help
Since 2016.1, U-Boot can natively generate the Zynq boot
image, and so the Xilinx-specific format and tools have been
removed. Should you still have an older U-Boot that needs
this, a python3 version of the zynq-boot-bin.py script can be
downloaded from the URL below and called from a post-build
script.
https://gist.githubusercontent.com/jameshilliard/e09235dfc6f96c11418a134e6ebf7890/raw/135b7480c405ae8a77a9db615e495f9a9f2d3242/zynq-boot-bin.py
package/brcmfmac_sdio-firmware-rpi: merge of rpi-{bt,wifi}-firmware Move rpi-bt-firmware and rpi-wifi-firmware packages to the new brcmfmac_sdio-firmware-rpi one (as they are the same upstream package). Signed-off-by: Peter Seiderer <ps.report@gmx.net> [yann.morin.1998@free.fr: - fix check-package - legacy symbols still depend on arm || aarch64 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-18 22:14:34 +01:00
config BR2_PACKAGE_RPI_BT_FIRMWARE
bool "rpi-bt-firmware package was renamed"
depends on BR2_arm || BR2_aarch64
select BR2_LEGACY
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_BT
help
Package rpi-bt-firmware was moved as option to
Config.in.legacy: fix typo Fix typo added by commit 7527324132878f98999539bdd97bd3518747f585: brcmfmac-sdio-firmware-rpi by brcmfmac_sdio-firmware-rpi Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-22 22:43:18 +01:00
package brcmfmac_sdio-firmware-rpi.
package/brcmfmac_sdio-firmware-rpi: merge of rpi-{bt,wifi}-firmware Move rpi-bt-firmware and rpi-wifi-firmware packages to the new brcmfmac_sdio-firmware-rpi one (as they are the same upstream package). Signed-off-by: Peter Seiderer <ps.report@gmx.net> [yann.morin.1998@free.fr: - fix check-package - legacy symbols still depend on arm || aarch64 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-18 22:14:34 +01:00
config BR2_PACKAGE_RPI_WIFI_FIRMWARE
bool "rpi-wifi-firmware package was renamed"
depends on BR2_arm || BR2_aarch64
select BR2_LEGACY
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI
select BR2_PACKAGE_BRCMFMAC_SDIO_FIRMWARE_RPI_WIFI
help
Package rpi-wifi-firmware was moved as option to
Config.in.legacy: fix typo Fix typo added by commit 7527324132878f98999539bdd97bd3518747f585: brcmfmac-sdio-firmware-rpi by brcmfmac_sdio-firmware-rpi Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-22 22:43:18 +01:00
package brcmfmac_sdio-firmware-rpi.
package/brcmfmac_sdio-firmware-rpi: merge of rpi-{bt,wifi}-firmware Move rpi-bt-firmware and rpi-wifi-firmware packages to the new brcmfmac_sdio-firmware-rpi one (as they are the same upstream package). Signed-off-by: Peter Seiderer <ps.report@gmx.net> [yann.morin.1998@free.fr: - fix check-package - legacy symbols still depend on arm || aarch64 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-18 22:14:34 +01:00
package/gdb: remove python2 support Since at least gdb 7.8, python3 support has been available. As part of the progressive retiring of python2 support, it is time to drop its support in gdb by: - Removing BR2_PACKAGE_HOST_GDB_PYTHON in package/gdb/Config.in.host and removing the choice to leave just a BR2_PACKAGE_HOST_GDB_PYTHON3 option. - Adding BR2_PACKAGE_HOST_GDB_PYTHON to Config.in.legacy - Changing depends on BR2_PACKAGE_PYTHON || BR2_PACKAGE_PYTHON3 to depends on BR2_PACKAGE_PYTHON3 in package/gdb/Config.in Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-04 21:09:04 +01:00
config BR2_PACKAGE_HOST_GDB_PYTHON
bool "GDB Python2 support removed"
select BR2_LEGACY
help
Python2 is deprecated and no longer supported.
Please migrate to Python3.
package/gstreamer1/gstreamer1-mm: drop package gstreamer1-mm is not compatible with glibmm-2.68 API and not actively maintained anymore (one commit during the last 3 years): https://gitlab.gnome.org/GNOME/gstreamermm/-/issues/17 https://gitlab.gnome.org/GNOME/gstreamermm/-/commits/master As this is the only package that doesn't support glibmm-2.68 and because it can't be easily patched, drop it to avoid the following build failure raised since commit dddb65efbdf2c7952f22a1e51009f17f1676db4a: Package 'giomm-2.4', required by 'virtual:world', not found Fixes: - http://autobuild.buildroot.org/results/3479688334765fbbe4cb9620f4d3596f7d710404 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-01-11 18:43:45 +01:00
config BR2_PACKAGE_GSTREAMER1_MM
bool "gstreamer1-mm package removed"
select BR2_LEGACY
help
This package has been removed as it is not actively
maintained anymore and does not support glibmm-2.68 API.
package/linux-headers: drop 5.14.x headers The 5.14.x series is now EOL, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> [yann.morin.1998@free.fr: actualyl drop it from the choice list] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-11 00:13:01 +01:00
config BR2_KERNEL_HEADERS_5_14
bool "kernel headers version 5.14.x are no longer supported"
select BR2_LEGACY
help
Version 5.14.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/python-setuptools-scm: needs python3 python-setuptools-scm dropped python 2 support since https://github.com/pypa/setuptools_scm/commit/f0be71fbcf150bfc68e4169226399d6ae4da8f1b resulting in the following build failure since bump to version 6.3.2 in commit 12e3527fd97df9ae1b60b892c61d10ce291b7a00: /buildroot/autobuild/instance-2/output-1/host/lib" INTLTOOL_PERL=/usr/bin/perl /home/buildroot/autobuild/instance-2/output-1/host/bin/python setup.py build ) File "setup.py", line 22 f"{type(self).__name__} is forbidden, " ^ Fixes: - http://autobuild.buildroot.org/results/2f6125993de364b4a44d259f16806e6dfd792402 With python 2 support dropped, python-backports-functools-lru-cache can no longer be built, so drop it. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-01-09 13:43:35 +01:00
config BR2_PACKAGE_PYTHON_BACKPORTS_FUNCTOOLS_LRU_CACHE
bool "python-backports-functools-lru-cache package removed"
select BR2_LEGACY
help
This package has been removed as python-setuptools-scm
dropped support of python 2 since version 6.0.0.
package/civetweb: drop BR2_PACKAGE_CIVETWEB_WITH_LUA Drop BR2_PACKAGE_CIVETWEB_WITH_LUA and enable Lua support depending on BR2_PACKAGE_LUA and BR2_PACKAGE_LUAJIT It should be noted that civetweb will still use its embedded version of sqlite Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [Peter: add !BR2_STATIC_LIBS, pass LUA_SHARED_LIB_FLAG, explicitly link with -ldl, rework order] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-04 08:43:11 +01:00
config BR2_PACKAGE_CIVETWEB_WITH_LUA
bool "civetweb lua support option removed"
select BR2_LEGACY
help
Lua support does not depend on a version of Lua bundled
within the Civetweb sources anymore. Lua support is
automatically enabled if an Lua interpreter (lua or luajit)
is enabled in Buildroot.
package/sunxi-mali-utgard-driver: rename from sunxi-mali-mainline-driver This package provides a Mali kernel driver for Sunxi Mali Utgard GPUs. The trailing -mainline is historical and was used at a time when there was two packages providing this driver. The "non-upstream" package has been removed some time ago so before adding new packages bringing support for other ARM Mali GPU versions or implementations, rename sunxi-mali-mainline-driver into sunxi-mali-utgard-driver. Add a legacy entry. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> [Giulio: rebase on master. Add legacy entry instead of substituting the blob's one] Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 23:17:57 +01:00
config BR2_PACKAGE_SUNXI_MALI_MAINLINE_DRIVER
bool "sunxi-mali-mainline-driver package was renamed"
select BR2_LEGACY
select BR2_PACKAGE_SUNXI_MALI_UTGARD_DRIVER
help
Since the removal of the sunxi-mali-driver package, the
sunxi-mali-mainline-driver package that coexisted became the
only package to provide the Sunxi Mali driver. The "-mainline"
suffix being undescriptive nowadays and before adding new
packages bringing Mali support for other SoCs/GPU flavors, it
is clearer to rename it SUNXI_MALI_UTGARD_DRIVER.
package/sunxi-mali-utgard: rename from sunxi-mali-mainline This package provides Mali libraries for Sunxi Mali Utgard GPUs. The trailing -mainline is historical and was used at a time when there was two packages providing these libraries. The "non-upstream" package has been removed some time ago so before adding new packages bringing support for other ARM Mali GPU versions or implementations, rename sunxi-mali-mainline into sunxi-mali-utgard. Add a legacy entry. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> [Giulio: rebase on master. Rename SUNXI_MALI_MAINLINE_REV to SUNXI_MALI_UTGARD_REV in sunxi-mali-mailine-driver.mk and BR2_PACKAGE_SUNXI_MALI_MAINLINE to BR2_PACKAGE_SUNXI_UTGARD in sunxi-mali-mainline-driver/Config.in to respect bisectability] Tested-by: Luca Ceresoli <luca@lucaceresoli.net> [Build tested only] Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> [Arnout: also update existing select in Config.in.legacy] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 23:17:56 +01:00
config BR2_PACKAGE_SUNXI_MALI_MAINLINE
bool "sunxi-mali-mainline package was renamed"
select BR2_LEGACY
select BR2_PACKAGE_SUNXI_MALI_UTGARD
help
Since the removal of the sunxi-mali package, the
sunxi-mali-mainline package that coexisted became the only
package to provide Mali blobs. The "-mainline" suffix being
undescriptive nowadays and before adding new packages bringing
Mali support for other SoCs/GPU flavors, it is clearer to
rename it SUNXI_MALI_UTGARD.
config BR2_PACKAGE_SUNXI_MALI_MAINLINE_R6P2
bool "sunxi-mali-mainline-r6p2 was renamed"
select BR2_LEGACY
help
The sunxi-mali-mainline package has been renamed
sunxi-mali-utgard, the suboptions of this package have also
been renamed accordingly.
package/sunxi-mali-utgard: properly handle legacy for renamed options Commit "6a7a652b14 package/sunxi-mali-utgard: rename from sunxi-mali-mainline" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2022.02, following the example described in the beginning of the file. Cc: Giulio Benetti <giulio.benetti@benettiengineering.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:37 +01:00
# Note: BR2_PACKAGE_SUNXI_MALI_MAINLINE_R6P2 is still referenced from
# package/sunxi-mali-utgard/Config.in
package/sunxi-mali-utgard: rename from sunxi-mali-mainline This package provides Mali libraries for Sunxi Mali Utgard GPUs. The trailing -mainline is historical and was used at a time when there was two packages providing these libraries. The "non-upstream" package has been removed some time ago so before adding new packages bringing support for other ARM Mali GPU versions or implementations, rename sunxi-mali-mainline into sunxi-mali-utgard. Add a legacy entry. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> [Giulio: rebase on master. Rename SUNXI_MALI_MAINLINE_REV to SUNXI_MALI_UTGARD_REV in sunxi-mali-mailine-driver.mk and BR2_PACKAGE_SUNXI_MALI_MAINLINE to BR2_PACKAGE_SUNXI_UTGARD in sunxi-mali-mainline-driver/Config.in to respect bisectability] Tested-by: Luca Ceresoli <luca@lucaceresoli.net> [Build tested only] Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> [Arnout: also update existing select in Config.in.legacy] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 23:17:56 +01:00
config BR2_PACKAGE_SUNXI_MALI_MAINLINE_R8P1
bool "sunxi-mali-mainline-r8p1 was renamed"
select BR2_LEGACY
help
The sunxi-mali-mainline package has been renamed
sunxi-mali-utgard, the suboptions of this package have also
been renamed accordingly.
package/sunxi-mali-utgard: properly handle legacy for renamed options Commit "6a7a652b14 package/sunxi-mali-utgard: rename from sunxi-mali-mainline" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2022.02, following the example described in the beginning of the file. Cc: Giulio Benetti <giulio.benetti@benettiengineering.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:37 +01:00
# Note: BR2_PACKAGE_SUNXI_MALI_MAINLINE_R8P1 is still referenced from
# package/sunxi-mali-utgard/Config.in
package/sunxi-mali-utgard: rename from sunxi-mali-mainline This package provides Mali libraries for Sunxi Mali Utgard GPUs. The trailing -mainline is historical and was used at a time when there was two packages providing these libraries. The "non-upstream" package has been removed some time ago so before adding new packages bringing support for other ARM Mali GPU versions or implementations, rename sunxi-mali-mainline into sunxi-mali-utgard. Add a legacy entry. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> [Giulio: rebase on master. Rename SUNXI_MALI_MAINLINE_REV to SUNXI_MALI_UTGARD_REV in sunxi-mali-mailine-driver.mk and BR2_PACKAGE_SUNXI_MALI_MAINLINE to BR2_PACKAGE_SUNXI_UTGARD in sunxi-mali-mainline-driver/Config.in to respect bisectability] Tested-by: Luca Ceresoli <luca@lucaceresoli.net> [Build tested only] Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> [Arnout: also update existing select in Config.in.legacy] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 23:17:56 +01:00
package/qt5/qt5webkit-examples: remove package This package seems to have issues building with the latest qt5webkit release, as it has not received updates upstream since 2017 remove it as it is unlikely to be fixed. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-06 07:33:08 +01:00
config BR2_PACKAGE_QT5WEBKIT_EXAMPLES
bool "qt5webkit-examples removed"
select BR2_LEGACY
help
The qt5webkit-examples package is unmaintained and has been
removed.
toolchain: re-generate Bootlin toolchain descriptions Following the releases of 2021.11 Bootlin toolchains, this commit represents the result of re-running the gen-bootlin-toolchains script. The only part that isn't auto-generated are the contents of Config.in.legacy, which account for the replacement of the RISC-V LP64 toolchain by RISC-V LP64D toolchains. The complete set of runtime test cases was verified on Gitlab CI: https://gitlab.com/tpetazzoni/buildroot/-/pipelines/437767674 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-12-28 10:15:41 +01:00
config BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_BLEEDING_EDGE
bool "Bootlin riscv64 glibc bleeding-edge toolchain removed"
select BR2_LEGACY
help
The RISC-V 64-bit LP64 Bootlin toolchains have been removed,
in favor of RISC-V 64-bit LP64D toolchains.
Config.in.legacy: fix removed bootlin riscv64 toolchains commit b3c66481e1f1503fcbf193d0c780271e880ad500 replaced RISC-V LP64 bootlin toolchains by RISC-V LP64D. However, Config.in.legacy was added for BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_GLIBC_STABLE, which never existed (the stable version was only added after the switch to LP64D). Conversely, BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_MUSL_BLEEDING_EDGE, which was removed, was not mentioned in Config.in.legacy. Correct the symbol name and its comment in Config.in.legacy. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2022-01-04 18:11:28 +01:00
config BR2_TOOLCHAIN_EXTERNAL_BOOTLIN_RISCV64_MUSL_BLEEDING_EDGE
bool "Bootlin riscv64 musl bleeding-edge toolchain removed"
toolchain: re-generate Bootlin toolchain descriptions Following the releases of 2021.11 Bootlin toolchains, this commit represents the result of re-running the gen-bootlin-toolchains script. The only part that isn't auto-generated are the contents of Config.in.legacy, which account for the replacement of the RISC-V LP64 toolchain by RISC-V LP64D toolchains. The complete set of runtime test cases was verified on Gitlab CI: https://gitlab.com/tpetazzoni/buildroot/-/pipelines/437767674 Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-12-28 10:15:41 +01:00
select BR2_LEGACY
help
The RISC-V 64-bit LP64 Bootlin toolchains have been removed,
in favor of RISC-V 64-bit LP64D toolchains.
package/iputils: bump version to 20211215 tftp and traceroute6 has been removed in this release [1][2]. Due that LICENSE file has been changed. Also remove patch from this release. [1] https://github.com/iputils/iputils/pull/369 [2] https://github.com/iputils/iputils/pull/362 Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-15 23:11:52 +01:00
config BR2_PACKAGE_IPUTILS_TFTPD
Config.in.legacy: improve iputils options Improve iputils options added by commit db0c2a287970a8832b59f3cf9d81aa18aced2cec Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-16 23:08:40 +01:00
bool "iputils tftpd option removed"
package/iputils: bump version to 20211215 tftp and traceroute6 has been removed in this release [1][2]. Due that LICENSE file has been changed. Also remove patch from this release. [1] https://github.com/iputils/iputils/pull/369 [2] https://github.com/iputils/iputils/pull/362 Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-15 23:11:52 +01:00
select BR2_LEGACY
help
Config.in.legacy: improve iputils options Improve iputils options added by commit db0c2a287970a8832b59f3cf9d81aa18aced2cec Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-16 23:08:40 +01:00
tftpd has been removed from iputils since version 20211215.
package/iputils: bump version to 20211215 tftp and traceroute6 has been removed in this release [1][2]. Due that LICENSE file has been changed. Also remove patch from this release. [1] https://github.com/iputils/iputils/pull/369 [2] https://github.com/iputils/iputils/pull/362 Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-15 23:11:52 +01:00
config BR2_PACKAGE_IPUTILS_TRACEROUTE6
Config.in.legacy: improve iputils options Improve iputils options added by commit db0c2a287970a8832b59f3cf9d81aa18aced2cec Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-16 23:08:40 +01:00
bool "iputils traceroute6 option removed"
package/iputils: bump version to 20211215 tftp and traceroute6 has been removed in this release [1][2]. Due that LICENSE file has been changed. Also remove patch from this release. [1] https://github.com/iputils/iputils/pull/369 [2] https://github.com/iputils/iputils/pull/362 Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-15 23:11:52 +01:00
select BR2_LEGACY
help
Config.in.legacy: improve iputils options Improve iputils options added by commit db0c2a287970a8832b59f3cf9d81aa18aced2cec Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-16 23:08:40 +01:00
traceroute6 has been removed from iputils since version
20211215.
package/iputils: bump version to 20211215 tftp and traceroute6 has been removed in this release [1][2]. Due that LICENSE file has been changed. Also remove patch from this release. [1] https://github.com/iputils/iputils/pull/369 [2] https://github.com/iputils/iputils/pull/362 Signed-off-by: Petr Vorel <petr.vorel@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-12-15 23:11:52 +01:00
package/libmediaart: bump to version 1.9.5 - Switch to meson-package - Drop BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE which is not supported anymore - Update indentation in hash file (two spaces) https://gitlab.gnome.org/GNOME/libmediaart/-/blob/1.9.5/NEWS Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-10-26 21:56:01 +02:00
config BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE
bool "libmediaart 'none' backend removed"
select BR2_LEGACY
help
'none' backend has been removed from libmediaart since version
1.9.5.
package/mpd: update to version 0.23.y This version adds support for openmpt, pipewire and snapcast, which are disabled for now. It also adds support for a choice between pupnp and npupnp for the UPnP database. Therefore, the UPNP option is converted into three-value choice in Config.in. Legacy handling of the BR2_PACKAGE_MPD_UPNP makes sure that upnp remains selected. Signed-off-by: Andreas Ziegler <br015@umbiko.net> [Arnout: fix legacy handling; fix snapcast option] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-15 13:32:12 +01:00
config BR2_PACKAGE_MPD_UPNP
bool "MPD UPnP configuration changed"
select BR2_LEGACY
help
From version 0.23, MPD supports npupnp in addition to pupnp to
provide database access to a UPnP media server. To preserve
the existing functionality, the pupnp option has been selected
in the MPD UPnP configuration.
# Note: BR2_PACKAGE_MPD_UPNP is still referenced from package/mpd/Config.in
package/gnuradio: drop gr-pager (gr-flex) option gr-pager (labeled 'gr-flex' in our menuconfig) is not available since bump to version 3.8.0.0 in commit 0d6a7b2981d4 (package/gnuradio: bump to version 3.8.0.0) and upstream commit: https://github.com/gnuradio/gnuradio/commit/2d2caa205f3c3059deab7c82660908656167fd90 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-10 08:53:05 +02:00
comment "Legacy options removed in 2021.11"
package/openjdk{-bin}: bump version to 17.0.1+12 OpenJDK 17 is a new LTS release, which leaves the Buildroot Config option of "LTS" and "LATEST" as a misnomer because both 11 and 17 are LTS releases. There are two options in this case: 1) Remove "LATEST" and update OpenJDK 11 to 17, and only support 17. 2) Change "LTS" to "11" and "LATEST" to "17" and only support the latest 2 LTS OpenJDK releases. After some discussion with Thomas Petazzoni and Peter Korsgaard, and testing, option 2 is the best course of action for a few reasons: - OpenJDK 11 and 17 have very long support cycles: - OpenJDK 11 has two years of Active and five years of security support left. - OpenJDK 17 has five years of Active and ten years of security support left. - Both OpenJDK versions build with the same parameters. - The maintenance cost of both versions is meager. - Both versions pass tests.package.test_openjdk without issue. Changes: - Change BR2_OPENJDK_VERSION_LATEST -> BR2_OPENJDK_VERSION_17 - Change BR2_OPENJDK_VERSION_LTS -> BR2_OPENJDK_VERSION_11 Signed-off-by: Adam Duskett <aduskett@gmail.com> [Peter: add Config.in.legacy, use BR2_PACKAGE_OPENJDK_ prefix] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-11-04 19:47:26 +01:00
config BR2_OPENJDK_VERSION_LTS
bool "OpenJDK LTS version was renamed to OpenJDK 11"
select BR2_LEGACY
help
The LTS version option was renamed to OpenJDK 11 to make it
clear what LTS version is.
package/openjdk: properly handle legacy for renamed options Commit "a610bf9967 package/openjdk{-bin}: bump version to 17.0.1+12" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2021.11, following the example described in the beginning of the file. Cc: Tudor Holton <buildroot@tudorholton.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:36 +01:00
# Note: BR2_OPENJDK_VERSION_LTS is still referenced from
# package/openjdk/Config.in
package/openjdk{-bin}: bump version to 17.0.1+12 OpenJDK 17 is a new LTS release, which leaves the Buildroot Config option of "LTS" and "LATEST" as a misnomer because both 11 and 17 are LTS releases. There are two options in this case: 1) Remove "LATEST" and update OpenJDK 11 to 17, and only support 17. 2) Change "LTS" to "11" and "LATEST" to "17" and only support the latest 2 LTS OpenJDK releases. After some discussion with Thomas Petazzoni and Peter Korsgaard, and testing, option 2 is the best course of action for a few reasons: - OpenJDK 11 and 17 have very long support cycles: - OpenJDK 11 has two years of Active and five years of security support left. - OpenJDK 17 has five years of Active and ten years of security support left. - Both OpenJDK versions build with the same parameters. - The maintenance cost of both versions is meager. - Both versions pass tests.package.test_openjdk without issue. Changes: - Change BR2_OPENJDK_VERSION_LATEST -> BR2_OPENJDK_VERSION_17 - Change BR2_OPENJDK_VERSION_LTS -> BR2_OPENJDK_VERSION_11 Signed-off-by: Adam Duskett <aduskett@gmail.com> [Peter: add Config.in.legacy, use BR2_PACKAGE_OPENJDK_ prefix] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-11-04 19:47:26 +01:00
config BR2_OPENJDK_VERSION_LATEST
bool "OpenJDK latest version (16.x) was removed"
select BR2_LEGACY
help
OpenJDK 16.x is no longer mainted, so the option has been
removed. Use OpenJDK 17.x instead.
package/openjdk: properly handle legacy for renamed options Commit "a610bf9967 package/openjdk{-bin}: bump version to 17.0.1+12" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2021.11, following the example described in the beginning of the file. Cc: Tudor Holton <buildroot@tudorholton.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:36 +01:00
# Note: BR2_OPENJDK_VERSION_LATEST is still referenced from
# package/openjdk/Config.in
package/openjdk{-bin}: bump version to 17.0.1+12 OpenJDK 17 is a new LTS release, which leaves the Buildroot Config option of "LTS" and "LATEST" as a misnomer because both 11 and 17 are LTS releases. There are two options in this case: 1) Remove "LATEST" and update OpenJDK 11 to 17, and only support 17. 2) Change "LTS" to "11" and "LATEST" to "17" and only support the latest 2 LTS OpenJDK releases. After some discussion with Thomas Petazzoni and Peter Korsgaard, and testing, option 2 is the best course of action for a few reasons: - OpenJDK 11 and 17 have very long support cycles: - OpenJDK 11 has two years of Active and five years of security support left. - OpenJDK 17 has five years of Active and ten years of security support left. - Both OpenJDK versions build with the same parameters. - The maintenance cost of both versions is meager. - Both versions pass tests.package.test_openjdk without issue. Changes: - Change BR2_OPENJDK_VERSION_LATEST -> BR2_OPENJDK_VERSION_17 - Change BR2_OPENJDK_VERSION_LTS -> BR2_OPENJDK_VERSION_11 Signed-off-by: Adam Duskett <aduskett@gmail.com> [Peter: add Config.in.legacy, use BR2_PACKAGE_OPENJDK_ prefix] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-11-04 19:47:26 +01:00
package/mpd: drop tidal option tidal option has been removed from mpd since version 0.22.10 and https://github.com/MusicPlayerDaemon/MPD/commit/97c43954e8df3f772899cda951ad5a7dd4a24f25 resulting in the following build failure since bump of meson to version 0.60.1 in commit 78d3f2ea03dfba07a73fe0405c2aa4778f063ce3: ../output-1/build/mpd-0.22.11/meson.build:1:0: ERROR: Unknown options: "tidal" Fixes: - http://autobuild.buildroot.org/results/b8c5879a02078f4962088dff5ae2ede1f0e6b805 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 14:05:15 +01:00
config BR2_PACKAGE_MPD_TIDAL
bool "mpd tidal option removed"
select BR2_LEGACY
help
tidal has been removed from mpd since version 0.22.10.
package/mrouted: bump version to v4.4 - Upstream has .sha256 checksums now, drop redundant .md5 - Upstream has dropped RSRR support, drop Config.in support - Add BR2_PACKAGE_MROUTED_RSRR to Config.in.legacy Signed-off-by: Joachim Wiberg <troglobit@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-11-03 22:34:16 +01:00
config BR2_PACKAGE_MROUTED_RSRR
bool "RSRR for RSVP removed in mrouted v4.4"
select BR2_LEGACY
help
The RSRR configure option and feature was dropped in upstream
mrouted as of v4.4. This feature was marked as experimental
since its inception well before v4.0 and was never deployed
in the field outside of academia.
package/binutils: remove csky version Binutils is the last part of the csky toolchain fork. The csky support has been merged in binutils 2.32 [1]. [1] https://sourceware.org/git/?p=binutils-gdb.git;a=commitdiff;h=9d24df82ece4e87a0328173d6bd31cb9ff558bb4 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Guo Ren <ren_guo@c-sky.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Asked-by: Guo Ren <guoren@kernel.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-03 14:40:27 +02:00
config BR2_BINUTILS_VERSION_CSKY
bool "binutils csky version removed"
select BR2_LEGACY
help
Support for binutils csky version has been removed.
package/gcc: remove csky version Remove gcc csky fork since it doesn't build with the latest compilers (gcc 8, 10, 11 tested) [1]. Removing the csky gcc fork has become unavoidable since the Buildroot Docker image used by the gitlab CI will switch soon to Debian bullseye soon [2]. The csky support for csky807 and csky810 has been upstreamed in gcc 10 [3] and csky860 will be supported by gcc 12 [4]. There is no info about the csky610. Although the csky architecture is supported since gcc 10, the support was not enabled in Buildroot. [1] http://lists.busybox.net/pipermail/buildroot/2021-August/621504.html [2] 71b83227128be62c169313e85bb8f339f977ad67 [3] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=cc7232b999b8336cf4e261407ed9289c77bed1f0 [4] https://gcc.gnu.org/git/?p=gcc.git;a=commitdiff;h=db92bd223e3957ee58b5a0c0fffd8b7766f1def3 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Guo Ren <ren_guo@c-sky.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Asked-by: Guo Ren <guoren@kernel.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-03 14:40:26 +02:00
config BR2_GCC_VERSION_CSKY
bool "gcc csky version removed"
select BR2_LEGACY
help
Support for gcc csky version has been removed.
package/canfestival: remove package Canfestival hasn't seen a patch since November of 2017, and it requires python2 to build. Remove the package. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-10-13 20:06:54 +02:00
config BR2_PACKAGE_CANFESTIVAL
bool "canfestival package removed"
select BR2_LEGACY
help
This package has been removed as it is unmaintained since
November 2017.
package/nmap: remove ndiff option The ndiff package provided by Nmap relies on python2; moreover, there have been pending pull requests to move ndiff to python3 for over two years with very little engagement by the maintainers (https://github.com/nmap/nmap/pull/1807). Remove the option to select ndiff altogether, it is replaced by python-pyndiff, which provides the same functionality (and more) as the ndiff provided by nmap, and is compatible with python3. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-10-12 19:48:37 +02:00
config BR2_PACKAGE_NMAP_NDIFF
bool "The ndiff utility has been removed"
select BR2_LEGACY
select BR2_PACKAGE_PYTHON_PYNDIFF
help
The ndiff utility provided by nmap requires python2 which is
deprecated. The same functionality is provided by the python
package pyndiff.
package/gdb: drop support for version 8.3.x Now that gdb 11.x has been added, that 10.x is the default, we can drop version 8.3.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-10-09 21:16:44 +02:00
config BR2_GDB_VERSION_8_3
bool "gdb version 8.3.x removed"
select BR2_LEGACY
help
gdb 8.3.x has been removed, use a newer version instead.
package/python-meld3: drop package This project isn't maintained anymore: https://github.com/Supervisor/meld3/commit/ed4e7b30eeae9e03170f388f5c6fc31aac21bf7d Signed-off-by: Asaf Kahlon <asafka7@gmail.com> [Peter: add Config.in.legacy entry] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-10-06 18:11:47 +02:00
config BR2_PACKAGE_PYTHON_MELD3
bool "python-meld3 package removed"
select BR2_LEGACY
help
This package has been removed as it is unmaintained since
April 2020.
package/strongswan: add options to select EAP plugins Add options to chose individual EAP plugins. All the new plugins are enabled by default if the old single option was enabled, for a seamless update from an older Buildroot config, but for new configurations, they are not enabled by default. BR2_PACKAGE_STRONGSWAN_EAP_AKA_3GPP2 is the only plugin requiring libgmp; the selection of BR2_PACKAGE_GMP is moved down accordingly. Signed-off-by: Martin Elshuber <martin.elshuber@theobroma-systems.com> [yann.morin.1998@free.fr: - move BR2_PACKAGE_STRONGSWAN_EAP to legacy - extend commit log accordingly - fix check-package ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-20 17:28:30 +02:00
config BR2_PACKAGE_STRONGSWAN_EAP
bool "strongswan EAP plugins now individually selectable"
select BR2_LEGACY
help
The various EAP plugins are now individually selectable.
package/gnuradio: drop gr-pager (gr-flex) option gr-pager (labeled 'gr-flex' in our menuconfig) is not available since bump to version 3.8.0.0 in commit 0d6a7b2981d4 (package/gnuradio: bump to version 3.8.0.0) and upstream commit: https://github.com/gnuradio/gnuradio/commit/2d2caa205f3c3059deab7c82660908656167fd90 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-10 08:53:05 +02:00
config BR2_PACKAGE_GNURADIO_PAGER
bool "gnuradio gr-flex support removed"
select BR2_LEGACY
help
gr-flex has been removed from gnuradio since version 3.8.0.0.
package/linux-headers: drop 5.11.x / 5.12.x headers The 5.11.x and 5.12.xx series are now EOL, so drop them. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-09-11 15:37:46 +02:00
config BR2_KERNEL_HEADERS_5_11
bool "kernel headers version 5.11.x are no longer supported"
select BR2_LEGACY
help
Version 5.11.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
config BR2_KERNEL_HEADERS_5_12
bool "kernel headers version 5.12.x are no longer supported"
select BR2_LEGACY
help
Version 5.12.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop 5.13.x headers The 5.13.x series is now EOL, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-11-03 22:40:10 +01:00
config BR2_KERNEL_HEADERS_5_13
bool "kernel headers version 5.13.x are no longer supported"
select BR2_LEGACY
help
Version 5.13.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
Config.in.legacy: create 2021.08 Commit 469c11c516959375f6caddde178adbdcdc5d9887 wrongly added a new option to 2021.05 which has been released, move it to 2021.08 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-07-04 22:51:12 +02:00
comment "Legacy options removed in 2021.08"
package/kodi-screensaver-crystalmorph: remove package The package received its last updates in 2017, is not part of the official Kodi github repo and its build is broken with Kodi 19.x. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-03-02 08:06:58 +01:00
boot/grub2: add support to build multiple Grub2 configurations in the same build When Grub2 is build it is configured only for one boot set-up, BIOS Legacy, EFI 32 bit or EFI 64 bit. It can not deal with several boot set-up on the same image. This patch allows to build Grub2 for different configurations simultaneously. To cover Grub2 configuration of legacy BIOS platforms (32-bit), 32-bit EFI BIOS and 64-bit EFI BIOS in the same build, multi-build system felt much more reasonable to just extend the grub2 package into 3 packages. We can no longer use autotools-package as a consequence of this multi-build, and we have to resort to generic-package and a partial duplication of the autotools-infra. Grub2 was already using custom option like --prefix or --exec-prefix so this won't add much more weirdness. We use a GRUB2_TUPLES list to describe all the configurations selected. For each boot case described in the GRUB2_TUPLES list, it configures and builds Grub2 in a separate folder named build-$(tuple). We use a foreach loop to make actions on each tuple selected. We have to separate the BR2_TARGET_GRUB2_BUILTIN_MODULES and the BR2_TARGET_GRUB2_BUILTIN_CONFIG for each BIOS or EFI boot cases. Signed-off-by: Kory Maincent <kory.maincent@bootlin.com> [yann.morin.1998@free.fr: - keep sub-options properly indented - fix check-package ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-09-23 17:57:21 +02:00
config BR2_TARGET_GRUB2_BUILTIN_MODULES
string "the grub2 builtin modules has been renamed"
help
This option has been split to separate the builtin modules
between BR2_TARGET_GRUB2_BUILTIN_MODULES_PC and
BR2_TARGET_GRUB2_BUILTIN_MODULES_EFI.
config BR2_TARGET_GRUB2_BUILTIN_MODULES_WRAP
bool
default y if BR2_TARGET_GRUB2_BUILTIN_MODULES != ""
select BR2_LEGACY
config BR2_TARGET_GRUB2_BUILTIN_CONFIG
string "the grub2 builtin configuration has been renamed"
help
This option has been split to separate the builtin
configuration between BR2_TARGET_GRUB2_BUILTIN_CONFIG_PC and
BR2_TARGET_GRUB2_BUILTIN_CONFIG_EFI.
config BR2_TARGET_GRUB2_BUILTIN_CONFIG_WRAP
bool
default y if BR2_TARGET_GRUB2_BUILTIN_CONFIG != ""
select BR2_LEGACY
package/libmcrypt: drop package Drop libmcrypt which is a cryptographic package that is not maintained anymore. Here is an extract of https://en.wikipedia.org/wiki/Mcrypt: "The last update to libmcrypt was in 2007, despite years of unmerged patches. These facts have led security experts to declare mcrypt abandonware and discourage its use in new development.". Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-08-20 00:09:45 +02:00
config BR2_PACKAGE_LIBMCRYPT
bool "libmcrypt package was removed"
select BR2_LEGACY
help
This package has been removed as "the last update to libmcrypt
was in 2007, despite years of unmerged patches. These facts
have led security experts to declare mcrypt abandonware and
discourage its use in new development" (extract from
https://en.wikipedia.org/wiki/Mcrypt).
package/mcrypt: drop package Drop mcrypt which is a cryptographic package that is not maintained anymore. Here is an extract of https://en.wikipedia.org/wiki/Mcrypt: "The last update to libmcrypt was in 2007, despite years of unmerged patches. These facts have led security experts to declare mcrypt abandonware and discourage its use in new development." Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-08-20 00:09:44 +02:00
config BR2_PACKAGE_MCRYPT
bool "mcrypt package was removed"
select BR2_LEGACY
help
This package has been removed as "the last update to libmcrypt
was in 2007, despite years of unmerged patches. These facts
have led security experts to declare mcrypt abandonware and
discourage its use in new development" (extract from
https://en.wikipedia.org/wiki/Mcrypt).
package/php: drop mcrypt mcrypt has been dropped from php since version 7.2.0 and https://github.com/php/php-src/commit/5a17f632d4c7d936385485a0cb187172f33eb97a Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-08-02 23:04:02 +02:00
config BR2_PACKAGE_PHP_EXT_MCRYPT
bool "PHP mcrypt extension removed"
select BR2_LEGACY
help
mcrypt has been removed from php since version 7.2.0.
package/binutils: remove version 2.34 Now that we have 2.35, 2.36 and 2.37, with 2.36 as the default, we can remove 2.34. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-07-31 20:55:59 +02:00
config BR2_BINUTILS_VERSION_2_34_X
bool "binutils 2.34 has been removed"
select BR2_LEGACY
help
binutils 2.34 has been removed, use a newer version.
package/libsoil: remove package All kodi screensavers previously needing libsoil removed the dependency. For reference: https://github.com/xbmc/screensaver.matrixtrails/commit/92a0d44e9151cfce3be74e81a3e39f0688d69b7a https://github.com/xbmc/screensaver.asterwave/commit/8a778873754de09c93031408c71b3c40d198f3bc Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-08-01 08:12:25 +02:00
config BR2_PACKAGE_LIBSOIL
bool "libsoil package removed"
select BR2_LEGACY
help
The libsoil package was removed. All packages needing
libsoil removed the dependency.
package/clapack: remove package clapack has been unmaintained for a couple of years. It is semi-automatically generated from lapack sources using the f2c fortran-to-C converter, which itself is pretty much unmaintained. Remove the package. Remove the dependency on !CLAPACK from lapack. Automatically select lapack from legacy if possible. Cc: Alexandre PAYEN <alexandre.payen@smile.fr> Cc: Benjamin Kamath <kamath.ben@gmail.com> Cc: Thomas De Schampheleire <thomas.de_schampheleire@nokia.com> Cc: Romain Naour <romain.naour@smile.fr> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-07-25 13:12:30 +02:00
config BR2_PACKAGE_CLAPACK
bool "cblas/clapack package removed"
select BR2_LEGACY
select BR2_PACKAGE_LAPACK if BR2_PACKAGE_LAPACK_ARCH_SUPPORTS && BR2_TOOLCHAIN_HAS_FORTRAN
help
The clapack package was removed. LAPACK no longer generates a
C version. Use lapack instead. This does require a Fortran
compiler however.
package/spidermonkey: drop package Now that Spidermonkey is no longer required to build the polkit package, and no other packages require Spidermonkey, and python2 is required to build the package, it is safe to drop the package. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-07-21 23:45:18 +02:00
config BR2_PACKAGE_SPIDERMONKEY
bool "spidermonkey package removed"
select BR2_LEGACY
help
The spidermonkey package was removed. The only package that
depended on spidermonkey was polkit. The spidermonkey
dependency is replaced with duktape.
package/kodi: enable optional vaapi support also for OpenGLES Upstream commit https://github.com/xbmc/xbmc/commit/c638987dd8181765f975763cb643d6869a3f661b removed the dependency to x11 support in libva keeping only libdrm as dependency. This commit will enable the usage of libva with Kodi's OpenGLES render system. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-06-20 11:09:00 +02:00
config BR2_PACKAGE_KODI_LIBVA
bool "kodi option to add libva support removed"
select BR2_LEGACY
help
Kodi still has support for libva if the package is enabled but
the kodi-specific dependencies limiting libva support to non-
OPENGLES platforms were removed including this option.
package/python-idna: bump to version 3.2 - Python 2 is not supported since version 3.0 so update all reverse dependencies and remove python-coherence - License file name and its hash is updated due to: https://github.com/kjd/idna/commit/e7338bce90683246c480ddebd55b7682371389ed https://github.com/kjd/idna/commit/537aa99d4440b0f8a6178818350f27fcaab046ee https://github.com/kjd/idna/blob/v3.2/HISTORY.rst Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-07-10 23:55:32 +02:00
config BR2_PACKAGE_PYTHON_COHERENCE
bool "python-coherence package removed"
select BR2_LEGACY
help
This package has been removed as it can't be built anymore due
to python-twisted being now incompatible with python 2.
package/php: bump version to 8.0.7 Other changes: - Remove BR2_PACKAGE_PHP_EXT_JSON as the json extension is now an integral part of PHP and is no longer optional. Due to this, it is not added to Config.in.legacy. - Move BR2_PACKAGE_PHP_EXT_XMLRPC to Config.in.legacy as the extension has been removed. See https://wiki.php.net/rfc/unbundle_xmlprc for an explination. - Add a new patch that allows for opcache to cross-compile with PHP8. - Explicitly disable opcache-jit when opcache is enabled, as the JIT fails to cross-compile. - --enable-maintainer-zts is now --enable-zts Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-06-29 18:50:54 +02:00
config BR2_PACKAGE_PHP_EXT_XMLRPC
bool "PHP XMLRPC extension removed"
select BR2_LEGACY
help
The XMLRPC php extension was removed.
See: https://wiki.php.net/rfc/unbundle_xmlprc
package/gcc: restrict gcc 8.x to PowerPC SPE gcc 11.1 is around, gcc 10.2 is the default version, so drop 8.4 in order to reduce the gcc choice. For PowerPC SPE, introduce BR2_GCC_VERSION_POWERPC_SPE to avoid removing defconfigs arcturus_ucp1020_defconfig, freescale_p1025twr_defconfig and qemu_ppc_mpc8544ds_defconfig that are still used by some users [1]. BR2_GCC_VERSION_POWERPC_SPE use the same gcc version (8.4), no change expected. [1] 96e80ad214ced86c802d561946fa7da88c1595eb Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Oleksandr Zhadan <oleks@arcturusnetworks.com> Cc: Michael Durrant <mdurrant@ArcturusNetworks.com> Cc: Matthew Weber <matthew.weber@collins.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-06-27 16:00:49 +02:00
config BR2_GCC_VERSION_8_X
bool "gcc 8.x support removed"
select BR2_LEGACY
help
Support for gcc version 8.x has been removed. The current
default version (10.x or later) has been selected instead.
Config.in.legacy: create 2021.08 Commit 469c11c516959375f6caddde178adbdcdc5d9887 wrongly added a new option to 2021.05 which has been released, move it to 2021.08 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-07-04 22:51:12 +02:00
comment "Legacy options removed in 2021.05"
package/lvm2: drop BR2_PACKAGE_LVM2_APP_LIBRARY The application library (liblvm2app) has been dropped since version 2.03.00 and https://github.com/lvmteam/lvm2/commit/0d22b58172808f050abeacdb5d6a7b7132b91a8c It should be noted that lvm2 support must be dropped from udisks until a bump to at least version 2.7.0 and https://github.com/storaged-project/udisks/commit/4c0709a893be49a0db5b2839e4766621e2c1bb98 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: - slightly expand help text for legacy BR2_PACKAGE_UDISKS_LVM2 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-17 19:06:09 +02:00
config BR2_PACKAGE_UDISKS_LVM2
bool "udisks lvm2 support removed"
select BR2_LEGACY
help
The lvm2 support was removed because udisks < 2.7.0 still
depends on lvm2 application library, which was removed
Config.in.lgeacy: fix udisks lvm2 help Remove spurious "was removed" Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-17 23:18:57 +02:00
in lvm2.
package/lvm2: drop BR2_PACKAGE_LVM2_APP_LIBRARY The application library (liblvm2app) has been dropped since version 2.03.00 and https://github.com/lvmteam/lvm2/commit/0d22b58172808f050abeacdb5d6a7b7132b91a8c It should be noted that lvm2 support must be dropped from udisks until a bump to at least version 2.7.0 and https://github.com/storaged-project/udisks/commit/4c0709a893be49a0db5b2839e4766621e2c1bb98 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: - slightly expand help text for legacy BR2_PACKAGE_UDISKS_LVM2 ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-17 19:06:09 +02:00
config BR2_PACKAGE_LVM2_APP_LIBRARY
bool "lvm2 application library removed"
select BR2_LEGACY
help
The lvm2 application library was removed upstream.
package/lvm2: drop BR2_PACKAGE_LVM2_LVMETAD lvmetad has been dropped since version 2.03.00 and https://github.com/lvmteam/lvm2/commit/117160b27e510dceb1ed6acf995115c040acd88d Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-16 22:27:22 +02:00
config BR2_PACKAGE_LVM2_LVMETAD
bool "lvm2 lvmetad removed"
select BR2_LEGACY
help
The lvm2 lvmetad was removed upstream.
package/monkey: drop package As stated in commit 26a7d912f4a44bce558ee24bbadb5d10527f68c1, upstream is aware than the lack of release is an issue but no comments since 2018: https://github.com/monkey/monkey/issues/276 Moreover, TLS support is broken since 2016 but again upstream does not seem to care about it: https://github.com/monkey/monkey/issues/336 So just drop monkey Fixes: - http://autobuild.buildroot.org/results/0626ebab4f084d9b97d6696c7d4ebf7760d776a3 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-05-08 20:44:16 +02:00
config BR2_PACKAGE_MONKEY
bool "monkey package removed"
select BR2_LEGACY
help
This package has been removed as it has not seen any release
since 2016 and because TLS is broken on master.
package/docker-containerd: rename package to containerd containerd is now an independent project from Docker. This commit renames the Buildroot package from docker-containerd to containerd, adding a entry in Config.in.legacy accordingly. containerd is an industry-standard container runtime with an emphasis on simplicity, robustness and portability. It is available as a daemon for Linux and Windows, which can manage the complete container lifecycle of its host system: image transfer and storage, container execution and supervision, low-level storage and network attachments, etc. https://containerd.io Signed-off-by: Christian Stewart <christian@paral.in> Reviewed-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Arnout: - fix alphabetical ordering in package/Config.in - also do rename in DEVELOPERS - squash in second patch ]
2021-05-03 05:12:50 +02:00
config BR2_PACKAGE_DOCKER_CONTAINERD
bool "docker-containerd package was renamed to containerd"
select BR2_LEGACY
select BR2_PACKAGE_CONTAINERD
help
The containerd project is now independent from Docker.
The package was renamed to containerd accordingly.
package/iostat: drop package This package is not maintained anymore and even upstream site is dead. As iostat can also be provided by sysstat, just drop the package. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-05-01 21:51:26 +02:00
config BR2_PACKAGE_IOSTAT
Config.in.legacy: update iostat title Specify that iostat 'package' has been removed to be consistent with other entries Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-17 23:18:56 +02:00
bool "iostat package removed"
package/iostat: drop package This package is not maintained anymore and even upstream site is dead. As iostat can also be provided by sysstat, just drop the package. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-05-01 21:51:26 +02:00
select BR2_LEGACY
help
This package has been removed, use sysstat instead.
package/sconeserver: disable image Build of http::sconesite::image module was silently broken until commit d3b818c3cf0990117a8b59fcfc6c212f310ae6ec However, sconeserver fails to build with ImageMagick because: - it checks for ImageMagick++.pc instead of ImageMagick.pc - it uses the transform function which has been removed from the public API since version 7.0.1-0 and https://github.com/ImageMagick/ImageMagick/commit/06f590165f0505d42005264893fe14a9e8a79986 As sconeserver does not seem to be maintained anymore, drop BR2_PACKAGE_SCONESERVER_HTTP_SCONESITE_IMAGE. Fixes: - http://autobuild.buildroot.org/results/895ab582d1140f7677fc1c6934fa2e0c47c49f20 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Arnout: add legacy symbol. It costs us exactly nothing, and if someone actually had that selected, they know what's going on.]
2021-03-21 12:47:12 +01:00
config BR2_PACKAGE_SCONESERVER_HTTP_SCONESITE_IMAGE
bool "sconeserver http::sconesite::image removed"
Config.in.legacy: fix BR2_PACKAGE_SCONESERVER_HTTP_SCONESITE_IMAGE Commit fdb6fc2b4a5be747e7695f594cbbb1a941ceb05b forgot to select BR2_LEGACY Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-05-01 18:50:37 +02:00
select BR2_LEGACY
package/sconeserver: disable image Build of http::sconesite::image module was silently broken until commit d3b818c3cf0990117a8b59fcfc6c212f310ae6ec However, sconeserver fails to build with ImageMagick because: - it checks for ImageMagick++.pc instead of ImageMagick.pc - it uses the transform function which has been removed from the public API since version 7.0.1-0 and https://github.com/ImageMagick/ImageMagick/commit/06f590165f0505d42005264893fe14a9e8a79986 As sconeserver does not seem to be maintained anymore, drop BR2_PACKAGE_SCONESERVER_HTTP_SCONESITE_IMAGE. Fixes: - http://autobuild.buildroot.org/results/895ab582d1140f7677fc1c6934fa2e0c47c49f20 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Arnout: add legacy symbol. It costs us exactly nothing, and if someone actually had that selected, they know what's going on.]
2021-03-21 12:47:12 +01:00
help
Sconeserver cannot be built with ImageMagick - it uses the
"transofrm" function which is removed from public API.
package/x11r7/xserver_xorg-server: remove evdev input drivers for kdrive Upstream removed the evdev driver for kdrive: https://cgit.freedesktop.org/xorg/xserver/commit/configure.ac?h=server-1.20-branch&id=27819950e4158326e0f83a30f2e8968b932625ef Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-04-15 08:52:44 +02:00
config BR2_PACKAGE_XSERVER_XORG_SERVER_KDRIVE_EVDEV
bool "KDrive/TinyX evdev input driver removed"
select BR2_LEGACY
help
The evdev input driver in KDrive was removed.
package/x11r7/xserver_xorg-server: remove non-evdev input drivers for kdrive Upstream removed support for non-evdev input drivers for kdrive: https://cgit.freedesktop.org/xorg/xserver/commit/configure.ac?h=server-1.20-branch&id=e7b8b7b131d8283c96ed0aff4593ab41441b5d3b Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-04-15 08:52:42 +02:00
config BR2_PACKAGE_XSERVER_XORG_SERVER_KDRIVE_KBD
bool "KDrive/TinyX kbd input driver removed"
select BR2_LEGACY
help
The kbd input driver in KDrive was removed.
config BR2_PACKAGE_XSERVER_XORG_SERVER_KDRIVE_MOUSE
bool "KDrive/TinyX mouse input driver removed"
select BR2_LEGACY
help
The mouse input driver in KDrive was removed.
package/{mesa3d, mesa3d-headers}: bump version to 21.0.2 Release notes: 21.0.0: https://lists.freedesktop.org/archives/mesa-announce/2021-March/000622.html 21.0.1: https://lists.freedesktop.org/archives/mesa-announce/2021-March/000624.html 21.0.2: https://lists.freedesktop.org/archives/mesa-announce/2021-April/000625.html DRI swrast driver was removed: https://cgit.freedesktop.org/mesa/mesa/commit/?h=21.0&id=435de835cd639d1b9bb96f81fc224771dc90af6d OSMesa classic support was removed: https://cgit.freedesktop.org/mesa/mesa/commit/?h=21.0&id=ee802372180a2b4460cc7abb53438e45c6b6f1e4 To avoid any conflict, and to show that the new OSMesa is Gallium-based, we name the new option with a _GALLIUM suffix, even though this is now the only OSMesa implementation left. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [yann.morin.1998@free.fr: - rename the new option s/$/_GALLIUM/ - don't drop the the old (pre-classic) legacy option - slightly reword the OSMesa help entry ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-04-07 19:31:25 +02:00
config BR2_PACKAGE_MESA3D_OSMESA_CLASSIC
bool "mesa OSMesa (classic) option removed"
select BR2_LEGACY
select BR2_PACKAGE_MESA3D_OSMESA_GALLIUM
help
The OSMesa "classic" library option was removed upstream.
Only the Gallium-based implementation remains.
config BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST
bool "mesa DRI swrast driver removed"
select BR2_LEGACY
select BR2_PACKAGE_MESA3D_GALLIUM_DRIVER_SWRAST
help
The DRI swrast driver was removed upstream.
Only the Gallium-based implementation remains.
package/kodi-screensaver-crystalmorph: remove package The package received its last updates in 2017, is not part of the official Kodi github repo and its build is broken with Kodi 19.x. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-03-02 08:06:58 +01:00
config BR2_PACKAGE_KODI_SCREENSAVER_CRYSTALMORPH
bool "kodi-screensaver-crystalmorph removed"
select BR2_LEGACY
help
The package received its last updates in 2017, is not part
of the official Kodi github repo and its build is broken
with Kodi 19.x, so it was removed.
package/ipsec-tools: drop package Extract from http://ipsec-tools.sourceforge.net: "The development of ipsec-tools has been ABANDONED. ipsec-tools has security issues, and you should not use it. Please switch to a secure alternative!" Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-13 23:44:08 +01:00
comment "Legacy options removed in 2021.02"
package/audiofile: drop package The audiofile package is affected by multiple CVEs and is not maintained anymore (no release since 2013): https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&seach_type=all&query=cpe:2.3:a:audio_file_library_project:audio_file_library:0.3.6:*:*:*:*:*:*:* Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-02-07 21:27:18 +01:00
config BR2_PACKAGE_MPD_AUDIOFILE
bool "mpd audiofile support removed"
select BR2_LEGACY
help
The audiofile support was removed from mpd as audiofile is
affected by multiple CVEs and is not maintained anymore (no
release since 2013).
config BR2_PACKAGE_AUDIOFILE
bool "audiofile package removed"
select BR2_LEGACY
help
The audiofile package was removed as it is affected by
multiple CVEs and is not maintained anymore (no release since
2013).
package/binutils: drop 2.33.x series Now that 2.36.x has been added, that 2.35.x is the default version, drop support for 2.33.x. Note that we keep binutils 2.32.x as it is the latest version that works for FLAT binaries (used on noMMU platforms). Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-01-31 23:33:02 +01:00
config BR2_BINUTILS_VERSION_2_33_X
bool "binutils 2.33.x has been removed"
select BR2_LEGACY
help
binutils 2.33.x has been removed, use a newer version.
package/libupnp18: drop package Drop libupnp18 as libupnp has been bumped to 1.14.x and 1.8.x will not been fixed against CallStranger a.k.a. CVE-2020-12695 mpd and vlc are already compliant with libupnp 1.14.x (i.e those packages use UpnpInit2 instead of the deprecated UpnpInit) Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-01-25 20:49:49 +01:00
config BR2_PACKAGE_LIBUPNP18
bool "libupnp18 package removed"
select BR2_LEGACY
select BR2_PACKAGE_LIBUPNP
help
Version 1.8.x of libupnp (i.e. libupnp18) has been removed
because it will never be fixed against CallStranger a.k.a.
CVE-2020-12695. The libupnp package (which has been updated to
version 1.14.x) has been selected instead.
package/boa: drop package Drop boa package as it is affected by multiple CVEs (CVE-2017-9833, CVE-2018-21027 and CVE-2018-21028) and is not maintained anymore (no release since 2005): https://nvd.nist.gov/vuln/search/results?form_type=Advanced&results_type=overview&seach_type=all&query=cpe:2.3:a:boa:boa:0.94.14.21:*:*:*:*:*:*:* Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-01-17 22:54:13 +01:00
config BR2_PACKAGE_BOA
bool "boa package removed"
select BR2_LEGACY
help
The boa package was removed as it is affected by multiple
CVEs and is not maintained anymore (no release since 2005).
package/linux-firmware: remove imx sdma firmware As reported on the mailing list [1], the imx sdma firmwares for imx[6,7,8] are provided by two packages: firmware-imx and linux-firmware $ sha256sum ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin 7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784 ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin $ sha256sum ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin 7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784 ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin firmware-imx also has firmwares for older variants as well, so this is what we keep as the only imx sdma firmware provider. [1] http://lists.busybox.net/pipermail/buildroot/2021-January/300938.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Fabio Estevam <festevam@gmail.com> Cc: Stephane Viau <stephane.viau@oss.nxp.com> Cc: Gary Bisson <gary.bisson@boundarydevices.com> [yann.morin.1998@free.fr: explain why we keep firmware-imx] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-01-17 14:31:19 +01:00
config BR2_PACKAGE_LINUX_FIRMWARE_IMX_SDMA
bool "imx sdma firmware is provided by firmware-imx"
select BR2_LEGACY
Config.in.legacy: fix selection of firmware-imx In order to select firmware-imx we have to select freescale-imx first. Reported-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-01-18 21:32:12 +01:00
select BR2_PACKAGE_FREESCALE_IMX
package/linux-firmware: remove imx sdma firmware As reported on the mailing list [1], the imx sdma firmwares for imx[6,7,8] are provided by two packages: firmware-imx and linux-firmware $ sha256sum ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin 7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784 ./firmware-imx-8.10/firmware/sdma/sdma-imx6q.bin $ sha256sum ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin 7790c161b7e013a9dbcbffb17cc5d4cb63d952949a505647e4679f02d04c4784 ./linux-firmware-20201022/imx/sdma/sdma-imx6q.bin firmware-imx also has firmwares for older variants as well, so this is what we keep as the only imx sdma firmware provider. [1] http://lists.busybox.net/pipermail/buildroot/2021-January/300938.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Fabio Estevam <festevam@gmail.com> Cc: Stephane Viau <stephane.viau@oss.nxp.com> Cc: Gary Bisson <gary.bisson@boundarydevices.com> [yann.morin.1998@free.fr: explain why we keep firmware-imx] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2021-01-17 14:31:19 +01:00
select BR2_PACKAGE_FIRMWARE_IMX
help
linux-firmware provide the same firmware as firmware-imx.
We prefer using firmware-imx as the only provider.
package/gdb: drop gdb 8.2 With the introduction of gdb 10.1, we now have four versions of gdb supported, so let's drop support for the oldest. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-12-28 21:10:24 +01:00
config BR2_GDB_VERSION_8_2
bool "gdb 8.2.x has been removed"
select BR2_LEGACY
help
gdb 8.2 support has been removed, you can use a newer
version such as 8.3 or more recent.
package/qoriq-rcw: rename from package/rcw This is really only for QoriQ SoCs. Also the upstream package - despite its base name of the git repository - is "qoriq-components/rcw". Thus rename it to a more specify package name. Note that there are other rcw implementations for other platforms, and each implementation only applies to that specific platform; it hus does not make sense that there are more than one rcw enabled at the same time; so we keep using /usr/share/rcw as the install location; this also help backward compatibility with existing post-build scripts. Signed-off-by: Changming Huang <jerry.huang@nxp.com> Cc: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: - rebase on master - incorporate changes by Michael - don't move to an 'nxp' sub-directory - reword the legacy entry; select the new package - expand commit log to explain why we keep installing in host/usr/share/rcw/ (thanks to Michael for prompting that) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 09:38:50 +01:00
config BR2_PACKAGE_HOST_RCW
Config.in.legacy: fix typo oriq-rcw -> qoriq-rcw Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2021-01-17 23:01:01 +01:00
bool "rcw package was renamed to qoriq-rcw"
package/qoriq-rcw: rename from package/rcw This is really only for QoriQ SoCs. Also the upstream package - despite its base name of the git repository - is "qoriq-components/rcw". Thus rename it to a more specify package name. Note that there are other rcw implementations for other platforms, and each implementation only applies to that specific platform; it hus does not make sense that there are more than one rcw enabled at the same time; so we keep using /usr/share/rcw as the install location; this also help backward compatibility with existing post-build scripts. Signed-off-by: Changming Huang <jerry.huang@nxp.com> Cc: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: - rebase on master - incorporate changes by Michael - don't move to an 'nxp' sub-directory - reword the legacy entry; select the new package - expand commit log to explain why we keep installing in host/usr/share/rcw/ (thanks to Michael for prompting that) ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 09:38:50 +01:00
select BR2_PACKAGE_HOST_QORIQ_RCW
select BR2_LEGACY
help
The rcw package was specific to the QorIQ platform, so it has
been renamed to qoriq-rcw, to leave room for other *-rcw
packages for other platforms.
{linux, linux-headers}: bump 5.{4, 10}.x 4.{4, 9, 14, 19} series Drop 5.9 stable (EOL). Signed-off-by: Petr Vorel <petr.vorel@gmail.com> [Peter: add Config.in.legacy handling for 5.9] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2021-01-11 18:55:20 +01:00
config BR2_KERNEL_HEADERS_5_9
bool "kernel headers version 5.9.x are no longer supported"
select BR2_LEGACY
help
Version 5.9.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop 5.8 headers The 5.8.x series is now EOL, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-12-14 16:56:11 +01:00
config BR2_KERNEL_HEADERS_5_8
bool "kernel headers version 5.8.x are no longer supported"
select BR2_LEGACY
help
Version 5.8.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
arch/Config.in.powerpc: Drop PPC601 support Linux support was removed in 5.10 [1]. Since no in-tree defconfig depends on it, just remove it. [1] https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/arch/powerpc?id=f0ed73f3fa2cdca65973659689ec9e46d99a5f60 Reported-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Michael Walle <michael@walle.cc> [yann.morin.1998@free.fr: reorder legacy entry] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-12-15 09:14:33 +01:00
config BR2_powerpc_601
bool "PowerPC 601 support removed"
select BR2_LEGACY
help
The support for the PowerPC 601 processors has been removed.
package/ti-sgx-{km, um}: bump to SDK 06.01.00.08 versions Currently, the ti-sgx packages and the beaglebone_qt5_defconfig do not work with KMS nor Weston. What's worse, is the latest SDK version 06.03.00.106 (as of this commit) of these packages is broken and does not correctly support KMS, and attempting to run KMS applications results in eglfs initialization failures. As such, bumping these packages to the version before 06.03.00.106 is the best option. Because of the above problems, several packages must change at the same time to ensure this patch does not break any other packages: - ti-sgx-libgbm - dropped, merged into ti-sgx-um, see below - ti-sgx-um: - bump the version that matches TI SDK 06.01.00.08. - demove select BR2_PACKAGE_TI_SGX_LIBGBM in Config.in, as the libgbm package merges ti-sgx-libgbm with this package. - ti-sgx-km: - bump the version that matches TI SDK 06.01.00.08. Signed-off-by: Adam Duskett <Aduskett@gmail.com> Tested-by: Markus <zehnder@live.com> [yann.morin.1998@free.fr: - actually switch qt5base to use ti-sgx-um - split the beaglebone config changes to their own patch - split the ti-sgx-demos changes to their own patch ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-12-12 23:01:26 +01:00
config BR2_PACKAGE_TI_SGX_LIBGBM
bool "ti-sgx-libgbm support removed"
select BR2_LEGACY
help
TI has merged the ti-sgx-libgbm package with the ti-sgx-um
package
package/ipsec-tools: drop package Extract from http://ipsec-tools.sourceforge.net: "The development of ipsec-tools has been ABANDONED. ipsec-tools has security issues, and you should not use it. Please switch to a secure alternative!" Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-11-13 23:44:08 +01:00
config BR2_PACKAGE_IPSEC_TOOLS
bool "ipsec-tools package was removed"
select BR2_LEGACY
help
This package has been removed as it has security issues and
has been abandoned since 2014.
Config.in.legacy: adjust location of gdb 8.1 legacy option The gdb 8.1 option will have been removed from 2020.11, not 2020.08. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-29 13:50:52 +02:00
comment "Legacy options removed in 2020.11"
package/kodi-peripheral-steamcontroller: remove package The package is broken: https://github.com/kodi-game/peripheral.steamcontroller/pull/8#issuecomment-441469406 https://github.com/kodi-game/peripheral.steamcontroller/issues/10#issuecomment-467551856 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-06-14 09:33:00 +02:00
package/gpsd: bump version to 3.21 Update gpsd to latest release v3.21: - bump version - update checksums - remove patch for v3.20: it is not needed for v3.21 - remove obsolete options and add them to Config.in.legacy Signed-off-by: Olivier Dautricourt <olivier.dautricourt@orolia.com> Signed-off-by: Sergey Matyukevich <geomatsi@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-11-01 12:47:11 +01:00
config BR2_PACKAGE_GPSD_FIXED_PORT_SPEED
bool "compile with fixed serial port speed"
select BR2_LEGACY
help
Since gpsd 3.20, GPSD_FIXED_PORT_SPEED is replaced
by runtime option --speed.
config BR2_PACKAGE_GPSD_RECONFIGURE
bool "allow gpsd to change device settings"
select BR2_LEGACY
help
Since gpsd 3.21, GPSD_RECONFIGURE is replaced
by runtime option --passive.
config BR2_PACKAGE_GPSD_CONTROLSEND
bool "allow gpsctl/gpsmon to change device settings"
select BR2_LEGACY
help
Option removed in gpsd 3.21
package/opencv: drop package opencv 2.x has seen no release since July 2018 and all buildroot packages are already compatible with opencv3 so drop it to ease the addition of opencv4 which is not fully backward compatible with opencv3 as "a lot of C API from OpenCV 1.x has been removed.": https://opencv.org/opencv-4-0. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-10-18 16:32:00 +02:00
config BR2_PACKAGE_OPENCV
bool "opencv package was removed"
select BR2_LEGACY
help
This package has been removed, use opencv3 instead.
package/libcroco: drop package Drop libcrococo as it is affected by several security issues such as CVE-2020-12825 which will never be fixed as this project has been archived: https://gitlab.gnome.org/Archive/libcroco/-/issues/8 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-10-16 07:52:48 +02:00
config BR2_PACKAGE_LIBCROCO
bool "libcroco package was removed"
select BR2_LEGACY
help
This package has been removed as it is affected by several
security issues such as CVE-2020-12825 which will never be
fixed as libcroco has been archived.
package/bellagio: drop package Drop bellagio support as the project is no longer maintained (no update since 2011, see [1]) and the last reference (from gst-omx) is gone. [1] http://omxil.sourceforge.net Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-09-24 23:17:14 +02:00
config BR2_PACKAGE_BELLAGIO
bool "bellagio package was removed"
select BR2_LEGACY
help
This package has been removed as it is not maintained anymore
(no release since 2011).
package/systemd: group all journal-remote tools under a single option The -Dremote=true flag enables three tools: systemd-journal-gatewayd, systemd-journal-remote and systemd-journal-upload. It is not possible with simple means to install them seperately. So use the systemd-journal-remote option to enable or disable them all together. Drop systemd-journal-gatewayd option and add it to legacy. Fixes: #12301 Signed-off-by: Michael Nosthoff <buildroot@heine.tech> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-10-14 17:12:50 +02:00
config BR2_PACKAGE_SYSTEMD_JOURNAL_GATEWAY
bool "systemd-journal-gatewayd now in systemd-journal-remote"
select BR2_LEGACY
select BR2_PACKAGE_SYSTEMD_JOURNAL_REMOTE
help
All system journal remote programs are now enabled using
BR2_PACKAGE_SYSTEMD_JOURNAL_REMOTE.
package/uboot-tools: migrate BR2_TARGET_UBOOT_BOOT_SCRIPT from U-Boot pkg For consistancy and dependencies between uboot and uboot-tools, this patch migrates the script creation over in a similar way as the env image creation. Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-09-24 21:29:11 +02:00
config BR2_TARGET_UBOOT_BOOT_SCRIPT
bool "u-boot script generation was moved"
select BR2_LEGACY
select BR2_PACKAGE_HOST_UBOOT_TOOLS
select BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT
help
Migrated U-Boot script generation to uboot-tools
# Note: BR2_TARGET_UBOOT_BOOT_SCRIPT_SOURCE is still referenced from
# package/uboot-tools/Config.in
config BR2_TARGET_UBOOT_BOOT_SCRIPT_SOURCE
string "The uboot script source string has been renamed"
depends on BR2_TARGET_UBOOT_BOOT_SCRIPT
help
Migrated U-Boot script generation to uboot-tools.
New option is named
BR2_PACKAGE_HOST_UBOOT_TOOLS_BOOT_SCRIPT_SOURCE
package/uboot-tools: migrate BR2_TARGET_UBOOT_ENVIMAGE from U-Boot pkg Migrating the support for this feature to uboot-tools to gain the ability to build env files when BR2_TARGET_UBOOT isn't selected. When _ENVIMAGE_SOURCE is not set, we generate a default environment. However, this default depends on the U-Boot configuration. Therefore, this can only be done if uboot itself is built as well, and host-uboot-tools needs to depend on uboot. For the same reason, the commands for creating the environment have to be adapted a little. Take this occasion to drastically simplify them. Note: This patch creates a circular dependency with uboot until the similar migration patch is merged for uboot scripts Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-09-24 21:29:10 +02:00
config BR2_TARGET_UBOOT_ENVIMAGE
bool "u-boot env generation was moved"
select BR2_LEGACY
select BR2_PACKAGE_HOST_UBOOT_TOOLS
select BR2_PACKAGE_HOST_UBOOT_TOOLS_ENVIMAGE
help
Migrated U-Boot env generation to uboot-tools
# Note: BR2_TARGET_UBOOT_ENVIMAGE_SOURCE is still referenced from
# package/uboot-tools/Config.in
config BR2_TARGET_UBOOT_ENVIMAGE_SOURCE
string "The uboot env image source string has been renamed"
depends on BR2_TARGET_UBOOT_ENVIMAGE
help
Migrated U-Boot env generation to uboot-tools.
New option is named
BR2_PACKAGE_HOST_UBOOT_TOOLS_ENVIMAGE_SOURCE
# Note: BR2_TARGET_UBOOT_ENVIMAGE_SIZE is still referenced from
# package/uboot-tools/Config.in
config BR2_TARGET_UBOOT_ENVIMAGE_SIZE
string "The uboot env image size string has been renamed"
depends on BR2_TARGET_UBOOT_ENVIMAGE
help
Migrated U-Boot env generation to uboot-tools.
New option is named BR2_PACKAGE_HOST_UBOOT_TOOLS_ENVIMAGE_SIZE
config BR2_TARGET_UBOOT_ENVIMAGE_REDUNDANT
bool "u-boot env generation was moved"
depends on BR2_TARGET_UBOOT_ENVIMAGE
select BR2_PACKAGE_HOST_UBOOT_TOOLS_ENVIMAGE_REDUNDANT
help
Migrated U-Boot env generation to uboot-tools
package/kismet: bump to version 2020-09-R3 - Drop all patches (not needed anymore) - Update help message of Config.in: kismet does not support only WiFi but also Bluetooth, SDR ... - Remove ncurses dependency - libnl is now optional - Drop --with-netlink-version (not available anymore) - Add protobuf, protobuf-c, sqlite and zlib mandatory dependencies - kismet_client and kismet_drone have been dropped since version 2019-04-R1 - Select libmicrohttpd for kismet_server - Add optional libusb and lm-sensors dependencies - Use --{enable,disable}-{libcap,pcre} options - Use the new LICENSE file Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-10-04 17:50:03 +02:00
config BR2_PACKAGE_KISMET_CLIENT
bool "kismet client support was removed"
select BR2_LEGACY
help
Kismet client support was removed since version 2019-04-R1.
config BR2_PACKAGE_KISMET_DRONE
bool "kismet drone support was removed"
select BR2_LEGACY
help
Kismet drone support was removed since version 2019-04-R1.
package/gcc: remove gcc 7.5.0 gcc 10.2 is around, gcc 9.3 is the default version, so drop 7.5 in order to reduce the gcc choice. See: https://gcc.gnu.org/legacy-ml/gcc/2019-11/msg00099.html The last defconfig using gcc 7 (roseapplepi_defconfig) has been updated by 9cd065438020582011f393bd71308717b07c5a71. Signed-off-by: Romain Naour <romain.naour@gmail.com> [Peter: add Config.in.legacy entry] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-10-03 11:17:04 +02:00
config BR2_GCC_VERSION_7_X
bool "gcc 7.x support removed"
select BR2_LEGACY
help
Support for gcc version 7.x has been removed. The current
default version (9.x or later) has been selected instead.
Config.in.legacy: fix spelling of 'config' Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-09-23 23:04:43 +02:00
config BR2_PACKAGE_GST1_VALIDATE
package/gst1-devtools: new package (was gst1-validate) Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-09-16 21:49:28 +02:00
bool "gst1-validate was moved to gst1-devtools"
select BR2_PACKAGE_GST1_DEVTOOLS
select BR2_LEGACY
help
This package has been removed, use gst1-devtools instead.
package/gst1-plugins-bad: bump version to 1.18.0 - change home page url to https - remove 0001-meson-build-gir-even-when-cross-compiling-if-introspection.patch (upstream [1]) - remove 002-meson-allow-the-user-to-disable-opencv.patch (upstream [2]) - add option for new plugins dvbsubenc, rist, rtmp2, rtp, switchbin and v4l2codecs - removed yadif plugin (functionality moved to gst1-plugins-good deinterlace [3]) - meson options: avtp=disabled, d3d11=disabled, mediafoundation=disabled, microdns=disabled, svthevcenc=disabled, transcode=disabled, wasapi2=disabled zxing=disabled, magicleap=disabled, extra-checks=disabled, doc=disabled [1] https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/97a4d0cd7de8cfbf983acc7e37ba2f8fb73c3e19.patch [2] https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/833a65cc3c993b864f077152ace95d660d6a9625.patch [3] https://gitlab.freedesktop.org/gstreamer/gst-plugins-bad/-/commit/c7095abd31a2828ef7832744bc2e221650c6502e.patch Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-09-16 21:49:26 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_YADIF
bool "gst1-plugins-bad yadif plugin was removed"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_GOOD_PLUGIN_DEINTERLACE
help
This plugin was removed with gst1-plugins-bad-1.18.0, the
same functionality has moved to gst1-plugins-good
deinterlace plugin (method=yadif).
package/gqview: drop package Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-09-20 16:21:43 +02:00
config BR2_PACKAGE_GQVIEW
bool "gqview package was removed"
select BR2_LEGACY
help
This package has been removed as it is not maintained anymore
(no release since 2006).
package/weston-imx: remove deprecated package - the package couldn't be selected with vivante backend anyway since the split - the package couldn't be updated to newer versions as it would imply forking libdrm and wayland-protocols for it to build - drawback of not using NXP weston is the lack of G2D support, let's have it as a known issue for Buildroot but use standard weston package Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-06-19 14:55:00 +02:00
config BR2_PACKAGE_WESTON_IMX
bool "weston-imx package was removed"
select BR2_LEGACY
help
This package has been removed, use weston instead.
package/linux-headers: drop 5.7 headers The 5.7.x series is now EOL, so drop it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-09-05 22:19:56 +02:00
config BR2_KERNEL_HEADERS_5_7
bool "kernel headers version 5.7.x are no longer supported"
select BR2_LEGACY
help
Version 5.7.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/tinyhttpd: remove package tinyhttpd is affected by CVE-2002-1819 and is not maintained anymore (no release since 2001) so remove it Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-17 10:38:32 +02:00
config BR2_PACKAGE_TINYHTTPD
bool "tinyhttpd package removed"
select BR2_LEGACY
help
The tinyhttpd package was removed as it is affected by
CVE-2002-1819 and is not maintained anymore (no release since
2001).
package/x11r7/xserver_xorg-server: remove unmaintained versions 1.14.7 & 1.17.4 Upstream does not maintain these older versions anymore. Due to security fixes not being backported to these versions anymore we remove these old X server versions. Move current patches from version-specific directory to package directory. No legacy handling is added for the old versions, since it's simply a version bump. THe old packages and features (AIGLX) that depend on the old versions do have legacy handling. Remove legacy handling for 1.19.* Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-08-29 13:34:03 +02:00
config BR2_PACKAGE_XSERVER_XORG_SERVER_AIGLX
bool "X.org Enable AIGLX Extension"
select BR2_LEGACY
help
AIGLX Extension was removed in X.org X server version 1.19.0
package/amd-catalyst: remove package Current X.org X server is incompatible with this driver. We no longer support unmaintainted versions of X.org X server. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-08-29 13:34:02 +02:00
config BR2_PACKAGE_AMD_CATALYST
bool "amd-catalyst"
select BR2_LEGACY
help
Current X.org server is incompatible with this driver.
package/nvidia-tegra23: remove package Current X.org X server is incompatible with this driver. We no longer support unmaintainted versions of X.org X server. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2020-08-29 13:34:01 +02:00
config BR2_PACKAGE_NVIDIA_TEGRA23
bool "nvidia-tegra23 package removed"
select BR2_LEGACY
help
Current X.org server is incompatible with this driver.
package/gdb: drop support for gdb 8.1 Now that gdb 9.2 has been introduced, and gdb 8.3 is the default gdb version, we can drop the oldest gdb version, 8.1. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-08-17 12:01:18 +02:00
config BR2_GDB_VERSION_8_1
bool "gdb 8.1.x has been removed"
select BR2_LEGACY
help
The 8.1.x version of gdb has been removed. Use a newer
version instead.
package/kodi-peripheral-steamcontroller: remove package The package is broken: https://github.com/kodi-game/peripheral.steamcontroller/pull/8#issuecomment-441469406 https://github.com/kodi-game/peripheral.steamcontroller/issues/10#issuecomment-467551856 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-06-14 09:33:00 +02:00
comment "Legacy options removed in 2020.08"
toolchain/toolchain-external/toolchain-external-codesourcery-amd64: remove package This toolchain uses an old gcc 6.2.0 compiler (not even the latest gcc from the 6.x series), which fails to build the recent Boost package. Since newer versions of this toolchain are no longer made publicly available from Mentor Graphics, our only option is to drop the toolchain. Fixes: http://autobuild.buildroot.net/results/10edaed22c15b9d0f7de187085aeebc96e5ebe6c/ Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-08-23 13:15:13 +02:00
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_AMD64
bool "toolchain-external-codesourcery-amd64 removed"
select BR2_LEGACY
help
The CodeSourcery toolchain for AMD64, in version 2016.11 was
dropped, due to it using a too old gcc 6.2.0 compiler which
caused issues compiling a number of recent packages
(e.g. Boost). CodeSourcery has stopped making newer versions
of this toolchain publicly available, so it was not possible
to update it.
package/linux-headers: drop support for 5.6.x headers The 5.6.x series is now EOL so remove the option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-07-28 09:17:07 +02:00
config BR2_KERNEL_HEADERS_5_6
bool "kernel headers version 5.6.x are no longer supported"
select BR2_LEGACY
help
Version 5.6.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop support for 5.5.x headers The 5.5.x series is now EOL so remove the option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-07-28 09:17:06 +02:00
config BR2_KERNEL_HEADERS_5_5
bool "kernel headers version 5.5.x are no longer supported"
select BR2_LEGACY
help
Version 5.5.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/binutils: remove version 2.31.1 Now that binutils 2.34 has been introduced, and we have moved to 2.33.1 as the default version, it is time to drop support for binutils 2.31.1. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-06-25 14:13:02 +02:00
config BR2_BINUTILS_VERSION_2_31_X
bool "binutils version 2.31.1 support removed"
select BR2_LEGACY
help
Support for binutils version 2.31.1 has been removed. The
current default version (2.33.1 or later) has been selected
instead.
package/kodi-peripheral-steamcontroller: remove package The package is broken: https://github.com/kodi-game/peripheral.steamcontroller/pull/8#issuecomment-441469406 https://github.com/kodi-game/peripheral.steamcontroller/issues/10#issuecomment-467551856 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-06-14 09:33:00 +02:00
config BR2_PACKAGE_KODI_PERIPHERAL_STEAMCONTROLLER
bool "kodi-peripheral-steamcontroller package was removed"
select BR2_LEGACY
help
This package is broken.
package/gcc: remove version 5.5.5 gcc 9.2 is around, gcc 8.4 is the default version, so drop 5.5 in order to reduce the gcc choice. GCC 5.5 was disabled for Glibc based toolchain since Glibc 2.30 needs GCC 6.2 or later. See: https://sourceware.org/ml/libc-alpha/2019-08/msg00029.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-22 22:15:40 +01:00
comment "Legacy options removed in 2020.05"
package/wiringpi: remove The author has completely ripped off the git tree, so the sources are no longer available, with that message: "Please look for alternatives for wiringPi" And indeed there is a better alternative, using the kernel GPIO subsystem and drivers. Note that queezelite looses that functionality now, but upstream squeezelite has done changes to do without wiringpi (hint for an upgrade?). Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr> Cc: Peter Seiderer <ps.report@gmx.net> Cc: Hiroshi Kawashima <kei-k@ca2.so-net.ne.jp> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-05-24 22:26:51 +02:00
config BR2_PACKAGE_WIRINGPI
bool "wiringpi package removed"
select BR2_LEGACY
help
The author of wiringpi has deprecated the package, and
completely removed the git tree that was serving the
sources, with this message:
Please look for alternatives for wiringPi
package/python-pycrypto: remove package This package doesn't work with Python 3.8 since the code contains time.clock() that was deprecated in Python 3.3 and removed in Python 3.8. Instead of applying non upstream patches from Fedora [1], python-pycrypto was replaced by python-pycryptodomex for crda and optee-os package. Now we can remove safely this package. [1] http://lists.busybox.net/pipermail/buildroot/2020-April/280683.html Fixes: https://gitlab.com/buildroot.org/buildroot/-/jobs/498144209 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-27 00:33:23 +02:00
config BR2_PACKAGE_PYTHON_PYCRYPTO
bool "python-pycrypto package removed"
select BR2_LEGACY
help
This package has been removed, use python-pycryptodomex
instead.
package/mtdev2tuio: remove package mtdev2tuio breaks the builds every now and then and is not maintained upstream. It does not seem to be useful any more. Signed-off-by: Stephan Hoffmann <sho@relinux.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-05-18 11:47:55 +02:00
config BR2_PACKAGE_MTDEV2TUIO
bool "mtdev2tuio package removed"
select BR2_LEGACY
help
The mtdev2tuio package was removed as it breaks the builds
every now and then and is not maintained upstream.
package/ezxml: remove package ezXML is affected by several CVEs and is not maintained anymore (no release since 2006) so remove it. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-05-16 15:11:01 +02:00
config BR2_PACKAGE_EZXML
bool "ezxml package removed"
select BR2_LEGACY
help
The ezXML package was removed as it is affected by several
CVEs and is not maintained anymore (no release since 2006).
package/collectd: remove lvm lvm has been removed since version 5.11.0 and https://github.com/collectd/collectd/commit/0e73c26f5670b2f11eecfdadaf545bcc7f260658 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-04-15 08:30:04 +02:00
config BR2_PACKAGE_COLLECTD_LVM
bool "lvm support in collectd was removed"
select BR2_LEGACY
help
collectd removed LVM plugin, liblvm2app has been deprecated
package/python-pyasn: remove duplicate package This is a duplicate of python-pyasn1. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-20 00:47:19 +02:00
config BR2_PACKAGE_PYTHON_PYASN
bool "duplicate python-pyasn1 package removed"
select BR2_LEGACY
select BR2_PACKAGE_PYTHON_PYASN1
help
This package was a duplicate of python-pyasn1.
package/python-pyasn-modules: remove duplicate package This is a duplicate of python-pyasn1-modules. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-19 10:50:11 +02:00
config BR2_PACKAGE_PYTHON_PYASN_MODULES
bool "duplicate python-pyasn1-modules package removed"
select BR2_LEGACY
select BR2_PACKAGE_PYTHON_PYASN1_MODULES
help
This package was a duplicate of python-pyasn1-modules.
package/linux-firmware: drop redundant QCA6174 firmware symbol BR2_PACKAGE_LINUX_FIRMWARE_QUALCOMM_6174 is a superset of BR2_PACKAGE_LINUX_FIRMWARE_ATHEROS_10K_QCA6174. Drop the redundant symbol. Add the full list of license files to BR2_PACKAGE_LINUX_FIRMWARE_QUALCOMM_6174. Add notice_ath10k_firmware-5.txt license file hash. Cc: Yegor Yefremov <yegorslists@googlemail.com> Reported-by: Yann E. MORIN <yann.morin.1998@free.fr> Signed-off-by: Baruch Siach <baruch@tkos.co.il> [yann.morin.1998@free.fr: - reorder license files - rewrap license files to usual style for multi-line variables ] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-04-12 09:24:31 +02:00
config BR2_PACKAGE_LINUX_FIRMWARE_ATHEROS_10K_QCA6174
bool "duplicate QCA6174 firmware symbol removed"
select BR2_LEGACY
select BR2_PACKAGE_LINUX_FIRMWARE_QUALCOMM_6174
help
This config symbol duplicates existing symbol for QCA6174
firmware.
package/qt5: bump version to 5.13.2 qt5canvas3d: - removed with 5.13 according to [1] qt5webengine: - remove 0001-pkg_config-Fixes-when-use_sysroot-false.patch (taken from upstream [2]) - update 3rdparty license hash list and chromium-latest.inc file [1] https://doc.qt.io/qt-5/whatsnew513.html [2] https://chromium.googlesource.com/chromium/src/+/a8c8396fd20d98666d517c45b358c63736e345ef Signed-off-by: Peter Seiderer <ps.report@gmx.net> [Thomas: add Config.in.legacy entry for qt5canvas3d] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-03 23:23:55 +02:00
config BR2_PACKAGE_QT5CANVAS3D
bool "qt5canvas3d was removed"
select BR2_LEGACY
help
This Qt5 module was removed by the upstream Qt project since
Qt 5.13, so the corresponding Buildroot package was removed
as well.
package/kodi: remove optional libtheora support Kodi plays these files through ffmpeg and does not link to libtheora anymore, see PR 9686. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-04-05 15:07:59 +02:00
config BR2_PACKAGE_KODI_LIBTHEORA
bool "libtheora support in Kodi was removed"
select BR2_LEGACY
help
Kodi does not need libtheora
Config.in.legacy: move cegui06 package to 2020.05 section During package update, the legacy option was set to the existing 2020.02 release instead of the next 2020.05. Signed-off-by: Bartosz Bilas <b.bilas@grinn-global.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-30 13:40:15 +02:00
config BR2_PACKAGE_CEGUI06
bool "BR2_PACKAGE_CEGUI06 was renamed"
select BR2_PACKAGE_CEGUI
select BR2_LEGACY
help
The BR2_PACKAGE_CEGUI06 config symbol was renamed to
BR2_PACKAGE_CEGUI.
package/gcc: remove version 5.5.5 gcc 9.2 is around, gcc 8.4 is the default version, so drop 5.5 in order to reduce the gcc choice. GCC 5.5 was disabled for Glibc based toolchain since Glibc 2.30 needs GCC 6.2 or later. See: https://sourceware.org/ml/libc-alpha/2019-08/msg00029.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-03-22 22:15:40 +01:00
config BR2_GCC_VERSION_5_X
bool "gcc 5.x support removed"
select BR2_LEGACY
help
Support for gcc version 5.x has been removed. The current
default version (8.x or later) has been selected instead.
Config.in.legacy: fix separator comment location When the fis and gadgetfs-test packages were removed, their respective options in Config.in.legacy were placed before the "Legacy options removed in 2020.02", while they should have been placed after. Let's fix that. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-02-03 16:47:34 +01:00
comment "Legacy options removed in 2020.02"
package/jamvm: drop package JamVM has not had a release since 2014 and is unmaintained. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-03-03 23:12:58 +01:00
config BR2_PACKAGE_JAMVM
bool "jamvm removed"
select BR2_LEGACY
help
JamVM has not had a release since 2014 and is unmaintained.
package/classpath: drop package This package has been abandoned by upstream since 2016 and has not had a release since 2012. In addition the GNU Compiler for Java that classpath was written to be used with has been removed as of GCC 7. It is no longer feasible to support classpath as it requires a java compiler capable of producing java 1.5 compatible bytecode which is not possible on hosts with a recent java compiler. Signed-off-by: James Hilliard <james.hilliard1@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-03-02 11:01:46 +01:00
config BR2_PACKAGE_CLASSPATH
bool "classpath removed"
select BR2_LEGACY
help
GNU Classpath package was removed. The last upstream
release was in 2012 and there hasn't been a commit
since 2016.
package/qt5: drop 5.6 support As discussed during the FOSDEM2019 develop days, Qt 5.6 is very old (5.6.3 was released in September 2017, and 5.6.x became EOL in March 2019), so drop it before the new Buildroot LTS release: https://elinux.org/Buildroot:DeveloperDaysFOSDEM2019#Qt5_versions_to_support:_keep_5.6_or_a_newer_LTS.3F And add legacy handling for it. There are a number of places where code checks for BR2_PACKAGE_QT5_VERSION_LATEST, so leave that as a blind option for now to not break the build. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-02-26 15:45:32 +01:00
config BR2_PACKAGE_QT5_VERSION_5_6
bool "qt 5.6 support removed"
select BR2_LEGACY
help
Support for Qt 5.6 is EOL and has been removed. The current
version (5.12 or later) has been selected instead.
package/libcurl: rename curl binary config symbol Package optional or choice config symbols are usually prefixed with the package config symbol name. Rename BR2_PACKAGE_CURL to BR2_PACKAGE_LIBCURL_CURL to conform. Update references to the old name. Cc: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-02-10 13:06:59 +01:00
config BR2_PACKAGE_CURL
bool "BR2_PACKAGE_CURL was renamed"
select BR2_PACKAGE_LIBCURL_CURL
select BR2_LEGACY
help
The BR2_PACKAGE_CURL config symbol was renamed to
BR2_PACKAGE_LIBCURL_CURL.
package/gstreamer/*: remove packages Gstreamer 0.10 has been deprecated upstream since 2012 and is missing a lot of features and (security) fixes compared to gstreamer1, so remove it. All gstreamer-0.10 sub packages depends on gstreamer, so we only need to add a legacy entry for that. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:25 +01:00
config BR2_PACKAGE_GSTREAMER
bool "gstreamer-0.10 removed"
select BR2_LEGACY
help
Gstreamer-0.10 package was removed. It has been deprecated
upstream since 2012, and is missing a lot of features and
fixes compared to gstreamer-1.x.
package/nvidia-tegra23-binaries: drop gstreamer 0.10.x support With the upcoming removal of gstreamer 0.10, the logic for installing binaries using gstreamer 0.10.x in nvidia-tegra23-binaries must go as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:24 +01:00
config BR2_PACKAGE_NVIDIA_TEGRA23_BINARIES_GSTREAMER_PLUGINS
bool "nvidia-tegra23 binaries gstreamer 0.10.x support removed"
select BR2_LEGACY
help
Gstreamer 0.10.x is no longer available in Buildroot, so
neither is the support in nvidia-tegra23 binaries.
config BR2_PACKAGE_NVIDIA_TEGRA23_BINARIES_NV_SAMPLE_APPS
bool "nvidia-tegra23 binaries sample apps removed"
select BR2_LEGACY
help
Gstreamer 0.10.x is no longer available in Buildroot, so
neither is the support in nvidia-tegra23 binaries.
package/freerdp: drop gstreamer 0.10.x support With the upcoming removal of gstreamer 0.10, the logic for building freerdp with support for it must go as well. As there is now a single option for gstreamer (1.x) support, convert the gstreamer support choice to a normal option for simplicity. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:23 +01:00
config BR2_PACKAGE_FREERDP_GSTREAMER
bool "freerdp gstreamer 0.10.x support removed"
select BR2_LEGACY
help
Gstreamer 0.10.x is no longer available in Buildroot, so
neither is the support in freerdp.
package/opencv3: drop gstreamer 0.10.x support With the upcoming removal of gstreamer 0.10, the logic for building opencv3 with support for it must go as well. As there is now a single option for gstreamer (1.x) support, convert the gstreamer support choice to a normal option for simplicity. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:22 +01:00
config BR2_PACKAGE_OPENCV3_WITH_GSTREAMER
bool "opencv3 gstreamer 0.10.x support removed"
select BR2_LEGACY
help
Gstreamer 0.10.x is no longer available in Buildroot, so
neither is the support in opencv3.
package/opencv: drop gstreamer 0.10.x support With the upcoming removal of gstreamer 0.10, the logic for building opencv with support for it must go as well. As there is now a single option for gstreamer (1.x) support, convert the gstreamer support choice to a normal option for simplicity. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:21 +01:00
config BR2_PACKAGE_OPENCV_WITH_GSTREAMER
bool "opencv gstreamer 0.10.x support removed"
select BR2_LEGACY
help
Gstreamer 0.10.x is no longer available in Buildroot, so
neither is the support in opencv.
package/libplayer: remove package Libplayer is dead upstream. The mercurial repo is no longer online, it hasn't seen any releases since 2010 and the mplayer backend was removed from Buildroot in 2018. With the upcoming removal of gstreamer 0.10, there is no longer any backends available in Buildroot, so remove the package. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-07 15:50:20 +01:00
config BR2_PACKAGE_LIBPLAYER
bool "libplayer package was removed"
select BR2_LEGACY
help
The libplayer package was removed. The latest release is
from 2010 and none of the backends are available in
Buildroot any more.
package/gcc: remove gcc 5.5 or1k fork Remove the old gcc 5.5 fork for or1k architecture that start to fail to build with recent version of Binutils >= 2.32 with the following error: host-gcc-final-or1k-musl-5.4.0-20170218/build/./gcc/crtbeginS.o: addend should be zero for plt relocations host/or1k-buildroot-linux-uclibc/bin/ld: final link failed: bad value https://gitlab.com/kubu93/buildroot/-/jobs/391938988 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-01-02 23:04:15 +01:00
config BR2_GCC_VERSION_OR1K
bool "gcc 5.x fork for or1k has been removed"
select BR2_LEGACY
help
Support for gcc 5.x for or1k has been removed. The current
default version (9.x or later) has been selected instead.
package/bluez_utils: drop package BlueZ 4.x is deprecated since a long time (BlueZ 5.x has been released in 2012) so drop it. For cwiid, sconeserver and ussp-push, replace bluez_utils by bluez5_utils. All other packages already support bluez5_utils so just drop bluez_utils. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-01-12 23:08:39 +01:00
config BR2_PACKAGE_BLUEZ_UTILS
bool "bluez-utils was removed"
select BR2_LEGACY
Config.in.legacy: fix selection of bluez5_utils Select BR2_PACKAGE_BLUEZ5_UTILS only if all its reverse dependencies are selected Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-02-11 00:01:37 +01:00
select BR2_PACKAGE_BLUEZ5_UTILS if BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_4 \
&& BR2_TOOLCHAIN_HAS_SYNC_4
package/bluez_utils: drop package BlueZ 4.x is deprecated since a long time (BlueZ 5.x has been released in 2012) so drop it. For cwiid, sconeserver and ussp-push, replace bluez_utils by bluez5_utils. All other packages already support bluez5_utils so just drop bluez_utils. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-01-12 23:08:39 +01:00
help
The bluez-utils (BlueZ 4.x) package was removed as it is
deprecated since a long time. As an alternative, the
bluez5-utils (BlueZ 5.x) has been automatically selected in
your configuration.
package/gadgetfs-test: remove package Remove gadgetfs-test as gadgetfs has been deprecated in favour of functionfs. Signed-off-by: Mark Corbin <mark@dibsco.co.uk> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-03 15:40:57 +01:00
config BR2_PACKAGE_GADGETFS_TEST
bool "gadgetfs-test was removed"
select BR2_LEGACY
help
The gadgetfs-test package was removed. Gadgetfs has been
deprecated in favour of functionfs. Consider using
gadget-tool (gt) instead.
package/fis: remove package Remove fis as RedBoot hasn't been updated for over 10 years. Signed-off-by: Mark Corbin <mark@dibsco.co.uk> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-02-03 14:57:26 +01:00
config BR2_PACKAGE_FIS
bool "fis was removed"
select BR2_LEGACY
help
The fis package was removed.
package/{refpolicy,libsepol}: move policy version selection from refpolicy to libsepol Currently, a user sets a policy version via the refpolicy package. Having the option here has a few disadvantages: - The Refpolicy package is not technically needed to use SELinux. - When building a modular policy, Refpolicy will ignore the version string and build the highest version possible which will cause libsemanage to possibly fail when loading the policy. Specifying a manual policy version in /etc/selinux/semanage.conf forces libsemanage to load a specific policy version, which fixes the above issue. However, because refpolicy currently defines the policy version, libsemanage does not have a way to determine the policy version, as refpolicy is not a dependency of libsemanage. To work around these limitations, move the policy version number selection to libsepol, as a system using SELinux always requires this library. Signed-off-by: Adam Duskett <aduskett@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-02-03 14:29:49 +01:00
config BR2_PACKAGE_REFPOLICY_POLICY_VERSION
string "refpolicy policy version"
help
The refpolicy policy version option has been moved to the
libsepol package.
config BR2_PACKAGE_REFPOLICY_POLICY_VERSION_WRAP
bool
default y if BR2_PACKAGE_REFPOLICY_POLICY_VERSION != ""
select BR2_LEGACY
package/celt051: drop package Remove celt051 package as celt has been merged into the IETF Opus codec and is now obsolete (see http://celt-codec.org/). The only reverse dependency of celt051 is spice. Opus support on spice has been added upstream 6 years ago with: https://gitlab.freedesktop.org/spice/spice/commit/ce9b714137a767b81f2d3c40b5f3ce0d5cf70fc8 Spice disabled celt by default since version 0.14.1 and: https://gitlab.freedesktop.org/spice/spice-common/commit/72b0d603e128cd3af15974fe6b3e4b56ea9c6f34 Spice evens error out, by default, if Opus is missing but not explicitly disabeld since: https://gitlab.freedesktop.org/spice/spice-common/commit/f5224738425a7e97e1c32ea85bb3b243e50d4e22 This will also fix a static build failure on spice with celt051 and opus. Fixes: - http://autobuild.buildroot.org/results/96c786f85d35f33508e9c71778043d16b87f72cd Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> [yann.morin.1998@free.fr: slight rephrasing in legacy help] Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-24 21:09:31 +01:00
config BR2_PACKAGE_CELT051
bool "celt051 package was removed"
select BR2_LEGACY
select BR2_PACKAGE_OPUS
help
The celt051 package was removed as it is now obsolete since
the CELT codec has been merged into the IETF Opus codec. As
a result, the opus package has been automatically selected
in your configuration.
package/wireguard: change to the wireguard-tools package With the kernel support for WireGuard getting mainlined, the upstream repo has been split in a wireguard-tools repo for the userspace tooling and wireguard-linux-compat for the kernel side (for 3.10+ legacy kernels). So rename the package to wireguard-tools, use the new upstream and drop the kernel module handling. Also add Config.in.legacy handling for existing users. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-09 10:16:18 +01:00
config BR2_PACKAGE_WIREGUARD
bool "wireguard package renamed"
depends on BR2_TOOLCHAIN_HEADERS_AT_LEAST_3_10
select BR2_LEGACY
package/wireguard-linux-compat: new package With the kernel support for WireGuard getting mainlined, the upstream repo has been split in a wireguard-tools repo for the userspace tooling and wireguard-linux-compat for the kernel side (for 3.10+ legacy kernels). Add a wireguard-linux-compat for the compatibility out-of-tree kernel module, and update the Config.in.legacy handling to use it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-09 10:16:19 +01:00
select BR2_PACKAGE_WIREGUARD_LINUX_COMPAT if BR2_LINUX_KERNEL
package/wireguard: change to the wireguard-tools package With the kernel support for WireGuard getting mainlined, the upstream repo has been split in a wireguard-tools repo for the userspace tooling and wireguard-linux-compat for the kernel side (for 3.10+ legacy kernels). So rename the package to wireguard-tools, use the new upstream and drop the kernel module handling. Also add Config.in.legacy handling for existing users. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-09 10:16:18 +01:00
select BR2_PACKAGE_WIREGUARD_TOOLS
help
package/wireguard-linux-compat: new package With the kernel support for WireGuard getting mainlined, the upstream repo has been split in a wireguard-tools repo for the userspace tooling and wireguard-linux-compat for the kernel side (for 3.10+ legacy kernels). Add a wireguard-linux-compat for the compatibility out-of-tree kernel module, and update the Config.in.legacy handling to use it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-09 10:16:19 +01:00
The wireguard package has been renamed to wireguard-tools
for the userspace tooling and wireguard-linux-compat for the
kernel side for legacy (<5.6) kernels to match upstream.
package/wireguard: change to the wireguard-tools package With the kernel support for WireGuard getting mainlined, the upstream repo has been split in a wireguard-tools repo for the userspace tooling and wireguard-linux-compat for the kernel side (for 3.10+ legacy kernels). So rename the package to wireguard-tools, use the new upstream and drop the kernel module handling. Also add Config.in.legacy handling for existing users. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-09 10:16:18 +01:00
package/perl-net-ping: remove it Net::Ping is a Perl core module (ie. bundled with perl) Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-08 16:10:41 +01:00
config BR2_PACKAGE_PERL_NET_PING
bool "perl-net-ping was removed"
select BR2_LEGACY
help
Net::Ping is a Perl core module (ie. bundled with perl).
package/perl-mime-base64: remove it MIME::Base64 is a Perl core module (ie. bundled with perl) Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-08 16:10:40 +01:00
config BR2_PACKAGE_PERL_MIME_BASE64
bool "perl-mime-base64 was removed"
select BR2_LEGACY
help
MIME::Base64 is a Perl core module (ie. bundled with perl).
package/perl-digest-md5: remove it Digest::MD5 is a Perl core module (ie. bundled with perl) Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2020-01-08 16:10:38 +01:00
config BR2_PACKAGE_PERL_DIGEST_MD5
bool "perl-digest-md5 was removed"
select BR2_LEGACY
help
Digest::MD5 is a Perl core module (ie. bundled with perl).
package/erlang-p1-iconv: remove package This package was a dependency to ejabberd-18.09. It is not anymore use by any package nor maintain upstream, so remove it. Signed-off-by: Johan Oudinet <johan.oudinet@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2020-01-06 17:11:15 +01:00
config BR2_PACKAGE_ERLANG_P1_ICONV
bool "erlang-p1-iconv has been removed"
select BR2_LEGACY
help
The erlang-p1-iconv package was no longer used by ejabberd,
and was no longer maintained upstream, so it was removed.
package/linux-headers: drop support for 5.3.x headers The 5.3.x series is now EOL so remove the option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2020-01-04 16:56:50 +01:00
config BR2_KERNEL_HEADERS_5_3
bool "kernel headers version 5.3.x are no longer supported"
select BR2_LEGACY
help
Version 5.3.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/python-scapy3k: remove package Scapy3k is deprecated since Scapy supports Python 3. Scapy should be used instead. See https://bugs.busybox.net/show_bug.cgi?id=12376 Signed-off-by: Gabriel Potter <gabriel@potter.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-12-04 00:28:32 +01:00
config BR2_PACKAGE_PYTHON_SCAPY3K
bool "python-scapy3k is replaced by python-scapy"
select BR2_LEGACY
select BR2_PACKAGE_PYTHON_SCAPY
help
python-scapy3k has been deprecated, since python-scapy has
gained Python 3 support. Use BR2_PACKAGE_PYTHON_SCAPY
instead.
package/binutils: remove version 2.30 Now that binutils 2.33.1 has been introduced, and we have moved to 2.32 as the default version, it is time to drop support for binutils 2.30. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-11-30 16:17:52 +01:00
config BR2_BINUTILS_VERSION_2_30_X
bool "binutils version 2.30 support removed"
select BR2_LEGACY
help
Support for binutils version 2.30 has been removed. The
current default version (2.31 or later) has been selected
instead.
package/rpi-userland: bump version to 5070cb7f - rebased 0003-Disable-Werror-everywhere.patch - remove vcfiled support (upstream removed, see [1]) [1] https://github.com/raspberrypi/userland/commit/f00a1189b9f8246dc24c45985de599c50b8c62a5 Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-11-09 10:45:18 +01:00
config BR2_PACKAGE_RPI_USERLAND_START_VCFILED
bool "rpi-userland start vcfiled was removed"
select BR2_LEGACY
help
The vcfiled support was removed upstream.
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
config BR2_PACKAGE_TI_SGX_KM_AM335X
bool "ti-sgx-km AM335X option removed"
select BR2_LEGACY
select BR2_PACKAGE_TI_SGX_KM
help
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
config BR2_PACKAGE_TI_SGX_KM_AM437X
bool "ti-sgx-km AM437X option removed"
select BR2_LEGACY
help
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
config BR2_PACKAGE_TI_SGX_KM_AM4430
bool "ti-sgx-km AM4430 option removed"
select BR2_LEGACY
help
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
config BR2_PACKAGE_TI_SGX_KM_AM5430
bool "ti-sgx-km AM5430 option removed"
select BR2_LEGACY
help
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
package/wpa_supplicant: security bump version to 2.9 Fixes https://w1.fi/security/2019-6/ Removed patch applied upstream: http://w1.fi/cgit/hostap/commit/?id=f2973fa39d6109f0f34969e91551a98dc340d537 Removed all other upstream patches which are included in this release. Release notes: http://lists.infradead.org/pipermail/hostap/2019-April/039979.html http://lists.infradead.org/pipermail/hostap/2019-August/040373.html Support for the old dbus interface was removed upstream: http://w1.fi/cgit/hostap/commit/?id=6a8dee76d4090287c016680c009b1334e01b5fbd Removed Config.in option, removed _NEW from remaining dbus option, select BR2_PACKAGE_DBUS when needed and added Config.in.legacy options. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-25 21:28:43 +02:00
comment "Legacy options removed in 2019.11"
legacy: add missing entry for openvmtools' procps removal Commit 2be4232d98 removed the config option for openvmtools' procps support, but forgot to add it to the legacy menu. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2019-11-10 21:14:47 +01:00
config BR2_PACKAGE_OPENVMTOOLS_PROCPS
Config.in.legacy: fix small typo Fix small typo: oenvmtools -> openvmtools Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2019-11-10 21:41:51 +01:00
bool "openvmtools' procps support was removed"
legacy: add missing entry for openvmtools' procps removal Commit 2be4232d98 removed the config option for openvmtools' procps support, but forgot to add it to the legacy menu. Signed-off-by: Yann E. MORIN <yann.morin.1998@free.fr>
2019-11-10 21:14:47 +01:00
select BR2_LEGACY
help
Upstream stopped supporting this option a while ago.
package/alljoyn*: Remove the Alljoyn framework packages The upstream Alljoyn project is dead since the AllSeen Alliance merged with the Open Connectivity Foundation back in 2016. No other package depends on Alljoyn, so it can be removed. Signed-off-by: Titouan Christophe <titouan.christophe@railnova.eu> [Peter: fixup legacy option text] Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-10-31 18:37:21 +01:00
config BR2_PACKAGE_ALLJOYN
bool "alljoyn was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_BASE
bool "alljoyn-base was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_BASE_CONTROLPANEL
bool "alljoyn-base control panel was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_BASE_NOTIFICATION
bool "alljoyn-base notification was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_BASE_ONBOARDING
bool "alljoyn-base onboarding was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_TCL_BASE
bool "alljoyn-tcl-base was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
config BR2_PACKAGE_ALLJOYN_TCL
bool "alljoyn-tcl was removed"
select BR2_LEGACY
help
The alljoyn framework is dead
toolchain: expose BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS for all toolchain types This patch extends the "copy extra GCC libraries to target" feature to also work for internal toolchains. The variable has been renamed to be BR2_TOOLCHAIN_EXTRA_LIBS and the configuration option moved under the generic toolchain package. For external toolchains, the step that does the copy is still in the copy_toolchain_lib_root() helper which copies from the sysroot to the target. For the internal toolchain, the host gcc-final package does a post install hook to copy the libraries from the toolchain build folders to both the sysroot and target(!static). Examples where this can be useful is for adding debug libraries to the target like the GCC libsanitizer (libasan/liblsan/...). Cc: Markus Mayer <mmayer@broadcom.com> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-10-27 21:59:02 +01:00
config BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS
string "toolchain-external extra libs option has been renamed"
help
The option BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS has
been renamed to BR2_TOOLCHAIN_EXTRA_LIBS.
config BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS_WRAP
bool
default y if BR2_TOOLCHAIN_EXTRA_EXTERNAL_LIBS != ""
select BR2_LEGACY
package/python-pysnmp-apps: remove package The package was renamed to snmpclitools and is no longer maintained. Signed-off-by: Asaf Kahlon <asafka7@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-10-09 19:24:20 +02:00
config BR2_PACKAGE_PYTHON_PYSNMP_APPS
bool "python-pysnmp-apps was removed"
select BR2_LEGACY
select BR2_PACKAGE_SNMPCLITOOLS
help
Following upstream changes, the python-pysnmp-apps package
has been removed, and snmpclitools should be used as a
replacement.
package/linux-headers: drop support for 5.2.x headers The 5.2.x series is now EOL so remove the option and add legacy handling for it. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-10-18 05:59:53 +02:00
config BR2_KERNEL_HEADERS_5_2
bool "kernel headers version 5.2.x are no longer supported"
select BR2_LEGACY
help
Version 5.2.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
boot/riscv-pk: Remove obselete bootloader The RISCV Proxy Kernel (AKA BBL) isn't being used by most distros so has very limited testing. It has been replaced by OpenSBI and been deprecated for awhile, so let's just remove it. Signed-off-by: Alistair Francis <alistair.francis@wdc.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-10-08 18:32:19 +02:00
config BR2_TARGET_RISCV_PK
bool "riscv-pk was removed"
select BR2_LEGACY
help
The RISC-V Proxy Kernel (pk) and Berkley Boot Loader (BBL)
have been replaced with OpenSBI.
package/sqlite: bump version to 3.30.0 Release notes: https://www.sqlite.org/releaselog/3_30_0.html Changed Config.in option from stat3 to stat4 https://www.sqlite.org/compile.html#enable_stat3 "This option used to cause the ANALYZE command to collect index histogram data in the sqlite_stat3 table. But that functionality was superceded by SQLITE_ENABLE_STAT4 as of SQLite version 3.8.1 (2013-10-17). The SQLITE_ENABLE_STAT3 compile-time option continued to be supported through version 3.29.0 (2019-07-10) but has now become a no-op." Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-10-06 11:22:31 +02:00
config BR2_PACKAGE_SQLITE_STAT3
bool "sqlite stat3 support was removed"
select BR2_LEGACY
help
Upstream removed the support for stat3.
package/linux-headers: drop support for 5.1.x headers The 5.1.x series is now EOL and 5.3.x has been added, so remove the option and add legacy handling for it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-10-01 23:25:22 +02:00
config BR2_KERNEL_HEADERS_5_1
bool "kernel headers version 5.1.x are no longer supported"
select BR2_LEGACY
help
Version 5.1.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/devmem2: remove package It was here just for backwards compatibility and is not used by any package or board after commits 59856480b6 packages/devmem2: remove from all board configurations 2f6e3eae55 package/ti-gfx: do not use devmem2 in script There are address casting issues with 32bit access on a 64bit bus (like on the SoC FPGA ARM processors) with this tool. The Busybox version of devmem is the most up to date and supports quadword access. Fixes: https://bugs.busybox.net/show_bug.cgi?id=10171 Signed-off-by: Carlos Santos <unixmania@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-14 12:29:57 +02:00
config BR2_PACKAGE_DEVMEM2
bool "devmem2 package was removed"
select BR2_LEGACY
help
Use the the Busybox devmem utility, instead, which provides
the same functionality.
package/ustr: remove package This package was only used by libsemanage, but it is no longer used since SELinux 2.7, so drop it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-22 11:06:23 +02:00
config BR2_PACKAGE_USTR
bool "ustr package removed"
select BR2_LEGACY
help
The 'ustr' package was only used by SELinux libsemanage, but
since SELinux 2.7, ustr is no longer used. Therefore, we
removed this package from Buildroot.
package/kodi-screensaver-planestate: remove package This package is incompatible with Kodi 18.x, configure is broken: CMake Error at output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/share/kodi/cmake/AddonHelpers.cmake:197 (message): "@ADDON_DEPENDS@" not found in addon.xml.in. This package is also not part of the upstream binary repo: https://github.com/xbmc/repo-binary-addons Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-21 21:28:08 +02:00
config BR2_PACKAGE_KODI_SCREENSAVER_PLANESTATE
bool "kodi-screensaver-planestate package was removed"
select BR2_LEGACY
help
This package is incompatible with Kodi 18.x.
package/kodi-visualisation-waveforhue: remove package This package is incompatible with Kodi 18.x, configure is broken: CMake Error at output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/share/kodi/cmake/AddonHelpers.cmake:197 (message): "@ADDON_DEPENDS@" not found in addon.xml.in. For details read PR 2857 of https://github.com/LibreELEC/LibreELEC.tv Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-21 21:28:07 +02:00
config BR2_PACKAGE_KODI_VISUALISATION_WAVEFORHUE
bool "kodi-visualisation-waveforhue package was removed"
select BR2_LEGACY
help
This package is incompatible with Kodi 18.x.
package/kodi-audiodecoder-opus: remove package This package is incompatible with Kodi 18.x, configure is broken: CMake Error at output/host/x86_64-buildroot-linux-uclibc/sysroot/usr/share/kodi/cmake/AddonHelpers.cmake:197 (message): "@ADDON_DEPENDS@" not found in addon.xml.in. This package is also not part of the upstream binary repo: https://github.com/xbmc/repo-binary-addons Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-21 21:28:06 +02:00
config BR2_PACKAGE_KODI_AUDIODECODER_OPUS
bool "kodi-audiodecoder-opus package was removed"
select BR2_LEGACY
help
This package is incompatible with Kodi 18.x.
package/mesa3d: rename OSMesa option This option is renamed in order to match the naming used by the meson buildsystem. Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-20 18:38:38 +02:00
config BR2_PACKAGE_MESA3D_OSMESA
bool "mesa OSMesa option renamed"
package/mesa3d: add OSMesa classic needs dri swrast The meson build system now check if dri swrast is enabled when OSMesa classic is enabled. See: https://cgit.freedesktop.org/mesa/mesa/commit/?id=cbbd5bb889a2c271a504c379f36a7cb717a85af4 Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-20 18:38:39 +02:00
select BR2_PACKAGE_MESA3D_OSMESA_CLASSIC if BR2_PACKAGE_MESA3D_DRI_DRIVER_SWRAST
package/mesa3d: rename OSMesa option This option is renamed in order to match the naming used by the meson buildsystem. Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-09-20 18:38:38 +02:00
select BR2_LEGACY
help
The option was renamed in order to match the naming used
by the meson buildsystem.
package/hostapd: remove support for Realtek drivers After hostapd update to 2.9, the patch provided no longer works, although applies. Moreover, AP support for Realtek chips is broken anyway in kernels > 4.9. Signed-off-by: Alexander Mukhin <alexander.i.mukhin@gmail.com> [Thomas: add Config.in.legacy handling] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-09-06 12:21:00 +02:00
config BR2_PACKAGE_HOSTAPD_DRIVER_RTW
bool "hostapd rtl871xdrv driver removed"
select BR2_LEGACY
help
Since the update of hostapd to 2.9, the patch provided for
the rtl871xdrv no longer works, although it
applies. Moreover, AP support for Realtek chips is broken
anyway in kernels > 4.9. Therefore, this option has been
removed.
package/wpa_supplicant: security bump version to 2.9 Fixes https://w1.fi/security/2019-6/ Removed patch applied upstream: http://w1.fi/cgit/hostap/commit/?id=f2973fa39d6109f0f34969e91551a98dc340d537 Removed all other upstream patches which are included in this release. Release notes: http://lists.infradead.org/pipermail/hostap/2019-April/039979.html http://lists.infradead.org/pipermail/hostap/2019-August/040373.html Support for the old dbus interface was removed upstream: http://w1.fi/cgit/hostap/commit/?id=6a8dee76d4090287c016680c009b1334e01b5fbd Removed Config.in option, removed _NEW from remaining dbus option, select BR2_PACKAGE_DBUS when needed and added Config.in.legacy options. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-25 21:28:43 +02:00
config BR2_PACKAGE_WPA_SUPPLICANT_DBUS_NEW
bool "new dbus support option in wpa_supplicant was renamed"
select BR2_PACKAGE_WPA_SUPPLICANT_DBUS if BR2_TOOLCHAIN_HAS_THREADS
select BR2_LEGACY
help
The new dbus support option was renamed.
config BR2_PACKAGE_WPA_SUPPLICANT_DBUS_OLD
bool "old dbus support in wpa_supplicant was removed"
select BR2_LEGACY
help
The old dbus support was removed.
package/gdb: remove gdb 8.0.x 8.3 is around and 8.2 is the default version, so drop 8.0. Keep 7.12 which is the latest version that doesn't requires C++11 support. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-06-05 14:40:16 +02:00
comment "Legacy options removed in 2019.08"
boot/ts4800-mrboot: remove package Since the ts4800_defconfig has been removed, the ts4800-mrboot package is no longer useful, therefore we drop it. Cc: Patrick Keroulas <patrick.keroulas@savoirfairelinux.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-29 14:00:46 +02:00
config BR2_TARGET_TS4800_MBRBOOT
bool "ts4800-mbrboot package was removed"
select BR2_LEGACY
help
The defconfig for the TS4800 platform has been removed, so
the ts4800-mbrboot package, containing the boot code for
this specific platform has been removed as welL.
package/libamcodec: remove package Package is not needed anymore after support for odroid2c was dropped: https://git.buildroot.net/buildroot/commit/?id=b80712a16ae3deb65331a7923aa878e13e2e66b6 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-10 12:59:55 +02:00
config BR2_PACKAGE_LIBAMCODEC
bool "liamcodec package was removed"
select BR2_LEGACY
help
Support for odroidc2 based systems was removed, making the
libamcodec package useless.
package/odroid-scripts: remove package Package is not needed anymore after support for odroid2c was dropped: https://git.buildroot.net/buildroot/commit/?id=b80712a16ae3deb65331a7923aa878e13e2e66b6 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-10 12:59:54 +02:00
config BR2_PACKAGE_ODROID_SCRIPTS
bool "odroid-scripts package was removed"
select BR2_LEGACY
help
Support for odroidc2 based systems was removed, making the
odroid-scripts package useless.
package/odroid-mali: remove package Package is not needed anymore after support for odroid2c was dropped: https://git.buildroot.net/buildroot/commit/?id=b80712a16ae3deb65331a7923aa878e13e2e66b6 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-10 12:59:53 +02:00
config BR2_PACKAGE_ODROID_MALI
bool "odroid-mali package was removed"
select BR2_LEGACY
help
Support for odroidc2 based systems was removed, making the
odroid-mali package useless.
package/kodi: remove AMLogic support Kodi 19 will remove specific support for AMLogic: https://github.com/xbmc/xbmc/pull/16043 Also buildroot dropped support for the odroid2c defconfig: https://git.buildroot.net/buildroot/commit/?id=b80712a16ae3deb65331a7923aa878e13e2e66b6 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-08-10 12:59:52 +02:00
config BR2_PACKAGE_KODI_PLATFORM_AML
bool "Kodi AMLogic support was removed"
select BR2_LEGACY
help
Support for AMLogic was removed due to the removal of the
odroidc2 defconfig.
package/gcc: remove version 6.5 gcc 9.1 is around, gcc 8.3 is the default version, so drop 6.5 in order to reduce the gcc choice. Keep gcc 5.5 since it still used by beaglebone_qt5_defconfig. Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-02 15:09:36 +02:00
config BR2_GCC_VERSION_6_X
bool "gcc 6.x support removed"
select BR2_LEGACY
help
Support for gcc version 6.x has been removed. The current
default version (8.x or later) has been selected instead.
package/gcc: remove gcc 4.9 In order to reduce the number of choice in gcc selection, remove the gcc 4.9 version. This version was kept due to libstdc++ ABI-incompatible changes and other build issues with kernel and bootloader as reported by Arnout [1]. Since then, gcc 4.9 is not supported any more since glibc 2.29 [2] and recent kernel and bootloaders has been fixed to use more recent compiler version. [1] http://lists.busybox.net/pipermail/buildroot/2017-June/194374.html [2] https://www.sourceware.org/ml/libc-alpha/2019-01/msg00723.html Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-02 15:09:35 +02:00
config BR2_GCC_VERSION_4_9_X
bool "gcc 4.9.x support removed"
select BR2_LEGACY
help
Support for gcc version 4.9.x has been removed. The current
default version (8.x or later) has been selected instead.
package/gdb: remove gdb 7.12.1 gdb 7.12.1 was released on 21 Jan 2017 [1] and is the last version that doesn't requires a C++11 compiler. Since Buildroot now support three other gdb versions (8.1, 8.2 and 8.3), reduce the number of choice by dropping 7.12.1. Remove BR2_PACKAGE_GDB_NEEDS_CXX11 symbol since it's not useful anymore. [1] https://lists.gnu.org/archive/html/info-gnu/2017-01/msg00009.html Signed-off-by: Romain Naour <romain.naour@smile.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-08-02 15:09:31 +02:00
config BR2_GDB_VERSION_7_12
bool "gdb 7.12.x has been removed"
select BR2_LEGACY
help
The 7.12.x version of gdb has been removed. Use a newer
version instead.
package/x11r7/xapp_mkfontdir: remove package app_mkfontscale now includes the mkfontdir script: https://lists.x.org/archives/xorg-announce/2019-March/002988.html Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-06-02 12:45:19 +02:00
config BR2_PACKAGE_XAPP_MKFONTDIR
bool "mkfontdir is now included in xapp_mkfontscale"
select BR2_PACKAGE_XAPP_MKFONTSCALE
select BR2_LEGACY
help
xapp_mkfontscale now includes the mkfontdir script previously
distributed separately for compatibility with older X11
versions.
package/gdb: remove gdb 8.0.x 8.3 is around and 8.2 is the default version, so drop 8.0. Keep 7.12 which is the latest version that doesn't requires C++11 support. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-06-05 14:40:16 +02:00
config BR2_GDB_VERSION_8_0
bool "gdb 8.0.x has been removed"
select BR2_LEGACY
help
The 8.0.x version of gdb has been removed. Use a newer
version instead.
Config.in.legacy: add legacy entry for 4.20.x headers Commit b3bba8e4254 (package/linux-headers: drop support 4.20 headers) removed the option for 4.20.x kernel headers, but forgot to add a legacy option. Add that now. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-06-18 13:57:31 +02:00
config BR2_KERNEL_HEADERS_4_20
bool "kernel headers version 4.20.x are no longer supported"
select BR2_LEGACY
help
Version 4.20.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/linux-headers: drop support for 5.x headers The 5.0.x series is now EOL and vulnerable to the "TCP SACK PANIC" issue. Drop support for it in linux-headers. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-06-18 13:57:33 +02:00
config BR2_KERNEL_HEADERS_5_0
bool "kernel headers version 5.0.x are no longer supported"
select BR2_LEGACY
help
Version 5.0.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/gst-plugins-bad: remove apexsink support apexsink does not build with OpenSSL 1.1.x so remove this option especially because there is no more apexsink option in gstreamer1 (since version 1.12) Fixes: - http://autobuild.buildroot.org/results/a29e8a8509190fc4b3c419dae2301cf72a601f62 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-05 23:01:04 +01:00
comment "Legacy options removed in 2019.05"
arch/csky: remove BR2_CSKY_DSP option The DSP extention is in fact no longer used for C-SKY, nor supported by C-SKY gcc, so we remove it. Signed-off-by: Guo Ren <ren_guo@c-sky.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [Thomas: split from the VDSP patch, add Config.in.legacy] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:38:59 +02:00
config BR2_CSKY_DSP
bool "C-SKY DSP support removed"
select BR2_LEGACY
help
Config.in.legacy: fix check-package warnings Fixes the following warnings: Config.in.legacy:153: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in) Config.in.legacy:154: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in) Config.in.legacy:155: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in) Config.in.legacy:156: help text: <tab><2 spaces><62 chars> (http://nightly.buildroot.org/#writing-rules-config-in) which were introduced in commit 55c642287819a062d52e7f290c76ada778772fba ("arch/csky: remove BR2_CSKY_DSP option") Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-06-01 14:44:41 +02:00
C-SKY DSP instruction support for ck810 / ck807 was removed,
as it was no longer supported in C-SKY gcc. Perhaps the VDSP
instructions should be used instead, using the BR2_CSKY_VDSP
option.
arch/csky: remove BR2_CSKY_DSP option The DSP extention is in fact no longer used for C-SKY, nor supported by C-SKY gcc, so we remove it. Signed-off-by: Guo Ren <ren_guo@c-sky.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> [Thomas: split from the VDSP patch, add Config.in.legacy] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-05-31 08:38:59 +02:00
package/gstreamer1/gst1-plugins-{base, good, bad, ugly}: bump to 1.16.0 Group these patches because of several changes to the plugin packages. Changes: - Remove upstreamed patches: - 0001-fdkaacenc-Remove-MODE_2_1.patch - 0002-fdkaacdec-Use-WAV-channel-mapping-instead-of-interle.patch - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_COMPOSITOR to Config.in.legacy as this plugin is moved to gst1-plugins-base. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA to Config.in.legacy as this the plugin is now removed. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_OPENCV to Config.in.legacy as the plugin now requires opencv3 with the bgsegm opencv_contrib module, which is not in Buildroot. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_STEREO to Config.in.legacy as this plugin is merged with the audiofx plugin in gst1-plugins-good. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_VCD to Config.in.legacy as this plugin is removed. - Remove COPYING.LIB from gst-plugins-base mk file and hash file as it no longer exists. - Add BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_COMPOSITOR to gst1-plugins-base.mk - Add BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_OVERLAYCOMPOSITION to gst1-plugins-base. - Add mjpegtools to the dependencies of BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_MPEG2ENC - Remove BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA because it now depends on the package dssim which isn't available in Buildroot. - Remove upstream patch 0001-gstrtspconnection-Security-loophole-making-heap-over.patch Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-05-02 17:16:16 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_COMPOSITOR
bool "compositor moved to gst1-plugins-base"
select BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_COMPOSITOR
select BR2_LEGACY
help
The gst1-plugins-bad compositor plugin has moved
to gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA
bool "gst-plugins-bad IQA option was removed"
Config.in.legacy: fix check-package warning Order is type, depends, select. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-05-05 23:55:11 +02:00
select BR2_LEGACY
package/gstreamer1/gst1-plugins-{base, good, bad, ugly}: bump to 1.16.0 Group these patches because of several changes to the plugin packages. Changes: - Remove upstreamed patches: - 0001-fdkaacenc-Remove-MODE_2_1.patch - 0002-fdkaacdec-Use-WAV-channel-mapping-instead-of-interle.patch - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_COMPOSITOR to Config.in.legacy as this plugin is moved to gst1-plugins-base. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA to Config.in.legacy as this the plugin is now removed. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_OPENCV to Config.in.legacy as the plugin now requires opencv3 with the bgsegm opencv_contrib module, which is not in Buildroot. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_STEREO to Config.in.legacy as this plugin is merged with the audiofx plugin in gst1-plugins-good. - Add BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_VCD to Config.in.legacy as this plugin is removed. - Remove COPYING.LIB from gst-plugins-base mk file and hash file as it no longer exists. - Add BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_COMPOSITOR to gst1-plugins-base.mk - Add BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_OVERLAYCOMPOSITION to gst1-plugins-base. - Add mjpegtools to the dependencies of BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_MPEG2ENC - Remove BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA because it now depends on the package dssim which isn't available in Buildroot. - Remove upstream patch 0001-gstrtspconnection-Security-loophole-making-heap-over.patch Signed-off-by: Adam Duskett <Aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-05-02 17:16:16 +02:00
help
The gst1-plugins-bad IQA option was removed.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_OPENCV
bool "gst-plugins-bad opencv option was removed"
select BR2_LEGACY
help
The gst1-plugins-bad opencv option was removed because
buildroot does not have the opencv_contrib package which
is required for the bgsegm module which gst1-plugins-bad
now requires along with opencv3.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_STEREO
bool "stereo was merged into audiofx in gst1-plugins-good"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_GOOD_PLUGIN_AUDIOFX
help
The gst1-plugins-bad stereo plugin has merged with the
gst1-plugins-base audiofx plugin.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_VCD
bool "gst-plugins-bad vcd plugin was removed."
select BR2_LEGACY
help
The gst1-plugins-bad vcd plugin was removed.
package/lunit: remove package it was replaced by its fork lunitx which supports all versions of Lua. Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-04-03 15:06:09 +02:00
config BR2_PACKAGE_LUNIT
bool "lunit package removed"
select BR2_LEGACY
select BR2_PACKAGE_LUA_LUNITX
help
The lunit package was removed in favor of its fork lunitx,
which supports all versions of Lua.
package/ffmpeg: bump to version 4.1.2 FFserver is not supported anymore Remove patch 0001: fixed upstream in cae6f806a6367c7760ab6ed059d343d4a8eebd56 Remove patch 0002 to 0004: accepted upstream Signed-off-by: Louis-Paul Cordier <lpdev@cordier.org> [Bernd: bump to 4.1.2] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-23 13:28:18 +01:00
config BR2_PACKAGE_FFMPEG_FFSERVER
bool "ffmpeg ffserver removed"
select BR2_LEGACY
help
On July 10th, 2016, ffserver program has been dropped.
package/libump: remove package This library was previously a part of sunxi-mali. Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-06 16:24:26 +01:00
config BR2_PACKAGE_LIBUMP
bool "libump package removed"
select BR2_LEGACY
help
The libump package was removed, it was only used as a
dependency of sunxi-mali, which itself was removed.
package/sunxi-mali: remove package The package sunxi-mali-mainline is available for recent kernels. Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-06 16:24:25 +01:00
config BR2_PACKAGE_SUNXI_MALI
bool "sunxi-mali package removed"
select BR2_LEGACY
package/sunxi-mali-utgard: rename from sunxi-mali-mainline This package provides Mali libraries for Sunxi Mali Utgard GPUs. The trailing -mainline is historical and was used at a time when there was two packages providing these libraries. The "non-upstream" package has been removed some time ago so before adding new packages bringing support for other ARM Mali GPU versions or implementations, rename sunxi-mali-mainline into sunxi-mali-utgard. Add a legacy entry. Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com> Signed-off-by: Giulio Benetti <giulio.benetti@benettiengineering.com> [Giulio: rebase on master. Rename SUNXI_MALI_MAINLINE_REV to SUNXI_MALI_UTGARD_REV in sunxi-mali-mailine-driver.mk and BR2_PACKAGE_SUNXI_MALI_MAINLINE to BR2_PACKAGE_SUNXI_UTGARD in sunxi-mali-mainline-driver/Config.in to respect bisectability] Tested-by: Luca Ceresoli <luca@lucaceresoli.net> [Build tested only] Reviewed-by: Luca Ceresoli <luca@lucaceresoli.net> [Arnout: also update existing select in Config.in.legacy] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2021-11-05 23:17:56 +01:00
select BR2_PACKAGE_SUNXI_MALI_UTGARD
package/sunxi-mali: remove package The package sunxi-mali-mainline is available for recent kernels. Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-06 16:24:25 +01:00
help
The sunxi-mali package was removed, as the
sunxi-mali-mainline package replaces it for mainline
kernels on Allwinner platforms.
package/binutils: remove version 2.29 We are back with 3 binutils version in Buildroot. Now CFI support is always present for NIOSII. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-13 00:08:39 +01:00
config BR2_BINUTILS_VERSION_2_29_X
bool "binutils version 2.29 support removed"
select BR2_LEGACY
help
Support for binutils version 2.29 has been removed. The
current default version (2.31 or later) has been selected
instead.
package/binutils: remove version 2.28 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-13 00:08:38 +01:00
config BR2_BINUTILS_VERSION_2_28_X
bool "binutils version 2.28 support removed"
select BR2_LEGACY
help
Support for binutils version 2.28 has been removed. The
current default version (2.31 or later) has been selected
instead.
package/gst-plugins-bad: remove apexsink support apexsink does not build with OpenSSL 1.1.x so remove this option especially because there is no more apexsink option in gstreamer1 (since version 1.12) Fixes: - http://autobuild.buildroot.org/results/a29e8a8509190fc4b3c419dae2301cf72a601f62 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-03-05 23:01:04 +01:00
config BR2_PACKAGE_GST_PLUGINS_BAD_PLUGIN_APEXSINK
bool "gst-plugins-bad apexsink option removed"
select BR2_LEGACY
help
The gst-plugins-bad apexsink option was removed.
package/lua: remove 5.2.x version At this time : - Lua 5.3.5 will be the last one of its serie. - Lua 5.4 is up coming (lua-5.4.0-work2 is already available). - Lua 5.2.4 was released on 2015. For various reasons in the Lua ecosystem, the Lua 5.1 will stay. On BR, Lua 5.3 is the default version since 2016.02. So, the serie which could be removed is the 5.2.x. We could wait some days for other user feedback. Note: see discussion when 5.3.x was introduced : http://lists.busybox.net/pipermail/buildroot/2015-January/117638.html Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-12-02 11:25:06 +01:00
comment "Legacy options removed in 2019.02"
package/qt: remove package Qt4 has been marked obsolete for close to 1 year, since commit 3538b5fb10 (qt: mark as obsolete) and is no longer supported upstream since December 2015: https://blog.qt.io/blog/2015/05/26/qt-4-8-7-released/ So now finally remove it as the in tree users have been removed. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:58 +01:00
config BR2_PACKAGE_QT
bool "qt package removed"
select BR2_LEGACY
help
The qt package was removed.
package/qtuio: remove package The qtuio package uses the obsolete qt4 package, which we are about to remove, so remove qtuio as well. CC: Stephan Hoffmann <sho@relinux.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:52 +01:00
config BR2_PACKAGE_QTUIO
bool "qtuio package removed"
select BR2_LEGACY
help
The qtuio package was removed.
package/pinentry: remove qt4 option The qt4 option uses the obsolete qt4 package, which we are about to remove, so remove the pinentry-qt4 option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:51 +01:00
config BR2_PACKAGE_PINENTRY_QT4
bool "pinentry-qt4 option removed"
select BR2_LEGACY
help
The pinentry-qt4 option was removed.
package/poppler: remove qt option The qt option uses the obsolete qt4 package, which we are about to remove, so remove the poppler qt option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:50 +01:00
config BR2_PACKAGE_POPPLER_QT
bool "poppler qt option removed"
select BR2_LEGACY
help
The poppler qt option was removed.
package/opencv3: remove qt backend option The qt backend option uses the obsolete qt4 package, which we are about to remove, so remove the qt backend option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:49 +01:00
config BR2_PACKAGE_OPENCV3_WITH_QT
bool "opencv3 qt backend option removed"
select BR2_LEGACY
help
The opencv3 qt backend option was removed.
package/opencv: remove qt backend option The qt backend option uses the obsolete qt4 package, which we are about to remove, so remove the qt backend option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:48 +01:00
config BR2_PACKAGE_OPENCV_WITH_QT
bool "opencv qt backend option removed"
select BR2_LEGACY
help
The opencv qt backend option was removed.
package/amd-catalyst: remove control center option The control center option uses the obsolete qt4 package, which we are about to remove, so remote the cccle option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:47 +01:00
config BR2_PACKAGE_AMD_CATALYST_CCCLE
bool "catalyst control center option removed"
select BR2_LEGACY
help
The AMD Catalyst Control Center option was removed.
package/sdl: remove qtopia video driver option The qtopia option uses the obsolete qt4 package, which we are about to remove, to remove the qtopia option as well. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> [Arnout: move the enable-qtopia=no option to the beginning] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:46 +01:00
config BR2_PACKAGE_SDL_QTOPIA
bool "sdl qtopia video driver option removed"
select BR2_LEGACY
help
The SDL QTopia video driver option was removed.
package/python-pyqt: remove package The python-pyqt package uses the obsolete qt4 package, which we are about to remove, so remove python-pyqt as well. CC: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2019-02-06 15:10:44 +01:00
config BR2_PACKAGE_PYTHON_PYQT
bool "python-pyqt package removed"
select BR2_LEGACY
help
The python-pyqt package was removed. Consider python-pyqt5
instead.
package/luacrypto: remove package Fixes: http://autobuild.buildroot.net/results/afd/afdc598b80356a8301d890232466de421f7779d5/ Luacrypto fails to build with openssl 1.1.x. The package has not seen any functional changes since it was added in 2013 and has no reverse dependencies. The upstream repository (https://github.com/starius/luacrypto) explicitly states: this project is deprecated, use luaossl So remove the package. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-02-05 21:03:09 +01:00
config BR2_PACKAGE_LUACRYPTO
bool "luacrypto package removed"
select BR2_LEGACY
help
The luacrypto package was removed. Consider luaossl instead.
package/tn5250: remove package The latest (0.17.4) tn5250 release is from 2008, doesn't build with openssl 1.1.x and was dropped from Debian in 2011 because nobody cared to maintain it: https://packages.qa.debian.org/t/tn5250.html Given all of that, it is unlikely to be used much, so remove it. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Acked-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-02-05 20:01:09 +01:00
config BR2_PACKAGE_TN5250
bool "tn5250 package removed"
select BR2_LEGACY
help
The tn5250 package was removed.
package/boost: bump to version 1.69.0 - Remove fifth patch (already in version) - Remove BR2_PACKAGE_BOOST_SIGNALS as signals is now removed. Its removal was announced in 1.68 and its deprecation was announced in 1.54. Users are encouraged to use Signals2 instead. Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-13 18:43:16 +01:00
config BR2_PACKAGE_BOOST_SIGNALS
bool "Boost signals removed"
select BR2_LEGACY
help
Its removal was announced in boost 1.68 and its deprecation
was announced in 1.54. Users are encouraged to use Signals2
instead.
package/fftw: remove as regular package fftw is no longer a package: only fftw-single, fftw-double, fftw-long-double and fftw-quad are. fftw.mk only contains some common definitions that are used by the different fftw variants. The old BR2_PACKAGE_FFTW_PRECISION_* options, which are no longer used anywhere, are moved to Config.in.legacy. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Gwenhael Goavec-Merou <gwenhael.goavec-merou@trabucayre.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2019-01-21 14:51:10 +01:00
config BR2_PACKAGE_FFTW_PRECISION_SINGLE
bool "single"
select BR2_LEGACY
select BR2_PACKAGE_FFTW_SINGLE
help
This option has been removed in favor of
BR2_PACKAGE_FFTW_SINGLE.
config BR2_PACKAGE_FFTW_PRECISION_DOUBLE
bool "double"
select BR2_LEGACY
select BR2_PACKAGE_FFTW_DOUBLE
help
This option has been removed in favor of
BR2_PACKAGE_FFTW_DOUBLE.
config BR2_PACKAGE_FFTW_PRECISION_LONG_DOUBLE
bool "long double"
depends on !(BR2_TOOLCHAIN_BUILDROOT_UCLIBC && \
(BR2_arm || BR2_mips || BR2_mipsel))
select BR2_LEGACY
select BR2_PACKAGE_FFTW_LONG_DOUBLE
help
This option has been removed in favor of
BR2_PACKAGE_FFTW_LONG_DOUBLE.
config BR2_PACKAGE_FFTW_PRECISION_QUAD
bool "quad"
depends on (BR2_i386 || BR2_x86_64) && BR2_USE_WCHAR
select BR2_LEGACY
select BR2_PACKAGE_FFTW_QUAD
help
This option has been removed in favor of
BR2_PACKAGE_FFTW_QUAD.
package/lua: remove 5.2.x version At this time : - Lua 5.3.5 will be the last one of its serie. - Lua 5.4 is up coming (lua-5.4.0-work2 is already available). - Lua 5.2.4 was released on 2015. For various reasons in the Lua ecosystem, the Lua 5.1 will stay. On BR, Lua 5.3 is the default version since 2016.02. So, the serie which could be removed is the 5.2.x. We could wait some days for other user feedback. Note: see discussion when 5.3.x was introduced : http://lists.busybox.net/pipermail/buildroot/2015-January/117638.html Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-12-02 11:25:06 +01:00
config BR2_PACKAGE_LUA_5_2
bool "Lua 5.2.x version removed"
select BR2_LEGACY
help
The Lua 5.2.x version was removed.
package/lua: properly handle legacy for removed version Commit "297613f1c7 package/lua: remove 5.2.x version" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2019.02, following the example described in the beginning of the file. Cc: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:34 +01:00
# Note: BR2_PACKAGE_LUA_5_2 is still referenced from package/lua/Config.in
package/lua: remove 5.2.x version At this time : - Lua 5.3.5 will be the last one of its serie. - Lua 5.4 is up coming (lua-5.4.0-work2 is already available). - Lua 5.2.4 was released on 2015. For various reasons in the Lua ecosystem, the Lua 5.1 will stay. On BR, Lua 5.3 is the default version since 2016.02. So, the serie which could be removed is the 5.2.x. We could wait some days for other user feedback. Note: see discussion when 5.3.x was introduced : http://lists.busybox.net/pipermail/buildroot/2015-January/117638.html Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-12-02 11:25:06 +01:00
system cfg: remove mkpasswd MD5 format option As SHA256 is now default, removing weak MD5 option. C libraries now all support the SHA methods. glibc 2.7+ uclibc (bdd8362a88 package/uclibc: defconfig: enable sha-256...) musl 1.1.14+ One issue this would prevent, is a host tool issue with a FIPS enabled system where weak ciphers/methods are disabled. It seems the crypt(3) call is impacted by /proc/sys/crypto/fips_enabled (per crypt(3) man page). It results in mkpasswd returning "(EPERM) crypt failed." Rather then create a Buildroot host dependency check, this patch removes the potential corner case from being selected. Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-12-06 03:06:29 +01:00
config BR2_TARGET_GENERIC_PASSWD_MD5
bool "target passwd md5 format support has been removed"
select BR2_LEGACY
help
The default has been moved to SHA256 and all C libraries
now support that method by default
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
comment "Legacy options removed in 2018.11"
boot/xloader: remove package U-boot has provided SPL support as a viable replacement for the 2nd stage bootloader on TI platforms. The X-loader project hasn't had a commit in the log since 12-05-2011. (https://gitorious.org/x-loader/x-loader) Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-09-20 23:54:24 +02:00
config BR2_TARGET_XLOADER
bool "xloader has been removed"
select BR2_LEGACY
help
The package has been removed as u-boot SPL provides
similar functionality
package/tidsp-binaries: remove package The suit of TI OMAP3 dsp tools/libraries are being removed as the upstream projects are no longer active. Suggest using Buildroot 2018.02.x LTS if the feature is still required. Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-15 18:46:44 +02:00
config BR2_PACKAGE_TIDSP_BINARIES
bool "tidsp-binaries package removed"
select BR2_LEGACY
help
The tidsp-binaries package was removed.
package/dsp-tools: remove package The suit of TI OMAP3 dsp tools/libraries are being removed as the upstream projects are no longer active. The dsp-tools package used the tidsp-binaries package. Suggest using Buildroot 2018.02.x LTS if the feature is still required. Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-15 18:46:43 +02:00
config BR2_PACKAGE_DSP_TOOLS
bool "dsp-tools package removed"
select BR2_LEGACY
help
The dsp-tools package was removed.
package/gst-dsp: remove package The suit of TI OMAP3 dsp tools/libraries are being removed as the upstream projects are no longer active. The gst-dsp package used the tidsp-binaries package. Suggest using Buildroot 2018.02.x LTS if the feature is still required. Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-15 18:46:42 +02:00
config BR2_PACKAGE_GST_DSP
bool "gst-dsp package removed"
select BR2_LEGACY
help
The gst-dsp package was removed.
bootutils: drop package As suggested by Romain Naour during review of patch 976582 (https://patchwork.ozlabs.org/patch/976582), drop bootutils as "upstream is dead since 2009" and "BootUtils is a collection of utilities to facilitate booting of modern Kernel 2.6 based systems" Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-09-30 16:02:06 +02:00
config BR2_PACKAGE_BOOTUTILS
bool "bootutils package removed"
select BR2_LEGACY
help
The bootutils package was removed.
package/expedite: remove package As noticed with the last version bump [1], expedite is not actively maintained by upstream [2]. [1] http://lists.busybox.net/pipermail/buildroot/2018-September/231763.html [2] https://sourceforge.net/p/enlightenment/mailman/message/36428571 Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-09-30 14:55:46 +02:00
config BR2_PACKAGE_EXPEDITE
bool "expedite package has been removed"
select BR2_LEGACY
help
expedite is not actively maintained anymore.
https://sourceforge.net/p/enlightenment/mailman/message/36428571
package/{mesa3d, mesa3d-headers}: bump version to 18.2.0 Upstream unconditionally enabled floating-point textures: https://cgit.freedesktop.org/mesa/mesa/commit/?h=18.2&id=66673bef941af344314fe9c91cad8cd330b245eb x11 support depends on xlib_libXrandr now: https://cgit.freedesktop.org/mesa/mesa/commit/configure.ac?h=18.2&id=3f960c1338713d317ce6463be68cee162c968d8d Removed 0003-musl-time-h.patch, patch was applied upstream. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-09-10 18:30:00 +02:00
config BR2_PACKAGE_MESA3D_OPENGL_TEXTURE_FLOAT
bool "mesa3d opengl texture float option removed"
select BR2_LEGACY
help
mesa3d now unconditionally enables floating-point textures,
as the corresponding patent has expired.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
config BR2_KERNEL_HEADERS_4_10
bool "kernel headers version 4.10.x are no longer supported"
select BR2_LEGACY
help
Version 4.10.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
config BR2_KERNEL_HEADERS_4_11
bool "kernel headers version 4.11.x are no longer supported"
select BR2_LEGACY
help
Version 4.11.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
config BR2_KERNEL_HEADERS_4_12
bool "kernel headers version 4.12.x are no longer supported"
select BR2_LEGACY
help
Version 4.12.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
config BR2_KERNEL_HEADERS_4_13
bool "kernel headers version 4.13.x are no longer supported"
select BR2_LEGACY
help
Version 4.13.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
config BR2_KERNEL_HEADERS_4_15
bool "kernel headers version 4.15.x are no longer supported"
select BR2_LEGACY
help
Version 4.15.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 4.{10,11,12,13,15} versions These versions received their last updated more than three months ago and are no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: select an older kernel headers (4.9) rather than a newer one (4.14) in the legacy handling of 4.10, 4.11, 4.12 and 4.13.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-08-24 20:41:33 +02:00
package/linux-headers: really drop the 4.17 choice Currently, the build fails when the kernel headers 4.17 are selected: package/linux-headers/linux-headers.mk:149: *** LINUX_HEADERS_SITE cannot be empty when LINUX_HEADERS_SOURCE is not. Stop. This is caused by an hickup during the last merge of the next branch, where the value for 4.17 got dropped from BR2_DEFAULT_KERNEL_HEADERS, but the choice entry was left in. The correct fix against that hickup would be to restore the 4.17 value. But since 4.17 is no longer maintained, the proper fix is to really drop 4.17 altogether. For good this time! ;-) Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Peter Korsgaard <peter@korsgaard.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:30 +02:00
config BR2_KERNEL_HEADERS_4_17
bool "kernel headers version 4.17.x are no longer supported"
select BR2_LEGACY
help
Version 4.17.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
libnftnl: drop useless BR2_PACKAGE_LIBNFTNL_XML Commit fa0d1ebff99 (libnftnl: bump to version 1.0.9) removed the mxml dependency. Remove the redundant BR2_PACKAGE_LIBNFTNL_XML config symbol as well. Cc: Yegor Yefremov <yegorslists@googlemail.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-11-16 07:40:43 +01:00
config BR2_PACKAGE_LIBNFTNL_XML
bool "libnftl no longer supports XML output"
select BR2_LEGACY
help
libnftnl removed integration with libmxml.
package/linux-headers: drop obsolete 3.2.x / 4.{1, 16, 18}.x versions According to https://www.kernel.org/category/releases.html, these kernel versions are no longer supported, so drop them now that we have added 4.20.x Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2019-01-02 14:52:45 +01:00
config BR2_KERNEL_HEADERS_3_2
bool "kernel headers version 3.2.x are no longer supported"
select BR2_LEGACY
help
Version 3.2.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
config BR2_KERNEL_HEADERS_4_1
bool "kernel headers version 4.1.x are no longer supported"
select BR2_LEGACY
help
Version 4.1.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
config BR2_KERNEL_HEADERS_4_16
bool "kernel headers version 4.16.x are no longer supported"
select BR2_LEGACY
help
Version 4.16.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
config BR2_KERNEL_HEADERS_4_18
bool "kernel headers version 4.18.x are no longer supported"
select BR2_LEGACY
help
Version 4.18.x of the Linux kernel headers are no longer
maintained upstream and are now removed.
package/gdb: remove 7.10 Now that 8.1 has been added and 8.0 is the default version, let's remove the old 7.10 release. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-06-24 15:53:09 +02:00
###############################################################################
comment "Legacy options removed in 2018.08"
package/docker-engine: split docker-{cli, engine}, bump to v18.09.0 Docker upstream has split the Docker daemon and CLI into separate codebases: - github.com/docker/engine: daemon, "dockerd" binary - github.com/docker/cli: "docker" command line interface This commit splits the docker-engine package into docker-engine and docker-cli. Conveniently, the Docker project has begun maintaining two separate release-tagged repositories for the CLI and daemon as of v18.06-ce-rc1. Previous versions were tagged in a common "docker-ce" repository which makes compilation awkward for Buildroot, especially due to some limitations in the new Go package infrastructure. Docker repositories "engine" and "cli" recently started tagging releases. Select the latest stable release, v18.09.0. The CLI is no longer automatically included with the engine. Users will need to select BR2_PACKAGE_DOCKER_CLI to produce a both docker and dockerd target binaries. Docker CLI can be statically compiled. This enables usage of the system docker client binary to access the parent daemon API from within containers, where shared libraries are not available. While at it, drop the useless host-go dependency from docker-engine, since it's already added by the golang-package infrastructure. Signed-off-by: Christian Stewart <christian@paral.in> [Thomas: drop the host-go dependency from both docker-cli and docker-engine] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-11-27 09:56:55 +01:00
config BR2_PACKAGE_DOCKER_ENGINE_STATIC_CLIENT
bool "docker-engine static client option renamed"
select BR2_LEGACY
select BR2_PACKAGE_DOCKER_CLI_STATIC
help
BR2_PACKAGE_DOCKER_ENGINE_STATIC_CLIENT has been renamed to
BR2_PACKAGE_DOCKER_CLI_STATIC, following the package split of
docker-engine and docker-cli.
package/x11r7/xproto_*: mass removal The new package xorgproto will combine and replace all current xproto_* packages. For details read https://lists.x.org/archives/xorg-announce/2018-February/002835.html After switching to xorgproto the old xproto_* packages are removed. Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-07-21 16:16:44 +02:00
config BR2_PACKAGE_XPROTO_APPLEWMPROTO
bool "xproto-applewmproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-applewmproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_BIGREQSPROTO
bool "xproto-bigreqsproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-bigreqsproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_COMPOSITEPROTO
bool "xproto-compositeproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-compositeproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_DAMAGEPROTO
bool "xproto-dameproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-dameproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_DMXPROTO
bool "xproto-dmxproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-dmxproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_DRI2PROTO
bool "xproto-dri2proto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-dri2proto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_DRI3PROTO
bool "xproto-dri3proto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-dri3proto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_FIXESPROTO
bool "xproto-fixesproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-fixesproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_FONTCACHEPROTO
bool "xproto-fontcacheproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-fontcacheproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_FONTSPROTO
bool "xproto-fontsproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-fontsproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_GLPROTO
bool "xproto-glproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-glproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_INPUTPROTO
bool "xproto-inputproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-inputproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_KBPROTO
bool "xproto-kbproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-kbproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_PRESENTPROTO
bool "xproto-presentproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-presentproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_RANDRPROTO
bool "xproto-randrproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-randrproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_RECORDPROTO
bool "xproto-recordproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-recordproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_RENDERPROTO
bool "xproto-renderproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-renderproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_RESOURCEPROTO
bool "xproto-resourceproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-resourceproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_SCRNSAVERPROTO
bool "xproto-scrnsaverprot package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-scrnsaverprot package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_VIDEOPROTO
bool "xproto-videoproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-videoproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_WINDOWSWMPROTO
bool "xproto-windowswmproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-windowswmproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XCMISCPROTO
bool "xproto-xcmiscproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xcmiscproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XEXTPROTO
bool "xproto-xextproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xextproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XF86BIGFONTPROTO
bool "xproto-xf86bigfontproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xf86bigfontproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XF86DGAPROTO
bool "xproto-xf86dgaproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xf86dgaproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XF86DRIPROTO
bool "xproto-xf86driproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xf86driproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XF86VIDMODEPROTO
bool "xproto-xf86vidmodeproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xf86vidmodeproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XINERAMAPROTO
bool "xproto-xineramaproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xineramaproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XPROTO
bool "xproto-xproto package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xproto package has been replaced by the
xorgproto package, which combines all xproto_* packages.
config BR2_PACKAGE_XPROTO_XPROXYMANAGEMENTPROTOCOL
bool "xproto-xproxymanagementprotocol package replaced by xorgproto"
select BR2_LEGACY
select BR2_PACKAGE_XORGPROTO
help
The xproto-xproxymanagementprotocol package has been
replaced by the xorgproto package, which combines all
xproto_* packages.
gst1-plugins-${base, good, bad, ugly}: bump to 1.14.1 These are grouped together because several plugins have been re-arranged and there is no way to individually update each plugin package. Changes: Add the following to gst1-plugins-base and remove them from plugins-bad: - opengl - gles2 - glx - egl - x11 - dispmanx - audiomixer Add the following to plugins-good and remove them from plugins-ugly: - lame - mpg123 moved --disable-qt from plugins-bad to plugins-good Delete upstream patch from gst1-plugins-ugly ([1]) - 0001-x264enc-fix-build-with-newer-x264-with-support-for-m.patch Also add hashes for the license files. [1] https://cgit.freedesktop.org/gstreamer/gst-plugins-ugly/commit/?id=83c38dc44622611c1f67dd26e4cb383c5aef90f6 Signed-off-by: Adam Duskett <aduskett@gmail.com> [Upate to 1.14.1] [Removed legacy lame/mpg123 option, add Config.in.legacy handling] [remove leftover audiomixer handling from gst1-plugins-bad.mk] [remove upstream patch from gst1-plugins-ugly] Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-06-24 00:35:22 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_OPENGL
bool "gst1-plugins-bad opengl option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_OPENGL
help
The opengl option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_GLES2
bool "gst1-plugins-bad gles2 option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_GLES2
help
The gles2 option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_GLX
bool "gst1-plugins-bad glx option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_GLX
help
The glx option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_EGL
bool "gst1-plugins-bad egl option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_EGL
help
The egl option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_X11
bool "gst1-plugins-bad x11 option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_X11
help
The x11 option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_WAYLAND
bool "gst1-plugins-bad wayland option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_WAYLAND
help
The wayland option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_LIB_OPENGL_DISPMANX
bool "gst1-plugins-bad dispmanx option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_LIB_OPENGL_DISPMANX
help
The dispmanx option has been moved from gst1-plugins-mad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_AUDIOMIXER
bool "gst1-plugins-bad audiomixer option moved to gst1-plugins-base"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BASE_PLUGIN_AUDIOMIXER
help
The audiomixer option has been moved from gst1-plugins-bad to
gst1-plugins-base.
config BR2_PACKAGE_GST1_PLUGINS_UGLY_PLUGIN_LAME
bool "gst1-plugins-ugly lame option moved to gst1-plugins-good"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_GOOD_PLUGIN_LAME
help
The lame option has been moved from gst1-plugins-ugly to
gst1-plugins-good.
config BR2_PACKAGE_GST1_PLUGINS_UGLY_PLUGIN_MPG123
bool "gst1-plugins-ugly mpg123 option moved to gst1-plugins-good"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_GOOD_PLUGIN_MPG123
help
The mpg123 option has been moved from gst1-plugins-ugly to
gst1-plugins-good.
package/gdb: remove 7.11 Now that 8.1 has been added and 8.0 is the default version, let's remove the old 7.11 release. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-06-24 15:53:10 +02:00
config BR2_GDB_VERSION_7_11
bool "gdb 7.11 has been removed"
select BR2_LEGACY
help
The 7.11 version of gdb has been removed. Use a newer version
instead.
package/gdb: remove 7.10 Now that 8.1 has been added and 8.0 is the default version, let's remove the old 7.10 release. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-06-24 15:53:09 +02:00
config BR2_GDB_VERSION_7_10
bool "gdb 7.10 has been removed"
select BR2_LEGACY
help
The 7.10 version of gdb has been removed. Use a newer version
instead.
gnupg2: don't preserve the old gpg2 executable name Commit e82fadab236a (gnupg2: bump to version 2.2.0) added a configure option to keep the old 'gpg2' executable name to avoid conflict with the gnupg package. It turns out that gnupg depends on !BR2_PACKAGE_GNUPG2 since commit 2cadb26e6d4 (gnupg: make gnupg and gnupg2 mutually exclusive). Drop this configure option. Rename the config option that controls the removal of gpgv2, now gpgv, to match the new name. Add legacy config symbol handling. Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-14 13:02:38 +01:00
###############################################################################
package/kodi-adsp-*: remove packages Those packages are unmaintained and not in a working state, for details see https://github.com/xbmc/xbmc/pull/13723 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 15:58:08 +02:00
comment "Legacy options removed in 2018.05"
libmediaart: rename options to have proper prefix Options should be prefixed by BR2_PACKAGE_LIBMEDIAART and not BR2_PACKAGE_MEDIAART, but package was using both prefixes. This was found as default symbol was defined as BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE (correct prefix), but symbol was actually BR2_PACKAGE_MEDIAART_BACKEND_NONE). This commit therefore renames the incorrectly named options, and adds Config.in.legacy handling. Since the options are part of a choice, the legacy handling cannot select the new options, and is only here to inform the user. Fixes: c443830a57 libmediaart: new package Signed-off-by: Petr Vorel <petr.vorel@gmail.com> [Thomas: improve commit log, add Config.in.legacy handling] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:36 +02:00
config BR2_PACKAGE_MEDIAART_BACKEND_NONE
bool "libmediaart none backend option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_MEDIAART_BACKEND_NONE has been renamed to
BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE
config BR2_PACKAGE_MEDIAART_BACKEND_GDK_PIXBUF
bool "libmediaart gdk-pixbuf backend option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_MEDIAART_BACKEND_GDK_PIXBUF has been renamed to
BR2_PACKAGE_LIBMEDIAART_BACKEND_GDK_PIXBUF
Config.in.legacy: fix typo on BR2_PACKAGE_MEDIAART_BACKEND_QT Currently using this minimal .config: BR2_PACKAGE_MEDIAART_BACKEND_GDK_PIXBUF=y triggers: *** Legacy options removed in 2018.05 *** [ ] libmediaart none backend option renamed (NEW) [*] libmediaart gdk-pixbuf backend option renamed [*] libmediaart qt backend option renamed Commit "8553b39887 libmediaart: rename options to have proper prefix", part of the 2018.05 release had a copy&paste error. As stated in the beginning of the file: The oldest symbols will be removed again after about two years. But while we carry these legacy symbols, let's fix the typo. Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:17 +01:00
config BR2_PACKAGE_MEDIAART_BACKEND_QT
libmediaart: rename options to have proper prefix Options should be prefixed by BR2_PACKAGE_LIBMEDIAART and not BR2_PACKAGE_MEDIAART, but package was using both prefixes. This was found as default symbol was defined as BR2_PACKAGE_LIBMEDIAART_BACKEND_NONE (correct prefix), but symbol was actually BR2_PACKAGE_MEDIAART_BACKEND_NONE). This commit therefore renames the incorrectly named options, and adds Config.in.legacy handling. Since the options are part of a choice, the legacy handling cannot select the new options, and is only here to inform the user. Fixes: c443830a57 libmediaart: new package Signed-off-by: Petr Vorel <petr.vorel@gmail.com> [Thomas: improve commit log, add Config.in.legacy handling] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:36 +02:00
bool "libmediaart qt backend option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_MEDIAART_BACKEND_QT has been renamed to
BR2_PACKAGE_LIBMEDIAART_BACKEND_QT
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
config BR2_PACKAGE_TI_SGX_AM335X
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
bool "ti-sgx-km AM335X option removed"
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
select BR2_LEGACY
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
select BR2_PACKAGE_TI_SGX_KM
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
help
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
config BR2_PACKAGE_TI_SGX_AM437X
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
bool "ti-sgx-km AM437X option removed"
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
select BR2_LEGACY
help
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
config BR2_PACKAGE_TI_SGX_AM4430
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
bool "ti-sgx-km AM4430 option removed"
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
select BR2_LEGACY
help
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
config BR2_PACKAGE_TI_SGX_AM5430
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
bool "ti-sgx-km AM5430 option removed"
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
select BR2_LEGACY
help
package/ti-sgx-km: properly handle legacy for removed options Commit "c38b5566fe package/ti-sgx-{km, um, demos}: bump to latest TI version", added in release 2020.02, removed some options that were previously renamed in release 2018.05. Update the legacy entry for 2018.05 and add the corresponding legacy entries for 2020.02. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:35 +01:00
Starting from buildroot release 2020.02, the buildroot package
only supports the target am335x.
ti-sgx-km: rename options to have proper prefix The sub-options of the ti-sgx-km package had their name option prefixed by BR2_PACKAGE_TI_SGX, while the prefix should be BR2_PACKAGE_TI_SGX_KM. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:35 +02:00
janus-gateway: rename options to have proper prefix The sub-options of the janus-gateway package had their name option prefixed by BR2_PACKAGE_JANUS, while the prefix should be BR2_PACKAGE_JANUS_GATEWAY. This commit fixes that, and adds the necessary Config.in.legacy handling. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:34 +02:00
config BR2_PACKAGE_JANUS_AUDIO_BRIDGE
bool "janus-gateway audio-bridge option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_AUDIO_BRIDGE
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_AUDIO_BRIDGE has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_AUDIO_BRIDGE.
config BR2_PACKAGE_JANUS_ECHO_TEST
bool "janus-gateway echo-test option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_ECHO_TEST
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_ECHO_TEST has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_ECHO_TEST.
config BR2_PACKAGE_JANUS_RECORDPLAY
bool "janus-gateway recordplay option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_RECORDPLAY
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_RECORDPLAY has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_RECORDPLAY.
config BR2_PACKAGE_JANUS_SIP_GATEWAY
bool "janus-gateway sip-gateway option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_SIP_GATEWAY
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_SIP_GATEWAY has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_SIP_GATEWAY.
config BR2_PACKAGE_JANUS_STREAMING
bool "janus-gateway streaming option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_STREAMING
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_STREAMING has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_STREAMING.
config BR2_PACKAGE_JANUS_TEXT_ROOM
bool "janus-gateway text-room option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_TEXT_ROOM
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_TEXT_ROOM has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_TEXT_ROOM.
config BR2_PACKAGE_JANUS_VIDEO_CALL
bool "janus-gateway video-call option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_VIDEO_CALL
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_VIDEO_CALL has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_VIDEO_CALL.
config BR2_PACKAGE_JANUS_VIDEO_ROOM
bool "janus-gateway video-room option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_VIDEO_ROOM
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_VIDEO_ROOM has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_VIDEO_ROOM.
config BR2_PACKAGE_JANUS_MQTT
bool "janus-gateway mqtt option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_MQTT
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_MQTT has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_MQTT.
config BR2_PACKAGE_JANUS_RABBITMQ
bool "janus-gateway rabbitmq option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_RABBITMQ
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_RABBITMQ has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_RABBITMQ.
config BR2_PACKAGE_JANUS_REST
bool "janus-gateway rest option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_REST
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_REST has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_REST.
config BR2_PACKAGE_JANUS_UNIX_SOCKETS
bool "janus-gateway unix-sockets option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_UNIX_SOCKETS
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_UNIX_SOCKETS has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_UNIX_SOCKETS.
config BR2_PACKAGE_JANUS_WEBSOCKETS
bool "janus-gateway websockets option renamed"
select BR2_LEGACY
select BR2_PACKAGE_JANUS_GATEWAY_WEBSOCKETS
help
For consistency reasons, the janus-gateway option
BR2_PACKAGE_JANUS_WEBSOCKETS has been renamed to
BR2_PACKAGE_JANUS_GATEWAY_WEBSOCKETS.
ipsec-tools: rename options to have proper prefix A number of options in the ipsec-tools package had their Config.in option prefixed by BR2_PACKAGE_IPSEC, while the prefix should be BR2_PACKAGE_IPSEC_TOOLS. This commit fixes that, and adds the necessary Config.in.legacy handling. Since those options are part of a choice, the legacy handling cannot select the new name of the options, so the legacy handling only informs the user of the rename. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:33 +02:00
config BR2_PACKAGE_IPSEC_SECCTX_DISABLE
bool "ipsec-tools security context disable option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_IPSEC_SECCTX_DISABLE was renamed to
BR2_PACKAGE_IPSEC_TOOLS_SECCTX_DISABLE.
config BR2_PACKAGE_IPSEC_SECCTX_ENABLE
bool "ipsec-tools SELinux security context enable option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_IPSEC_SECCTX_ENABLE was renamed to
BR2_PACKAGE_IPSEC_TOOLS_SECCTX_ENABLE.
config BR2_PACKAGE_IPSEC_SECCTX_KERNEL
bool "ipsec-tools kernel security context enable option renamed"
select BR2_LEGACY
help
For consistency reasons, the option
BR2_PACKAGE_IPSEC_SECCTX_KERNEL was renamed to
BR2_PACKAGE_IPSEC_TOOLS_SECCTX_KERNEL.
libftdi: rename option to have proper prefix The option name BR2_PACKAGE_LIBTFDI_CPP obviously had a typo: it should have been named BR2_PACKAGE_LIBFTDI_CPP, and add the necessary Config.in.legacy handling. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:32 +02:00
config BR2_PACKAGE_LIBTFDI_CPP
bool "libftdi C++ bindings option renamed"
select BR2_LEGACY
select BR2_PACKAGE_LIBFTDI_CPP
help
The option BR2_PACKAGE_LIBTFDI_CPP was renamed to
BR2_PACKAGE_LIBFTDI_CPP in order to fix a typo in the option
name.
jquery-ui-themes: rename options to have proper prefix The choice options to select the specific jquery-ui theme to install had a prefix of BR2_PACKAGE_JQUERY_UI_THEME_ instead of BR2_PACKAGE_JQUERY_UI_THEMES_. This commit fixes that, and adds Config.in.legacy handling. It's worth mentioning that since those options are part of a choice, the legacy handling cannot select the new name of the option: we can simply inform the user about the renaming. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:31 +02:00
config BR2_PACKAGE_JQUERY_UI_THEME_BLACK_TIE
bool "jquery-ui-themes option black-tie renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
black-tie theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_BLACK_TIE to
BR2_PACKAGE_JQUERY_UI_THEMES_BLACK_TIE.
config BR2_PACKAGE_JQUERY_UI_THEME_BLITZER
bool "jquery-ui-themes option blitzer renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
blitzer theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_BLITZER to
BR2_PACKAGE_JQUERY_UI_THEMES_BLITZER.
config BR2_PACKAGE_JQUERY_UI_THEME_CUPERTINO
bool "jquery-ui-themes option cupertino renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
cupertino theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_CUPERTINO to
BR2_PACKAGE_JQUERY_UI_THEMES_CUPERTINO.
config BR2_PACKAGE_JQUERY_UI_THEME_DARK_HIVE
bool "jquery-ui-themes option dark-hive renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
dark-hive theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_DARK_HIVE to
BR2_PACKAGE_JQUERY_UI_THEMES_DARK_HIVE.
config BR2_PACKAGE_JQUERY_UI_THEME_DOT_LUV
bool "jquery-ui-themes option dot-luv renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
dot-luv theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_DOT_LUV to
BR2_PACKAGE_JQUERY_UI_THEMES_DOT_LUV.
config BR2_PACKAGE_JQUERY_UI_THEME_EGGPLANT
bool "jquery-ui-themes option eggplant renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
eggplant theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_EGGPLANT to
BR2_PACKAGE_JQUERY_UI_THEMES_EGGPLANT.
config BR2_PACKAGE_JQUERY_UI_THEME_EXCITE_BIKE
bool "jquery-ui-themes option excite-bike renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
excite-bike theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_EXCITE_BIKE to
BR2_PACKAGE_JQUERY_UI_THEMES_EXCITE_BIKE.
config BR2_PACKAGE_JQUERY_UI_THEME_FLICK
bool "jquery-ui-themes option flick renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
flick theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_FLICK to
BR2_PACKAGE_JQUERY_UI_THEMES_FLICK.
config BR2_PACKAGE_JQUERY_UI_THEME_HOT_SNEAKS
bool "jquery-ui-themes option hot-sneaks renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
hot-sneaks theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_HOT_SNEAKS to
BR2_PACKAGE_JQUERY_UI_THEMES_HOT_SNEAKS.
config BR2_PACKAGE_JQUERY_UI_THEME_HUMANITY
bool "jquery-ui-themes option humanity renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
humanity theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_HUMANITY to
BR2_PACKAGE_JQUERY_UI_THEMES_HUMANITY.
config BR2_PACKAGE_JQUERY_UI_THEME_LE_FROG
bool "jquery-ui-themes option le-frog renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
le-frog theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_LE_FROG to
BR2_PACKAGE_JQUERY_UI_THEMES_LE_FROG.
config BR2_PACKAGE_JQUERY_UI_THEME_MINT_CHOC
bool "jquery-ui-themes option mint-choc renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
mint-choc theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_MINT_CHOC to
BR2_PACKAGE_JQUERY_UI_THEMES_MINT_CHOC.
config BR2_PACKAGE_JQUERY_UI_THEME_OVERCAST
bool "jquery-ui-themes option overcast renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
overcast theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_OVERCAST to
BR2_PACKAGE_JQUERY_UI_THEMES_OVERCAST.
config BR2_PACKAGE_JQUERY_UI_THEME_PEPPER_GRINDER
bool "jquery-ui-themes option pepper-grinder renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
pepper-grinder theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_PEPPER_GRINDER to
BR2_PACKAGE_JQUERY_UI_THEMES_PEPPER_GRINDER.
config BR2_PACKAGE_JQUERY_UI_THEME_REDMOND
bool "jquery-ui-themes option redmond renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
redmond theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_REDMOND to
BR2_PACKAGE_JQUERY_UI_THEMES_REDMOND.
config BR2_PACKAGE_JQUERY_UI_THEME_SMOOTHNESS
bool "jquery-ui-themes option smoothness renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
smoothness theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_SMOOTHNESS to
BR2_PACKAGE_JQUERY_UI_THEMES_SMOOTHNESS.
config BR2_PACKAGE_JQUERY_UI_THEME_SOUTH_STREET
bool "jquery-ui-themes option south-street renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
south-street theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_SOUTH_STREET to
BR2_PACKAGE_JQUERY_UI_THEMES_SOUTH_STREET.
config BR2_PACKAGE_JQUERY_UI_THEME_START
bool "jquery-ui-themes option start renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
start theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_START to
BR2_PACKAGE_JQUERY_UI_THEMES_START.
config BR2_PACKAGE_JQUERY_UI_THEME_SUNNY
bool "jquery-ui-themes option sunny renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
sunny theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_SUNNY to
BR2_PACKAGE_JQUERY_UI_THEMES_SUNNY.
config BR2_PACKAGE_JQUERY_UI_THEME_SWANKY_PURSE
bool "jquery-ui-themes option swanky-purse renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
swanky-purse theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_SWANKY_PURSE to
BR2_PACKAGE_JQUERY_UI_THEMES_SWANKY_PURSE.
config BR2_PACKAGE_JQUERY_UI_THEME_TRONTASTIC
bool "jquery-ui-themes option trontastic renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
trontastic theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_TRONTASTIC to
BR2_PACKAGE_JQUERY_UI_THEMES_TRONTASTIC.
config BR2_PACKAGE_JQUERY_UI_THEME_UI_DARKNESS
bool "jquery-ui-themes option ui-darkness renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
ui-darkness theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_UI_DARKNESS to
BR2_PACKAGE_JQUERY_UI_THEMES_UI_DARKNESS.
config BR2_PACKAGE_JQUERY_UI_THEME_UI_LIGHTNESS
bool "jquery-ui-themes option ui-lightness renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
ui-lightness theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_UI_LIGHTNESS to
BR2_PACKAGE_JQUERY_UI_THEMES_UI_LIGHTNESS.
config BR2_PACKAGE_JQUERY_UI_THEME_VADER
bool "jquery-ui-themes option vader renamed"
select BR2_LEGACY
help
For consistency reasons, the jquery-ui-themes option for the
vader theme has been renamed from
BR2_PACKAGE_JQUERY_UI_THEME_VADER to
BR2_PACKAGE_JQUERY_UI_THEMES_VADER.
bluez5_utils: rename options to have the proper suffix The bluez5_utils Config.in options had a bogus prefix: BR2_PACKAGE_BLUEZ5 instead of the expected BR2_PACKAGE_BLUEZ5_UTILS. This commit fixes that, and adds the appropriate Config.in.legacy handling. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-05-13 21:07:30 +02:00
config BR2_PACKAGE_BLUEZ5_PLUGINS_HEALTH
bool "bluez5-utils health plugin option renamed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_HEALTH
help
For consistency reasons, the option
BR2_PACKAGE_BLUEZ5_PLUGINS_HEALTH has been renamed to
BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_HEALTH.
config BR2_PACKAGE_BLUEZ5_PLUGINS_MIDI
bool "bluez5-utils midi plugin option renamed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_MIDI
help
For consistency reasons, the option
BR2_PACKAGE_BLUEZ5_PLUGINS_MIDI has been renamed to
BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_MIDI.
config BR2_PACKAGE_BLUEZ5_PLUGINS_NFC
bool "bluez5-utils nfc plugin option renamed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_NFC
help
For consistency reasons, the option
BR2_PACKAGE_BLUEZ5_PLUGINS_NFC has been renamed to
BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_NFC.
config BR2_PACKAGE_BLUEZ5_PLUGINS_SAP
bool "bluez5-utils sap plugin option renamed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SAP
help
For consistency reasons, the option
BR2_PACKAGE_BLUEZ5_PLUGINS_SAP has been renamed to
BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SAP.
config BR2_PACKAGE_BLUEZ5_PLUGINS_SIXAXIS
bool "bluez5-utils sixaxis plugin option renamed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SIXAXIS
help
For consistency reasons, the option
BR2_PACKAGE_BLUEZ5_PLUGINS_SIXAXIS has been renamed to
BR2_PACKAGE_BLUEZ5_UTILS_PLUGINS_SIXAXIS.
package/transmission: remove BR2_PACKAGE_TRANSMISSION_REMOTE Commit 6e223241e1bb58a27eb890291f9f5c1fcc6a0818 ("Add Transmission package"), which added the transmission package, introduced a BR2_PACKAGE_TRANSMISSION_REMOTE Config.in option, supposedly matching the --enable-remote/--disable-remote transmission option. However, transmission as of version 2.33 packaged by this initial commit, did not have a --enable-remote/--disable-remote option, and it was apparently never part of transmission. Therefore, this commit removes this useless option. Since the transmission-remote tool is automatically built when the daemon is enabled, the Config.in.legacy handling selects BR2_PACKAGE_TRANSMISSION_DAEMON. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-02 08:05:40 +02:00
config BR2_PACKAGE_TRANSMISSION_REMOTE
bool "transmission remote tool option removed"
select BR2_LEGACY
select BR2_PACKAGE_TRANSMISSION_DAEMON
help
Upstream does not provide a separate configure option for
the tool transmission-remote, it is built when the
transmission daemon has been enabled. Therefore, Buildroot
has automatically enabled BR2_PACKAGE_TRANSMISSION_DAEMON
for you.
libkcapi: split BR2_PACKAGE_LIBKCAPI_APPS Since commit https://github.com/smuellerDD/libkcapi/commit/af313accf18887b4f6dbd7306c2389ddf271c9b7, hasher test application depends on dlfcn.h. To avoid putting all apps under !BR2_STATIC_LIBS dependency, split BR2_PACKAGE_LIBKCAPI_APPS into several variables. Moreover, BR2_USE_MMU is only a dependency of BR2_PACKAGE_LIBKCAPI_TEST as other applications don't use fork. Finally, enc or dgst applications could be enabled in a next patch if needed. Fixes: - http://autobuild.buildroot.net/results/7c57f3025030eff41a5cde52759821249859caf1 Signed-off-by: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-07 00:09:01 +02:00
config BR2_PACKAGE_LIBKCAPI_APPS
bool "libkcapi test applications removed"
select BR2_LEGACY
select BR2_PACKAGE_LIBKCAPI_HASHER if !BR2_STATIC_LIBS
select BR2_PACKAGE_LIBKCAPI_RNGAPP
select BR2_PACKAGE_LIBKCAPI_SPEED
select BR2_PACKAGE_LIBKCAPI_TEST
help
Test applications (hasher, rng read, speed-test, test) now
have their own configuration options in the libkcapi menu.
package/mplayer: remove package This package causes numerous build errors. During the last hackaton it was decided to remove this package: http://lists.busybox.net/pipermail/buildroot/2018-April/217514.html Fixes http://autobuild.buildroot.net/results/bda/bda461391c9e02e313fda887b75099e619527a7a/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-01 09:10:17 +02:00
config BR2_PACKAGE_MPLAYER
bool "mplayer package removed"
select BR2_LEGACY
help
The mplayer package was removed.
config BR2_PACKAGE_MPLAYER_MPLAYER
bool "mplayer package removed"
select BR2_LEGACY
help
The mplayer package was removed.
config BR2_PACKAGE_MPLAYER_MENCODER
bool "mplayer package removed"
select BR2_LEGACY
help
The mplayer package was removed.
package/libplayer: remove mplayer support Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-05-01 09:10:14 +02:00
config BR2_PACKAGE_LIBPLAYER_MPLAYER
bool "mplayer support in libplayer removed"
select BR2_LEGACY
help
The mplayer package was removed.
iqvlinux: remove package This package contains a kernel module from Intel, which could only be used together with Intel userspace tools provided under NDA, which also come with the same kernel module. The copy of the kernel module available on SourceForge is only provided to comply with the GPLv2 requirement. Intel engineers were even surprised it even built and were not willing to make any effort to fix their tarball naming to contain a version number. Therefore, it does not make sense for Buildroot to provide such a package. See https://sourceforge.net/p/e1000/bugs/589/ for the discussion. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Acked-by: Carlos Santos <casantos@datacom.ind.br> Acked-by: Romain Naour <romain.naour@gmail.com> [Thomas: - remove double "only" noticed by Carlos - fix typo packaged -> package noticed by Romain - fix check-package warning noticed by Ricardo] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-04 18:00:09 +02:00
config BR2_PACKAGE_IQVLINUX
bool "iqvlinux package removed"
select BR2_LEGACY
help
This package contained a kernel module from Intel, which
could only be used together with Intel userspace tools
provided under NDA, which also come with the same kernel
module. The copy of the kernel module available on
SourceForge is provided only to comply with the GPLv2
requirement. Intel engineers were even surprised it even
built and were not willing to make any effort to fix their
tarball naming to contain a version number. Therefore, it
does not make sense for Buildroot to provide such a package.
See https://sourceforge.net/p/e1000/bugs/589/ for the
discussion.
arch: drop BR2_BINFMT_FLAT_SEP_DATA support This was only used by Blackfin, so there's no good reason to keep it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-05 21:50:18 +02:00
config BR2_BINFMT_FLAT_SEP_DATA
bool "binfmt FLAT with separate code and data removed"
select BR2_LEGACY
help
This FLAT binary format was only used on Blackfin, which has
been removed.
arch: remove Blackfin architecture The Blackfin architecture has for a long time been complicated to maintain, with poor support in upstream binutils/gcc. As of April 2018, the Blackfin architecture has been dropped from the upstream Linux kernel. Also, the Analog Device engineer who used to be in touch with the Buildroot community also privately said we should drop the support for this architecture, which Analog Devices is no longer using, promoting and maintaining. The BR2_BINFMT_FLAT_SEP_DATA option becomes unselectable, it will be removed in a future commit. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-05 21:50:17 +02:00
config BR2_bfin
bool "Blackfin architecture support removed"
select BR2_LEGACY
help
Following the removal of Blackfin support for the upstream
Linux kernel, Buildroot has removed support for this CPU
architecture.
package/kodi-adsp-*: remove packages Those packages are unmaintained and not in a working state, for details see https://github.com/xbmc/xbmc/pull/13723 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 15:58:08 +02:00
config BR2_PACKAGE_KODI_ADSP_BASIC
bool "kodi-adsp-basic package removed"
select BR2_LEGACY
help
kodi-adsp-basic is unmaintained
config BR2_PACKAGE_KODI_ADSP_FREESURROUND
bool "kodi-adsp-freesurround package removed"
select BR2_LEGACY
help
kodi-adsp-freesurround is unmaintained
###############################################################################
gnupg2: don't preserve the old gpg2 executable name Commit e82fadab236a (gnupg2: bump to version 2.2.0) added a configure option to keep the old 'gpg2' executable name to avoid conflict with the gnupg package. It turns out that gnupg depends on !BR2_PACKAGE_GNUPG2 since commit 2cadb26e6d4 (gnupg: make gnupg and gnupg2 mutually exclusive). Drop this configure option. Rename the config option that controls the removal of gpgv2, now gpgv, to match the new name. Add legacy config symbol handling. Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-14 13:02:38 +01:00
comment "Legacy options removed in 2018.02"
linux-headers: drop old unsupported 3.x versions These versions are very old and no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-01-29 22:48:25 +01:00
config BR2_KERNEL_HEADERS_3_4
bool "kernel headers version 3.4.x are no longer supported"
select BR2_LEGACY
help
Version 3.4.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 3.x versions These versions are very old and no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-01-29 22:48:25 +01:00
config BR2_KERNEL_HEADERS_3_10
bool "kernel headers version 3.10.x are no longer supported"
select BR2_LEGACY
help
Version 3.10.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 3.x versions These versions are very old and no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-01-29 22:48:25 +01:00
config BR2_KERNEL_HEADERS_3_12
bool "kernel headers version 3.12.x are no longer supported"
select BR2_LEGACY
help
Version 3.12.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: drop old unsupported 3.x versions These versions are very old and no longer supported according to https://www.kernel.org/category/releases.html, so drop them and add legacy entries. Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-01-29 22:48:25 +01:00
package/binutils: remove support for 2.27 Now that binutils 2.30 has been introduced, and we have moved to 2.29.1 as the default version, it is time to drop support for binutils 2.27. Also use xz-compressed tarball for all official supported version. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-01-29 23:39:41 +01:00
config BR2_BINUTILS_VERSION_2_27_X
bool "binutils version 2.27 support removed"
select BR2_LEGACY
help
Support for binutils version 2.27 has been removed. The
current default version (2.29 or later) has been selected
instead.
eeprog: remove package The i2c-tools package has adopted the code of eeprog. Cc: Matt Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2018-01-02 07:16:01 +01:00
config BR2_PACKAGE_EEPROG
bool "eeprog package removed"
select BR2_LEGACY
select BR2_PACKAGE_I2C_TOOLS
select BR2_PACKAGE_BUSYBOX_SHOW_OTHERS
help
The eeprog program is now provided by the i2c-tools package.
gnupg2: don't preserve the old gpg2 executable name Commit e82fadab236a (gnupg2: bump to version 2.2.0) added a configure option to keep the old 'gpg2' executable name to avoid conflict with the gnupg package. It turns out that gnupg depends on !BR2_PACKAGE_GNUPG2 since commit 2cadb26e6d4 (gnupg: make gnupg and gnupg2 mutually exclusive). Drop this configure option. Rename the config option that controls the removal of gpgv2, now gpgv, to match the new name. Add legacy config symbol handling. Cc: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-11-14 13:02:38 +01:00
config BR2_PACKAGE_GNUPG2_GPGV2
bool "gnupg2 gpgv2 option removed"
select BR2_LEGACY
select BR2_PACKAGE_GNUPG2_GPGV
help
The gpgv2 executable is now named gpgv. The config option
has been renamed accordingly.
imx-gpu-viv: bump to version 6.2.2.p0 New features: - Added mutex protection for referencing gctSIGNAL in gckOS_MapSignal to fix a MT race issue. - Streamlined GPU address calculation base on MC20 (0/1) and MMU (0/1) combinations. - Fixed multiple Android HWC 2.0 rendering issues. Refined HWC 2.0 driver implementation. - Improved HWC2.0 composition performance by composing damaged regions only. - Enabled offline/online compiler IR assembly dump function for users. - Implemented the direct rendering support (no-resolve) for Wayland platform. - Added EGL_EXT_buffer_age extension for Wayland and fbdev platforms. - Updated wayland-viv protocol to support tile status sync from client to server. - Improved OpenCL 1.2 builtin function support with native GPU instructions. - Enabled OpenCL 1.2 API trace dump function controlled by VIV_TRACE environment variable. - Support for OpenGL4.0 - Cleaned up driver code issues reported by Klocwork and Coverity. Full changelog: http://git.freescale.com/git/cgit.cgi/imx/fsl-arm-yocto-bsp.git/tree/GraphicsChangeLogv6?h=imx-morty Note that the apitrace tool and the G2D libraries are not part of the package any longer, so the corresponding options are removed. The G2D libraries are now provided by a separate package. This package has been tested with both X11 and Framebuffer backends: # cd /usr/share/examples/viv_samples/vdk/ # ./tutorial7 # gmem_info ... display memory use per PID ... Also update packages that depended on g2d libraries to match new package name. Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2018-01-05 15:39:36 +01:00
config BR2_PACKAGE_IMX_GPU_VIV_APITRACE
bool "Vivante apitrace tool option removed"
select BR2_LEGACY
help
The apitrace tool for Vivante is not provided by the
imx-gpu-viv package any longer.
config BR2_PACKAGE_IMX_GPU_VIV_G2D
bool "Vivante G2D libraries from imx-gpu-viv removed"
select BR2_LEGACY
select BR2_PACKAGE_IMX_GPU_G2D
help
The G2D libraries are now provided by the imx-gpu-g2d package.
util-linux: add menu items for login utilities This change extends to the login utilities the current policy of having a selection item in the configuration menu for each utility that has an --enable/--disable knob in the "configure" script: - add selection items for login, runuser, su and sulogin (there was already an item for "last") - move "login utilities" to Config.in.legacy - make "login utilities" select last, login, runuser, su and sulogin Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-09-02 02:41:38 +02:00
###############################################################################
comment "Legacy options removed in 2017.11"
rfkill: remove package The rfkill program has been incorporated to the util-linux package. The new implementation is based upon, and backward compatible with, the original rfkill from Johannes Berg and Marcel Holtmann. Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-10-22 00:30:18 +02:00
config BR2_PACKAGE_RFKILL
bool "rfkill package removed"
select BR2_LEGACY
select BR2_PACKAGE_UTIL_LINUX
select BR2_PACKAGE_UTIL_LINUX_RFKILL
help
The rfkill program is now provided by the util-linux package.
util-linux: security bump to version 2.31 Fix CVE-2016-2779: runuser in util-linux allows local users to escape to the parent session via a crafted TIOCSTI ioctl call, which pushes characters to the terminal's input buffer. The new experimental "su --pty" feature has been implemented to fix this issue. The feature is not enabled by default and the new command line option --pty is necessary. Add rfkill, a command for enabling and disabling wireless devices. This implementation is based upon, and backward compatible with, the original rfkill from Johannes Berg and Marcel Holtmann, currently provided by the standalone "rfkill" package. Add uuidparse, a command to analyze and print information about UUID's. The "reset" script is not part of utill-linux anymore. Add a legacy config telling the user to use either BusyBox or the ncurses program. Drop the ncursesw patch, allready applied upstream. AUTORECONF is not required anymore. Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-10-31 11:47:51 +01:00
config BR2_PACKAGE_UTIL_LINUX_RESET
bool "util-linux reset option removed"
select BR2_LEGACY
help
The util-linux package no longer offers a "reset" command. Use
either the reset command provided by BusyBox or select ncurses
programs, which will install a symlink from "tset" to reset.
policycoreutils: split packages and bump to 2.7 Policycoreutils was broken up into several packages, as such several changes needed to happen for this patch to work: - Remove patches 3, 4, and 5 as they no longer apply. - Refresh patches 1 and 2 to work with version 2.7 - Remove semodule_${deps,expand,link,package} and sestatus from the makedirs in the mk file. - Remove restorecond from the make and config file. (Seperate package) - Remove Audit2allow from the make and config file. (In a different package) - Remove the package sepolgen - Add the package selinux-python - Add the package restorecond - Add the package semodule-utils - Add the relevant Config.in.legacy options into the menu. Because these are utilities that work on top of python, the older versions of these utilites still work, and as such this should be a single patch. Signed-off-by: Adam Duskett <Adamduskett@outlook.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-18 00:32:18 +02:00
config BR2_PACKAGE_POLICYCOREUTILS_AUDIT2ALLOW
bool "policycoreutils audit2allow option removed"
select BR2_LEGACY
select BR2_PACKAGE_SELINUX_PYTHON
select BR2_PACKAGE_SELINUX_PYTHON_AUDIT2ALLOW
help
The policycoreutils package no longer offers audit2allow
as a option. This package has been moved into the
selinux-python package by the SELinux maintainers.
config BR2_PACKAGE_POLICYCOREUTILS_RESTORECOND
bool "policycoreutils restorecond option removed"
select BR2_LEGACY
select BR2_PACKAGE_RESTORECOND
help
The policycoreutils package no longer offers restorecond
*: fix typo for separate(d|) in text seperate is a common misspelling of separate Fix all the typos in the tree that are not related to patch files. CHANGES seperate -> separate, in the list of changes Config.in.legacy seperate -> separate, in option name and help texts package/leafnode2/leafnode2.mk seperate -> separate, in a comment system/Config.in seperated -> separated, in a help text Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:15 +01:00
as a option. This package has been moved into a separate
policycoreutils: split packages and bump to 2.7 Policycoreutils was broken up into several packages, as such several changes needed to happen for this patch to work: - Remove patches 3, 4, and 5 as they no longer apply. - Refresh patches 1 and 2 to work with version 2.7 - Remove semodule_${deps,expand,link,package} and sestatus from the makedirs in the mk file. - Remove restorecond from the make and config file. (Seperate package) - Remove Audit2allow from the make and config file. (In a different package) - Remove the package sepolgen - Add the package selinux-python - Add the package restorecond - Add the package semodule-utils - Add the relevant Config.in.legacy options into the menu. Because these are utilities that work on top of python, the older versions of these utilites still work, and as such this should be a single patch. Signed-off-by: Adam Duskett <Adamduskett@outlook.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-18 00:32:18 +02:00
package maintained by the SELinux maintainers.
config BR2_PACKAGE_SEPOLGEN
bool "sepolgen package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_SELINUX_PYTHON
select BR2_PACKAGE_SELINUX_PYTHON_SEPOLGEN
help
Sepolgen is no longer a individual package, but instead has
been moved into the selinux-python package by the SELinux
maintainers.
package/openobex: bump version to 1.7.2 Package switched to cmake without providing most of the autoconf options previously available. Therefore we move all suboptions to Config.in.legacy. All patches are removed, the files to be patched do not exist anymore. OPENOBEX_EXTRACT_CMDS is not needed anymore, upstream provides the source as .tar.gz now. Version 1.6 added support for libusb-1.x and udev. The current version also supports bluez5_utils, not only bluez_utils. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Arnout: add help text to legacy options] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-09-16 17:15:35 +02:00
config BR2_PACKAGE_OPENOBEX_BLUEZ
bool "openobex bluez option removed"
select BR2_LEGACY
select BR2_PACKAGE_BLUEZ_UTILS
help
The OpenOBEX package no longer offers an option to enable or
disable BlueZ support. Instead, BlueZ support is always
included when the bluez5_utils or bluez_utils package is
selected.
config BR2_PACKAGE_OPENOBEX_LIBUSB
bool "openobex libusb option removed"
select BR2_LEGACY
select BR2_PACKAGE_LIBUSB
help
The OpenOBEX package no longer offers an option to enable or
disable libusb support. Instead, USB support is always
included when the libusb package is selected.
config BR2_PACKAGE_OPENOBEX_APPS
bool "openobex apps option removed"
select BR2_LEGACY
help
The OpenOBEX package no longer offers an option to enable or
disable apps support.
config BR2_PACKAGE_OPENOBEX_SYSLOG
bool "openobex syslog option removed"
select BR2_LEGACY
help
The OpenOBEX package no longer offers an option to enable or
disable syslog support.
config BR2_PACKAGE_OPENOBEX_DUMP
bool "openobex dump option removed"
select BR2_LEGACY
help
The OpenOBEX package no longer offers an option to enable or
disable dump support.
aiccu: remove package As the SixXS project has ceased its operation on 2017-06-06, the aiccu utility has been removed. Signed-off-by: Alexander Mukhin <alexander.i.mukhin@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-09-10 12:21:34 +02:00
config BR2_PACKAGE_AICCU
bool "aiccu utility removed"
select BR2_LEGACY
help
As the SixXS project has ceased its operation on 2017-06-06,
the AICCU utility has no use anymore and has been removed.
https://www.sixxs.net/sunset/
util-linux: add menu items for login utilities This change extends to the login utilities the current policy of having a selection item in the configuration menu for each utility that has an --enable/--disable knob in the "configure" script: - add selection items for login, runuser, su and sulogin (there was already an item for "last") - move "login utilities" to Config.in.legacy - make "login utilities" select last, login, runuser, su and sulogin Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-09-02 02:41:38 +02:00
config BR2_PACKAGE_UTIL_LINUX_LOGIN_UTILS
bool "util-linux login utilities option removed"
select BR2_LEGACY
select BR2_PACKAGE_UTIL_LINUX_LAST
select BR2_PACKAGE_UTIL_LINUX_LOGIN
select BR2_PACKAGE_UTIL_LINUX_RUNUSER
select BR2_PACKAGE_UTIL_LINUX_SU
select BR2_PACKAGE_UTIL_LINUX_SULOGIN
help
Login utilities (last, login, runuser, su, sulogin) now have
their own configuration options in the util-linux menu.
package/gcc: remove gcc 4.8 We're already using 5.x as default, and have 4.9.x on the lower side together with 7.x (7.1) on the higher side. Signed-off-by: Romain Naour <romain.naour@gmail.com> CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-05-23 22:24:40 +02:00
###############################################################################
comment "Legacy options removed in 2017.08"
boot/grub: remove grub is no longer maintained: it is stuck at version 0.97 with huge patches that have no opportunity to be applied upstream, as upstream has even renamed it grub-legacy. Besides, it no longer builds correctly with recent binutils versions, and even the huge patches we could grab from Debian do not help the slightest. Since upstream really considers it dead, and there are at least two alternatives (grub2 and syslinux), just remove grub. Add a legacy entry. Remove the test cases as well. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
2017-08-11 18:05:08 +02:00
config BR2_TARGET_GRUB
bool "grub (aka grub-legacy) has been removed"
select BR2_LEGACY
help
grub-legacy is no longer maintained, and no longer builds with
recent binutils versions.
Use grub2 or syslinux instead.
package/simicsfs: remove package Buildroot currently packages version 1.18 of simics, which is quite out of date, and does not compile with Linux 4.12+. The latest package v1.22 supports recent kernels, however that is not publicly available anymore like the older versions. In fact Simics is now moving away from the simicsfs kernel module, as the kernel module has required too much maintenance work. Users should move to the new user mode Simics agent instead. Therefore, we drop the corresponding package from Buildroot. Signed-off-by: Bin Meng <bmeng.cn@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-08-30 17:55:25 +02:00
config BR2_PACKAGE_SIMICSFS
bool "simicsfs support removed"
select BR2_LEGACY
help
Support for simicsfs kernel driver that provides access to a
host computer's local filesystem when the target is
executing within a SIMICS simulation has been removed.
Simics is now moving away from the simicsfs kernel module,
as the kernel module has required too much maintenance
work. Users should move to the user mode Simics agent
instead.
binutils: remove support for 2.26 Now that binutils 2.29 has been introduced, and we have moved to 2.28.1 as the default version, it is time to drop support for binutils 2.26.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-29 15:09:06 +02:00
config BR2_BINUTILS_VERSION_2_26_X
bool "binutils version 2.26 support removed"
select BR2_LEGACY
help
Support for binutils version 2.26 has been removed. The
current default version (2.28 or later) has been selected
instead.
arch/xtensa: allow specifying path to tarball file currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:56 +02:00
config BR2_XTENSA_OVERLAY_DIR
string "The BR2_XTENSA_OVERLAY_DIR option has been removed"
help
The BR2_XTENSA_OVERLAY_DIR has been removed in favour of
BR2_XTENSA_OVERLAY_FILE. You must now pass the complete
path to the overlay file, not to the directory containing
it.
config BR2_XTENSA_OVERLAY_DIR_WRAP
bool
default y if BR2_XTENSA_OVERLAY_DIR != ""
select BR2_LEGACY
arch/xtensa: get rid of an intermediate blind kconfig option It is not needed to have an intermediate blind option, we can just hide the prompt behind the same dependency as the non-blind symbol. Update our qemu-xtensa defconfig acordingly (note: it was using different values for both options, which is not possible; the blind option was just set to the non-blind one in the .config). Also remove an unneeded empty default for the BR2_XTENSA_OVERLAY_DIR string option (strings are empty by default). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:55 +02:00
config BR2_XTENSA_CUSTOM_NAME
arch/xtensa: allow specifying path to tarball file currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:56 +02:00
string "The BR2_XTENSA_CUSTOM_NAME option has been removed"
arch/xtensa: get rid of an intermediate blind kconfig option It is not needed to have an intermediate blind option, we can just hide the prompt behind the same dependency as the non-blind symbol. Update our qemu-xtensa defconfig acordingly (note: it was using different values for both options, which is not possible; the blind option was just set to the non-blind one in the .config). Also remove an unneeded empty default for the BR2_XTENSA_OVERLAY_DIR string option (strings are empty by default). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:55 +02:00
help
arch/xtensa: allow specifying path to tarball file currently, specifying a custom Xtrensa core is done with two variables: - the core name - the directory containing the overlay tarball However, the core name only serves to construct the tarball name, and is not used whatsoever to configure any of the toolchain components (binutils, gcc or gdb), except through the files that are overlayed in their respective source trees. This has two main drawbacks: - the overlay file must be named after the core, - the tarball can not be compressed. Furthermore, it also makes it extremely complex to implement a download of that tarball. So, those two variables can be squeezed into a single variable, that is the complete path of the overlay tarball. Update the qemu-xtensa defconfig accordingly. Note: we do not add a legacy entry for BR2_XTENSA_CORE_NAME, since it was previously a blind option in the last release, and there's been no release since we removed BR2_XTENSA_CUSTOM_NAME. So, we just update the legacy comments for BR2_XTENSA_CUSTOM_NAME, since that's all the user could have seen in any of our releases so far. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:56 +02:00
The BR2_XTENSA_CUSTOM_NAME option has been removed.
arch/xtensa: get rid of an intermediate blind kconfig option It is not needed to have an intermediate blind option, we can just hide the prompt behind the same dependency as the non-blind symbol. Update our qemu-xtensa defconfig acordingly (note: it was using different values for both options, which is not possible; the blind option was just set to the non-blind one in the .config). Also remove an unneeded empty default for the BR2_XTENSA_OVERLAY_DIR string option (strings are empty by default). Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Max Filippov <jcmvbkbc@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 14:21:55 +02:00
config BR2_XTENSA_CUSTOM_NAME_WRAP
bool
default y if BR2_XTENSA_CUSTOM_NAME != ""
select BR2_LEGACY
package/mke2img: remove package Now that we use mkfs to generate ext2/3/4 filesystem image by calling mkfs directly from fs/ext2/ext2.mk, we can remove this package. Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Signed-off-by: Samuel Martin <s.martin49@gmail.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-04 16:47:29 +02:00
config BR2_PACKAGE_HOST_MKE2IMG
bool "host mke2img has been removed"
select BR2_LEGACY
help
We now call mkfs directly to generate ext2/3/4 filesystem
image, so mke2img is no longer necessary.
fs/ext2: rename BR2_TARGET_ROOTFS_EXT2_BLOCKS to BR2_TARGET_ROOTFS_EXT2_SIZE This change deprecates the ext2/3/4 rootfs size in blocks symbol in favor of one that mimic the fs-size argument behavior of mkfs (i.e. size in a human readable format accepting k, m, g or t suffix or their upper-case variants). This change also updates the defconfigs that used to set BR2_TARGET_ROOTFS_EXT2_BLOCKS symbol. Signed-off-by: Samuel Martin <s.martin49@gmail.com> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-09 07:00:38 +02:00
config BR2_TARGET_ROOTFS_EXT2_BLOCKS
int "exact size in blocks has been removed"
default 0
help
This option has been removed in favor of
BR2_TARGET_ROOTFS_EXT2_SIZE. It has been set automatically
to the value you had before. Set to 0 here to remove the
warning.
config BR2_TARGET_ROOTFS_EXT2_BLOCKS_WRAP
bool
default y if BR2_TARGET_ROOTFS_EXT2_BLOCKS != 0 && \
BR2_TARGET_ROOTFS_EXT2_BLOCKS != 61440 # deprecated default value
select BR2_LEGACY
# Note: BR2_TARGET_ROOTFS_EXT2_BLOCKS_WRAP still referenced in fs/ext2/Config.in
fs/ext2: deprecate BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES option Soon, the ext{2,3,4} rootfs image will no longer be generated with genext2fs, but using mke2fs instead which has no support for the extra inode number option. So, deprecate the BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES option and recommend, in lieu, to set the total inode number, taking account of the extra ones if needed. Signed-off-by: Samuel Martin <s.martin49@gmail.com> Cc: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-04 16:47:25 +02:00
config BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES
int "ext2 extra inodes has been removed" if BR2_TARGET_ROOTFS_EXT2_INODES = 0
default 0
help
Buildroot now uses mkfs.ext2/3/4 to generate ext2/3/4
images. It now automatically selects the number of inodes
based on the image size. The extra number of inodes can no
longer be provided; instead, provide the total number of
inodes needed in BR2_TARGET_ROOTFS_EXT2_INODES.
config BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES_WRAP
bool
default y if BR2_TARGET_ROOTFS_EXT2_EXTRA_INODES != 0
select BR2_LEGACY
gst1-plugins-bad: bump version to 1.12.0 Remove non-existant configure options: --disable-mimic: https://github.com/GStreamer/gst-plugins-bad/commit/ad661999ad2c79a5d7721f0eb1e7f1f83a304224 --enable-dataurisrc: https://github.com/GStreamer/gst-plugins-bad/commit/de4bb6e1d4793637fd72d7316d06ebba4148583e --enable-videomeasure: https://github.com/GStreamer/gst-plugins-bad/commit/ca3020cf46d49d8e3fd54ec323b3a17cd389d780 --enable-apexsink, --disable-nas, --disable-linsys, --enable-sdl, --disable-sdltest, --disable-libvisual, --disable-timidity, --disable-sndio, --disable-wininet, --disable-xvid, --enable-cdxaparse, --enable-dccp, --enable-hdvparse, --enable-mve, --enable-nuvdemux, --enable-patchdetect, --enable-sdi, --enable-tta, --disable-pvr: https://github.com/GStreamer/gst-plugins-bad/commit/9b5de053995488d5ddc78c1bf4df651101271d70 [Peter: split out webrtc rename to a separate patch, tweak dataurisrc help] Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:01 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_CDXAPARSE
bool "cdxaparse removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_DATAURISRC
bool "dataurisrc moved to gstreamer1"
select BR2_LEGACY
help
Dataurisrc has moved to gstreamer core and is always built.
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_DCCP
bool "dccp removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_HDVPARSE
bool "hdvparse removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_MVE
bool "mve removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_NUVDEMUX
bool "nuvdemux removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_PATCHDETECT
bool "patchdetect removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_SDI
bool "sdi removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_TTA
bool "tta removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_VIDEOMEASURE
bool "videomeasure removed"
gst1-plugins-bad: add Image Quality Assessment (IQA) plugin This plugin replaces the recently removed videomeasure plugin. Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:02 +02:00
select BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_IQA
gst1-plugins-bad: bump version to 1.12.0 Remove non-existant configure options: --disable-mimic: https://github.com/GStreamer/gst-plugins-bad/commit/ad661999ad2c79a5d7721f0eb1e7f1f83a304224 --enable-dataurisrc: https://github.com/GStreamer/gst-plugins-bad/commit/de4bb6e1d4793637fd72d7316d06ebba4148583e --enable-videomeasure: https://github.com/GStreamer/gst-plugins-bad/commit/ca3020cf46d49d8e3fd54ec323b3a17cd389d780 --enable-apexsink, --disable-nas, --disable-linsys, --enable-sdl, --disable-sdltest, --disable-libvisual, --disable-timidity, --disable-sndio, --disable-wininet, --disable-xvid, --enable-cdxaparse, --enable-dccp, --enable-hdvparse, --enable-mve, --enable-nuvdemux, --enable-patchdetect, --enable-sdi, --enable-tta, --disable-pvr: https://github.com/GStreamer/gst-plugins-bad/commit/9b5de053995488d5ddc78c1bf4df651101271d70 [Peter: split out webrtc rename to a separate patch, tweak dataurisrc help] Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:01 +02:00
select BR2_LEGACY
gst1-plugins-bad: add Image Quality Assessment (IQA) plugin This plugin replaces the recently removed videomeasure plugin. Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:02 +02:00
help
videomeasure plugin has been removed and has been replaced by
iqa, which has automatically been enabled.
gst1-plugins-bad: bump version to 1.12.0 Remove non-existant configure options: --disable-mimic: https://github.com/GStreamer/gst-plugins-bad/commit/ad661999ad2c79a5d7721f0eb1e7f1f83a304224 --enable-dataurisrc: https://github.com/GStreamer/gst-plugins-bad/commit/de4bb6e1d4793637fd72d7316d06ebba4148583e --enable-videomeasure: https://github.com/GStreamer/gst-plugins-bad/commit/ca3020cf46d49d8e3fd54ec323b3a17cd389d780 --enable-apexsink, --disable-nas, --disable-linsys, --enable-sdl, --disable-sdltest, --disable-libvisual, --disable-timidity, --disable-sndio, --disable-wininet, --disable-xvid, --enable-cdxaparse, --enable-dccp, --enable-hdvparse, --enable-mve, --enable-nuvdemux, --enable-patchdetect, --enable-sdi, --enable-tta, --disable-pvr: https://github.com/GStreamer/gst-plugins-bad/commit/9b5de053995488d5ddc78c1bf4df651101271d70 [Peter: split out webrtc rename to a separate patch, tweak dataurisrc help] Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:01 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_APEXSINK
bool "apexsink removed"
select BR2_LEGACY
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_SDL
bool "sdl removed"
select BR2_LEGACY
gst1-plugins-ugly: bump version to 1.12.0 Remove non-existant configure options: --enable-mad: https://github.com/GStreamer/gst-plugins-ugly/commit/2f767fb24ac8ee001bde7e1452b46a4f8fe3a719 Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-12 12:18:05 +02:00
config BR2_PACKAGE_GST1_PLUGINS_UGLY_PLUGIN_MAD
bool "mad (*.mp3 audio) removed"
select BR2_LEGACY
core: change the strip command from a choice to a boolean Curently, we have a choice to select between stripping and not stripping. This is legacy code from back when we had a third option, sstrip (super-strip). Since we removed sstrip, stripping or not stripping is now just a boolean rather than a choice. Make it so. We make BR2_STRIP_strip default to 'y' to keep the current behaviour of defaulting to stripping. Move BR2_STIP_none to legacy, and instruct the user to review the new setting. Drop any reference to BR2_STRIP_none in comments. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-01 14:51:21 +02:00
config BR2_STRIP_none
bool "Strip command 'none' has been removed"
select BR2_LEGACY
help
The strip command choice has been changed into a single
boolean option. Please check that the new setting is
correct (in the "Build options" sub-menu)
package/beecrypt: remove c++ support Optional C++ support depends on icu, the icu version bump to 59.1 brought ABI-breaking changes http://site.icu-project.org/download/59#TOC-char16_t-in-C- which are incompatible with beecrypt. Since beecrypt did not get any updates upstream since 2009 and no package uses beecrypt's C++ support we disable this broken option. With C++ support removed patches 0002 & 0004 are not needed anymore. Fixes http://autobuild.buildroot.net/results/a1a/a1ad507371192ddecacab0df91f7b2a84c7c288d/ Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-06-11 14:48:51 +02:00
config BR2_PACKAGE_BEECRYPT_CPP
bool "C++ support removed in beecrypt"
select BR2_LEGACY
help
Support for C++ depends on icu. The beecrypt package is
incompatible with icu 59+.
spice: security bump to version 0.12.6 Fixes the following security issues: CVE-2015-3247: Race condition in the worker_update_monitors_config function in SPICE 0.12.4 allows a remote authenticated guest user to cause a denial of service (heap-based memory corruption and QEMU-KVM crash) or possibly execute arbitrary code on the host via unspecified vectors. CVE-2015-5260: Heap-based buffer overflow in SPICE before 0.12.6 allows guest OS users to cause a denial of service (heap-based memory corruption and QEMU-KVM crash) or possibly execute arbitrary code on the host via QXL commands related to the surface_id parameter. CVE-2015-5261: Heap-based buffer overflow in SPICE before 0.12.6 allows guest OS users to read and write to arbitrary memory locations on the host via guest QXL commands related to surface creation. Client/gui support is gone upstream (moved to spice-gtk / virt-viewer), so add Config.in.legacy handling for them. Lz4 is a new optional dependency, so handle it. The spice protocol definition is no longer included and instead used from spice-protocol. The build system uses pkg-config --variable=codegendir to find the build time path of this, which doesn't take our STAGING_DIR prefix into consideration, so it needs some help. The installed protocol definition will likewise be newer than the generated files, so we need to workaround that to ensure they are not regenerated (which needs host python / pyparsing). Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-06-22 00:07:42 +02:00
config BR2_PACKAGE_SPICE_CLIENT
bool "spice client support removed"
select BR2_LEGACY
help
Spice client support has been removed upstream. The
functionality now lives in the spice-gtk widget and
virt-viewer.
config BR2_PACKAGE_SPICE_GUI
bool "spice gui support removed"
select BR2_LEGACY
help
Spice gui support has been removed upstream. The
functionality now lives in the spice-gtk widget and
virt-viewer.
spice: bump to version 0.12.5 Tunneling support is gone upstream, so drop the patch and add Config.in.legacy handling for the option. Celt051 is no longer a hard dependency, and opus is a new optional dependency, so adjust the dependencies to match. Python / pyparsing are not needed as the tarball contains the generated files (this should presumably have been host-python in the first place as these are used at build time), but we need a small workaround to convince configure that they really aren't needed. Alsa-lib is only needed for client support, and the configure script checks for X11/Xext/Xrender, so adjust the dependencies to match. A user manual is now generated by default if asciidoc is available, so explicitly disable that. Signed-off-by: Peter Korsgaard <peter@korsgaard.com> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-06-22 00:07:41 +02:00
config BR2_PACKAGE_SPICE_TUNNEL
bool "spice network redirection removed"
select BR2_LEGACY
help
Spice network redirection, aka tunnelling has been removed
upstream.
package/input-tools: remove package remove input-tools, it has been obsoleted by linuxconsoletools linuxconsoletools uses the same name as upstream and carries the latest version of the tools installed by input-tools. Signed-off-by: Koen Martens <gmc@sonologic.nl> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-06-20 20:54:49 +02:00
config BR2_PACKAGE_INPUT_TOOLS
bool "input-tools removed"
select BR2_LEGACY
select BR2_PACKAGE_LINUXCONSOLETOOLS
help
input-tools has been removed, it is replaced by
linuxconsoletools, which has automatically been enabled.
config BR2_PACKAGE_INPUT_TOOLS_INPUTATTACH
bool "inputattach moved to linuxconsoletools"
select BR2_LEGACY
select BR2_PACKAGE_LINUXCONSOLETOOLS
select BR2_PACKAGE_LINUXCONSOLETOOLS_INPUTATTACH
help
input-tools has been removed, inputattach is now part
of linuxconsoletools, which has automatically been
enabled.
config BR2_PACKAGE_INPUT_TOOLS_JSCAL
bool "jscal moved to linuxconsoletools"
select BR2_LEGACY
select BR2_PACKAGE_LINUXCONSOLETOOLS
select BR2_PACKAGE_LINUXCONSOLETOOLS_JOYSTICK
help
input-tools has been removed, jscal is now part
of linuxconsoletools, which has automatically been
enabled.
config BR2_PACKAGE_INPUT_TOOLS_JSTEST
bool "jstest moved to linuxconsoletools"
select BR2_LEGACY
select BR2_PACKAGE_LINUXCONSOLETOOLS
select BR2_PACKAGE_LINUXCONSOLETOOLS_JOYSTICK
help
input-tools has been removed, jstest is now part
of linuxconsoletools, which has automatically been
enabled.
toolchain: remove CodeSourcery sh toolchain Since glibc 2.17, executable link command need not include the -lrt option for clock_* system calls. As a result, over time less and less software packages bother to check whether to toolchain needs -lrt. We are now at a point where maintainers refuse to add this complexity into their build system. This requires Buildroot to carry patches fixing this issue indefinitely. glibc 2.17 is now 4.5 years old. There is no reason to use an older version with current software. This commit removes the predefined profile for CodeSourcery sh toolchain that is based on glibc 2.16. One may still use the custom external toolchain support in Buildroot to get this toolchain back, and deal with any build issues that this toolchain causes. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-06-16 05:32:48 +02:00
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_SH
bool "SH Sourcery toolchain has been removed"
select BR2_LEGACY
help
The Sourcery CodeBench toolchain for the sh architecture has
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
been removed, since it uses glibc older than 2.17 that
requires -lrt to link executables using clock_* system calls.
This makes this toolchain difficult to maintain over time.
toolchain: remove CodeSourcery sh toolchain Since glibc 2.17, executable link command need not include the -lrt option for clock_* system calls. As a result, over time less and less software packages bother to check whether to toolchain needs -lrt. We are now at a point where maintainers refuse to add this complexity into their build system. This requires Buildroot to carry patches fixing this issue indefinitely. glibc 2.17 is now 4.5 years old. There is no reason to use an older version with current software. This commit removes the predefined profile for CodeSourcery sh toolchain that is based on glibc 2.16. One may still use the custom external toolchain support in Buildroot to get this toolchain back, and deal with any build issues that this toolchain causes. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-06-16 05:32:48 +02:00
toolchain: remove CodeSourcery x86 toolchain Since glibc 2.17, executable link command need not include the -lrt option for clock_* system calls. As a result, over time less and less software packages bother to check whether to toolchain needs -lrt. We are now at a point where maintainers refuse to add this complexity into their build system. This requires Buildroot to carry patches fixing this issue indefinitely. glibc 2.17 is now 4.5 years old. There is no reason to use an older version with current software. This commit removes the predefined profile for CodeSourcery x86 toolchain that is based on glibc 2.16. One may still use the custom external toolchain support in Buildroot to get this toolchain back, and deal with any build issues that this toolchain causes. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-06-16 05:32:47 +02:00
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_X86
bool "x86 Sourcery toolchain has been removed"
select BR2_LEGACY
help
The Sourcery CodeBench toolchain for the x86 architecture has
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
been removed, since it uses glibc older than 2.17 that
requires -lrt to link executables using clock_* system calls.
This makes this toolchain difficult to maintain over time.
toolchain: remove CodeSourcery x86 toolchain Since glibc 2.17, executable link command need not include the -lrt option for clock_* system calls. As a result, over time less and less software packages bother to check whether to toolchain needs -lrt. We are now at a point where maintainers refuse to add this complexity into their build system. This requires Buildroot to carry patches fixing this issue indefinitely. glibc 2.17 is now 4.5 years old. There is no reason to use an older version with current software. This commit removes the predefined profile for CodeSourcery x86 toolchain that is based on glibc 2.16. One may still use the custom external toolchain support in Buildroot to get this toolchain back, and deal with any build issues that this toolchain causes. Signed-off-by: Baruch Siach <baruch@tkos.co.il> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-06-16 05:32:47 +02:00
package/gcc: remove gcc 4.8 We're already using 5.x as default, and have 4.9.x on the lower side together with 7.x (7.1) on the higher side. Signed-off-by: Romain Naour <romain.naour@gmail.com> CC: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-05-23 22:24:40 +02:00
config BR2_GCC_VERSION_4_8_X
bool "gcc 4.8.x support removed"
select BR2_LEGACY
help
Support for gcc version 4.8.x has been removed. The current
default version (5.x or later) has been selected instead.
glibc: drop version 2.22 We don't want a dozen glibc versions and there's no particular reason to keep this old version around so drop it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> [Thomas: add entry to Config.in.legacy.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-02-25 01:34:47 +01:00
###############################################################################
comment "Legacy options removed in 2017.05"
package/sunxi-mali: remove sunxi-mali libMali for r2p4 Mali kernel modules sunxi-mali userspace drivers (libMali.so) for r2p4 Mali kernel modules are linked against libUMP.so.2 but libump package in Buildroot only provide libUMP.so.3. In upstream commit 1c5063f43cdc9de341c0d63b2e3921cab86c7742 [1], library versioning was added. For the r3p* libraries, libUMP.so.3 is used (and provided by Buildroot libump package), but for the r2p* libraries, libUMP.so.2 is used (and not provided by Buildroot libump package). Due to this any program or library trying to link with -lGLESv2 or -lEGL will fail with the following error: arm-none-linux-gnueabi/bin/ld: warning: libUMP.so.2, needed by output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libMali.so, not found (try using -rpath or -rpath-link) output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_close' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_mapped_pointer_get' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_secure_id_get' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_mapped_pointer_release' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libMali.so: undefined reference to `ump_reference_add' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libMali.so: undefined reference to `ump_size_get' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_reference_release' output/host/usr/arm-buildroot-linux-gnueabi/sysroot/armv4t/usr/lib/libEGL.so: undefined reference to `ump_open' collect2: error: ld returned 1 exit status Since nothing provides libUMP.so.2, this commit removes the BR2_PACKAGE_SUNXI_MALI_R2P4 option and adds the BR2_ARM_EABIHF dependency directly to sunxi-mali package. Fixes: http://autobuild.buildroot.net/results/8d0/8d0b78798abf0c4ca124952d0d0455da6f8fa14f/ [1] https://github.com/linux-sunxi/sunxi-mali-proprietary/commit/1c5063f43cdc9de341c0d63b2e3921cab86c7742 [2] http://lists.busybox.net/pipermail/buildroot/2017-February/183500.html Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Francois Perrad <francois.perrad@gadz.org> [Thomas: fix conflicts when applying on master, tweak commit log.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-02-21 22:43:16 +01:00
config BR2_PACKAGE_SUNXI_MALI_R2P4
bool "sunxi-mali r2p4 removed"
select BR2_LEGACY
help
sunxi-mali libMali for r2p4 Mali kernel module has been
removed since the libump package only provides libUMP.so.3.
libMali for r2p4 Mali kernel module requires libUMP.so.2.
package/nodejs: remove support for coffeescript BR2_PACKAGE_NODEJS_MODULES_COFFEESCRIPT has been deprecated. To continue using add coffee-script to BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL. Fixes: http://autobuild.buildroot.org/results/0e4fb1a615ab9654ad2b4b1274a34583e02aa44e http://autobuild.buildroot.org/results/fabf2f5f25c62be615fd09e59e6ad9234385645f http://autobuild.buildroot.org/results/8653d78a190df1e691f52a911d8153104c46226b http://autobuild.buildroot.org/results/2fc7e5e64ad6ced02a47e5062176d316eed0f43b Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-05-06 15:19:13 +02:00
config BR2_PACKAGE_NODEJS_MODULES_COFFEESCRIPT
bool "CoffeeScript option has been removed"
select BR2_LEGACY
help
The option to enable NodeJS CoffeeScript has been removed.
To continue using it, add "coffee-script" to
BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL.
package/nodejs: remove support for express BR2_PACKAGE_NODEJS_MODULES_EXPRESS has been deprecated. To continue using add express to BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL Fixes: http://autobuild.buildroot.org/results/fcfa38e98c22c8809452f7d0ee86dfe2e9d2482f http://autobuild.buildroot.org/results/946996fa78c7814d1e0ea0ef1239c6eb0c7aa8dd http://autobuild.buildroot.org/results/df920e7b17617f1e4867d94eda52cab38f7b0622 Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-05-06 15:19:12 +02:00
config BR2_PACKAGE_NODEJS_MODULES_EXPRESS
bool "Express web application framework option has been removed"
select BR2_LEGACY
help
The option to enable the NodeJS Express web application
framework has been removed. To continue using it, add
"express" to BR2_PACKAGE_NODEJS_MODULES_ADDITIONAL.
bluez5_utils: allow install of deprecated tools Since BlueZ 5.44 many command line tools are deprecated, among them gatttool. Add an option to install these tools. Remove the gatttool specific option, since it is redundant now. Fixes: http://autobuild.buildroot.net/results/ddb/ddb975c9e1475fee1da63cb21240d8d59b161076/ http://autobuild.buildroot.net/results/19a/19adc0aa5a7e48119ef4ba25ba0403867f74f678/ http://autobuild.buildroot.net/results/9bd/9bd8e13ddffdd0631ddca30ec40cc4664729b0cb/ Cc: Marcin Bis <marcin@bis.org.pl> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Baruch Siach <baruch@tkos.co.il> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-05-01 14:59:41 +02:00
config BR2_PACKAGE_BLUEZ5_UTILS_GATTTOOL
bool "bluez5_utils gatttool install option removed"
select BR2_PACKAGE_BLUEZ5_UTILS_DEPRECATED
help
The option to install gatttool specifically has been removed.
Since version 5.44 gatttool is in the list of deprecated
tools. The option to build and install deprecated tools has
been automatically enabled.
openocd: bump to 0.10.0 Some configure options have been renamed. Support for the deprecated FT2232 devices has been removed in this release, so remove this option. Signed-off-by: Christophe Priouzeau <christophe.priouzeau@st.com> [Thomas: - Add Config.in.legacy handling, suggested by Arnout. - Improve commit log with more details, suggested by Arnout.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-28 16:34:34 +02:00
config BR2_PACKAGE_OPENOCD_FT2XXX
bool "openocd ft2232 support has been removed"
select BR2_PACKAGE_OPENOCD_FTDI
select BR2_LEGACY
help
FT2232 support in OpenOCD has been removed, it's replaced by
FDTI support, which has automatically been enabled.
package/kodi: bump to version 17.1-Krypton Removed unneeded patches - 0001-Fixup-include-path.patch (not needed after CMake switch) - 0005-native-TexturePacker-fix-compilation-with-gcc-4.6.patch (applied upstream) - 0006-ffmpeg30.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0007-exif-Fix-for-out-of-memory-errors-with-large-numbers.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0008-Fix-nullpadding-issue-when-reading-certain-id3v1-tag.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0009-lib-cximage-6.0-fix-compilation-with-gcc6.patch (cximage was removed in bump from 16.x to 17.0) - 0010-curl-support-version-7.5.0-and-upwards.patch (applied upstream) - 0011-xbmc_pvr_types.h-Fix-compilation-with-gcc6.patch (applied upstream) - 0012-Fix_includes_in_amcodec.patch (was backported from 17.0-Krypton to 16.0-Jarvis) Rebased patches - 0004-kodi-config.cmake-use-CMAKE_FIND_ROOT_PATH-to-fix-cr.patch also renamed to 0001-... Removed dependencies not needed anymore: - boost https://github.com/xbmc/xbmc/commit/41ae93f0913f7ba72087a48370f8d66a3eac9fcc - giflib https://github.com/xbmc/xbmc/commit/d44338baf1f6d1e6b76cd7dbab6453d76cc2ac31 - jasper/tiff https://github.com/xbmc/xbmc/commit/00724eb109a702f0098089d849f7c02ea173a4a9 - jpeg https://github.com/xbmc/xbmc/commit/7d5bdfb9a09348bde92b323ef6077b5e75edaca7 - libdcadec https://github.com/xbmc/xbmc/commit/378eb2687c1da5f97ef47c78431033b52f0d4417 - libglew https://github.com/xbmc/xbmc/commit/03ff0d5ea02963b1283fe8bc7c1bad18f2dd97b6 - libgcrypt was already an optional dependency in Kodi 16, not part of the CMake buildsystem anymore - libmpeg2 https://github.com/xbmc/xbmc/commit/d22c829d67937e8d03fdac8f8b0bf2d1fa8fbf70 - libogg/libvorbis https://github.com/xbmc/xbmc/commit/4c609691776ab845d83153e19d191b7fd445edb9 - libpng https://github.com/xbmc/xbmc/commit/be6b50c6c3f91809a9045c199d054cbc1d637d5d - librtmp, the new rtmp inputstream addon will be added later https://github.com/xbmc/xbmc/commit/d04f43a4eb6f920cc42a28627b580f17e2be1bb5 - libsquish https://github.com/xbmc/xbmc/commit/ed03f828be3615d294eb4a4cfccc5cdccec22997 - xlib_libXmu - xlib_libXt Switched to CMake, autoconf was deprecated: https://github.com/xbmc/xbmc/pull/10797 The dependency for egl/gles on arm, formerly enforced by the automake build system, was not ported to CMake. Bumped BR2_TOOLCHAIN_GCC_AT_LEAST to 4.8 to fix build errors with gcc-4.7 found while testing http://autobuild.buildroot.net/toolchains/configs/sourcery-x86.config For details please read http://lists.busybox.net/pipermail/buildroot/2017-April/190195.html Added hard-dependency for libegl, needed after https://github.com/xbmc/xbmc/commit/0ac305f7cf82e98021b6e0d70c3d4c51fc1cf18a Libva support depends on X11 https://github.com/xbmc/xbmc/blob/Krypton/project/cmake/modules/FindVAAPI.cmake#L42 and OpenGL/EGL https://github.com/xbmc/xbmc/blob/Krypton/xbmc/cores/VideoPlayer/DVDCodecs/Video/VAAPI.h#L23 Libvdpau support depends on X11 https://github.com/xbmc/xbmc/blob/Krypton/project/cmake/modules/FindVDPAU.cmake#L21 and OpenGL/EGL https://github.com/xbmc/xbmc/blob/Krypton/xbmc/cores/VideoPlayer/DVDCodecs/Video/VDPAU.h#L43 Updated clean-up hook and added host-xmlstarlet as dependency to manipulate the list of default system addons in addon-manifest.xml. Added dependency to BR2_ENABLE_LOCALE, needs iconv_open: https://github.com/xbmc/xbmc/blob/Krypton/xbmc/utils/CharsetConverter.cpp#L200 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: minor tweaks.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-29 10:37:28 +02:00
config BR2_PACKAGE_KODI_RTMPDUMP
bool "kodi rtmp has been removed"
select BR2_LEGACY
package/kodi-inputstream-rtmp: new package Select the new package by the legacy option for easier update. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: use SPDX license code.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-07-16 16:35:17 +02:00
select BR2_PACKAGE_KODI_INPUTSTREAM_RTMP
package/kodi: bump to version 17.1-Krypton Removed unneeded patches - 0001-Fixup-include-path.patch (not needed after CMake switch) - 0005-native-TexturePacker-fix-compilation-with-gcc-4.6.patch (applied upstream) - 0006-ffmpeg30.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0007-exif-Fix-for-out-of-memory-errors-with-large-numbers.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0008-Fix-nullpadding-issue-when-reading-certain-id3v1-tag.patch (was backported from 17.0-Krypton to 16.0-Jarvis) - 0009-lib-cximage-6.0-fix-compilation-with-gcc6.patch (cximage was removed in bump from 16.x to 17.0) - 0010-curl-support-version-7.5.0-and-upwards.patch (applied upstream) - 0011-xbmc_pvr_types.h-Fix-compilation-with-gcc6.patch (applied upstream) - 0012-Fix_includes_in_amcodec.patch (was backported from 17.0-Krypton to 16.0-Jarvis) Rebased patches - 0004-kodi-config.cmake-use-CMAKE_FIND_ROOT_PATH-to-fix-cr.patch also renamed to 0001-... Removed dependencies not needed anymore: - boost https://github.com/xbmc/xbmc/commit/41ae93f0913f7ba72087a48370f8d66a3eac9fcc - giflib https://github.com/xbmc/xbmc/commit/d44338baf1f6d1e6b76cd7dbab6453d76cc2ac31 - jasper/tiff https://github.com/xbmc/xbmc/commit/00724eb109a702f0098089d849f7c02ea173a4a9 - jpeg https://github.com/xbmc/xbmc/commit/7d5bdfb9a09348bde92b323ef6077b5e75edaca7 - libdcadec https://github.com/xbmc/xbmc/commit/378eb2687c1da5f97ef47c78431033b52f0d4417 - libglew https://github.com/xbmc/xbmc/commit/03ff0d5ea02963b1283fe8bc7c1bad18f2dd97b6 - libgcrypt was already an optional dependency in Kodi 16, not part of the CMake buildsystem anymore - libmpeg2 https://github.com/xbmc/xbmc/commit/d22c829d67937e8d03fdac8f8b0bf2d1fa8fbf70 - libogg/libvorbis https://github.com/xbmc/xbmc/commit/4c609691776ab845d83153e19d191b7fd445edb9 - libpng https://github.com/xbmc/xbmc/commit/be6b50c6c3f91809a9045c199d054cbc1d637d5d - librtmp, the new rtmp inputstream addon will be added later https://github.com/xbmc/xbmc/commit/d04f43a4eb6f920cc42a28627b580f17e2be1bb5 - libsquish https://github.com/xbmc/xbmc/commit/ed03f828be3615d294eb4a4cfccc5cdccec22997 - xlib_libXmu - xlib_libXt Switched to CMake, autoconf was deprecated: https://github.com/xbmc/xbmc/pull/10797 The dependency for egl/gles on arm, formerly enforced by the automake build system, was not ported to CMake. Bumped BR2_TOOLCHAIN_GCC_AT_LEAST to 4.8 to fix build errors with gcc-4.7 found while testing http://autobuild.buildroot.net/toolchains/configs/sourcery-x86.config For details please read http://lists.busybox.net/pipermail/buildroot/2017-April/190195.html Added hard-dependency for libegl, needed after https://github.com/xbmc/xbmc/commit/0ac305f7cf82e98021b6e0d70c3d4c51fc1cf18a Libva support depends on X11 https://github.com/xbmc/xbmc/blob/Krypton/project/cmake/modules/FindVAAPI.cmake#L42 and OpenGL/EGL https://github.com/xbmc/xbmc/blob/Krypton/xbmc/cores/VideoPlayer/DVDCodecs/Video/VAAPI.h#L23 Libvdpau support depends on X11 https://github.com/xbmc/xbmc/blob/Krypton/project/cmake/modules/FindVDPAU.cmake#L21 and OpenGL/EGL https://github.com/xbmc/xbmc/blob/Krypton/xbmc/cores/VideoPlayer/DVDCodecs/Video/VDPAU.h#L43 Updated clean-up hook and added host-xmlstarlet as dependency to manipulate the list of default system addons in addon-manifest.xml. Added dependency to BR2_ENABLE_LOCALE, needs iconv_open: https://github.com/xbmc/xbmc/blob/Krypton/xbmc/utils/CharsetConverter.cpp#L200 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> [Thomas: minor tweaks.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-29 10:37:28 +02:00
help
Internal rtmp support was removed from Kodi.
package/kodi-visualisation-fountain: remove package Remove broken package: https://github.com/notspiff/visualization.fountain/issues/1#issuecomment-166156021 Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-29 10:37:21 +02:00
config BR2_PACKAGE_KODI_VISUALISATION_FOUNTAIN
bool "kodi-visualisation-fountain has been removed"
select BR2_LEGACY
help
According to upstream 'the visualization is not currently
in a working shape.'
portmap: remove package as it is obsolete The upstream tarball isn't available, no releases since ten years. The latest change to upstream git is from 2014. Better use rpcbind for any RPC portmapper service. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> [Thomas: make the legacy option select rpcbind, as suggested by Arnout.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-02 05:37:08 +02:00
config BR2_PACKAGE_PORTMAP
bool "portmap has been removed"
select BR2_LEGACY
select BR2_PACKAGE_RPCBIND
help
The portmap upstream tarball is removed, no releases since
ten years and latest change in upstream git in 2014.
You should better use rpcbind as a RPC portmapper.
binutils: remove support for binutils 2.25 Now that we have switched to binutils 2.27 as the default binutils version, it's time to get rid of binutils 2.25. So this commit remove the 2.25 version choice, the hash file entry, the patches, and adds a Config.in.legacy option. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-03 22:28:21 +02:00
config BR2_BINUTILS_VERSION_2_25_X
bool "binutils version 2.25 support removed"
select BR2_LEGACY
help
Support for binutils version 2.25 has been removed. The
current default version (2.27 or later) has been selected
instead.
uclibc: update to 1.0.23 Bugfix release, internal RPC implementation removed. All patches applied upstream. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-04-03 20:18:02 +02:00
config BR2_TOOLCHAIN_BUILDROOT_INET_RPC
bool "uclibc RPC support has been removed"
select BR2_LEGACY
help
uClibc-ng removed internal RPC implementation in 1.0.23. You
should use libtirpc instead.
fs/ext2: Remove support for auto-calculation of rootfs size Auto-calculation of the rootfs size cannot be done in a reliable way as it depends on the host filesystem and is broken on non ext4 host (see bugs [1] [2]). So let the user specify the size he wants for his rootfs. [1] https://bugs.busybox.net/show_bug.cgi?id=8831 [2] https://bugs.busybox.net/show_bug.cgi?id=9496 Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Thomas: as suggested by Arnout, use 60 MB as the default size instead of 64 MB.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-24 17:20:29 +01:00
config BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS
int "extra size in blocks has been removed"
default 0
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Since the support for auto calculation of the filesystem size
has been removed, this option is now useless and must be 0.
You may want to check that BR2_TARGET_ROOTFS_EXT2_BLOCKS
matchs your needs.
fs/ext2: Remove support for auto-calculation of rootfs size Auto-calculation of the rootfs size cannot be done in a reliable way as it depends on the host filesystem and is broken on non ext4 host (see bugs [1] [2]). So let the user specify the size he wants for his rootfs. [1] https://bugs.busybox.net/show_bug.cgi?id=8831 [2] https://bugs.busybox.net/show_bug.cgi?id=9496 Signed-off-by: Sébastien Szymanski <sebastien.szymanski@armadeus.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Thomas: as suggested by Arnout, use 60 MB as the default size instead of 64 MB.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-24 17:20:29 +01:00
config BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS_WRAP
bool
default y if BR2_TARGET_ROOTFS_EXT2_EXTRA_BLOCKS != 0
select BR2_LEGACY
systemd: bump version to 233 --disable-kdbus no longer exists, so remove everything related to it. Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-22 12:39:13 +01:00
config BR2_PACKAGE_SYSTEMD_KDBUS
bool "systemd-kdbus has been removed"
select BR2_LEGACY
help
--enable/disable-kdbus configure option has been removed since
systemd-231.
polarssl: remove unmaintained package The 1.2.x branch is no longer maintained, so remove it since it's likely security-vulnerable. mbedtls is the modern replacement which was renamed from polarssl when ARM bought them up. However major releases broke API so polarssl 1.2.x isn't always interchangeable with polarssl/mbedtls 1.3.x (interim mixed naming because of new ownership) or newer 2.x series. Fortunately we don't have any package in the tree that uses polarssl exclusively. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Acked-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [Thomas: - Remove entry in DEVELOPERS file for this package. Noticed by Arnout. - Remove comment in bctoolbox.mk that no longer makes sense after polarssl removal. Noticed by Arnout.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-16 14:04:34 +01:00
config BR2_PACKAGE_POLARSSL
bool "polarssl has been removed"
select BR2_LEGACY
help
The polarssl crypto library has been removed since the 1.2.x
release branch is no longer maintained. Newer upstream
branches/releases (mbedtls) have API changes so they're not
drop-in replacements.
package/nbd: rename options ... and add myself to the DEVELOPERS for nbd. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-12 10:58:15 +01:00
config BR2_NBD_CLIENT
bool "nbd client option was renamed"
select BR2_LEGACY
select BR2_PACKAGE_NBD_CLIENT
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The nbd client option has been renamed to
BR2_PACKAGE_NBD_CLIENT.
package/nbd: rename options ... and add myself to the DEVELOPERS for nbd. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-12 10:58:15 +01:00
config BR2_NBD_SERVER
bool "nbd server option was renamed"
select BR2_LEGACY
select BR2_PACKAGE_NBD_SERVER
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The nbd server option has been renamed to
BR2_PACKAGE_NBD_SERVER.
package/nbd: rename options ... and add myself to the DEVELOPERS for nbd. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-12 10:58:15 +01:00
gtest/gmock: bump to version 1.8.0 GTest version 1.8.0 includes gmock so merge both packages inside gtest In this merge: - Add gmock as a suboption of gtest (BR2_PACKAGE_GTEST_GMOCK) following advice from Arnout Vandecappelle - Add BR2_PACKAGE_GMOCK as a legacy entry, selecting BR2_PACKAGE_GTEST and BR2_PACKAGE_GTEST_GMOCK. - Use cmake to install libraries and headers and add missing files (gtest.pc, gtest-config, gmock.pc) in GTEST_POST_INSTALL_STAGING_HOOKS instead of redefining GTEST_INSTALL_STAGING_CMDS - Remove patch on Python as gmock/gtest now supports python 3.0 (commit 456fc2b5c4e9ebf05a5987dfe1ff0ac9ffeb53cc) - Add the correct license in HOST_GTEST_LICENSE as all python code in googlemock/scripts/generator is licensed under Apache-2.0 and not BSD-3c - Fix URL of gtest project in Config.in - Remove the gmock entry from DEVELOPERS - Install gmock_gen directly, instead of as a symlink to gmock_gen.py Notice that any external package that depends on gmock will cause an immediate build termination because make doesn't know how to build gmock. Since the user has just removed gmock from the legacy menu, it should be quite obvious what needs to be done. Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Reviewed-by: Romain Naour <romain.naour@gmail.com> [Thomas: - Use += instead of = when assigning a value to <pkg>_DEPENDENCIES in conditional - Remove comment about the "tricky logic" around BUILD_GTEST and BUILD_GMOCK - Move GTEST_GMOCK_INSTALL_MISSING_FILE inside the ($(BR2_PACKAGE_GTEST_GMOCK),y) condition.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-02-14 12:05:16 +01:00
config BR2_PACKAGE_GMOCK
bool "gmock merged into gtest package"
select BR2_LEGACY
select BR2_PACKAGE_GTEST
select BR2_PACKAGE_GTEST_GMOCK
help
GMock is now a suboption of the GTest package.
linux-headers: remove 3.18.x and 4.8.x series These aren't supported upstream any more so remove the options and add them to legacy handling. Switch older deprecations that used 3.18.x to 3.12.x Remove stray version strings as well. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-02 21:18:29 +01:00
config BR2_KERNEL_HEADERS_4_8
bool "kernel headers version 4.8.x are no longer supported"
select BR2_LEGACY
help
Version 4.8.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: remove 3.18.x and 4.8.x series These aren't supported upstream any more so remove the options and add them to legacy handling. Switch older deprecations that used 3.18.x to 3.12.x Remove stray version strings as well. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-02 21:18:29 +01:00
config BR2_KERNEL_HEADERS_3_18
bool "kernel headers version 3.18.x are no longer supported"
select BR2_LEGACY
help
Version 3.18.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: remove 3.18.x and 4.8.x series These aren't supported upstream any more so remove the options and add them to legacy handling. Switch older deprecations that used 3.18.x to 3.12.x Remove stray version strings as well. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-02 21:18:29 +01:00
glibc: drop version 2.22 We don't want a dozen glibc versions and there's no particular reason to keep this old version around so drop it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> [Thomas: add entry to Config.in.legacy.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-02-25 01:34:47 +01:00
config BR2_GLIBC_VERSION_2_22
bool "glibc 2.22 removed"
select BR2_LEGACY
help
Support for glibc version 2.22 has been removed. The current
default version has been selected instead.
snowball-{hdmiservice, init}: remove packages The snowball_defconfig has been removed one year ago in commit b3fa8e24defb20e1734e7e75f432090fe83c0dd8 ("configs: remove calao_snowball_defconfig"), and it's no longer possible to buy Snowball boards. Therefore, there is no reason to keep the snowball-related packages in our tree. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-05 14:32:38 +01:00
###############################################################################
comment "Legacy options removed in 2017.02"
perl-db-file: remove this package The module DB_File (Berkeley DB wrapper) is a Perl core module. Long time ago, its build as a core module was broken. Since perl-cross-1.0.2, this issue is fixed. So, this package which build DB_File as CPAN module, becomes useless. Signed-off-by: Francois Perrad <francois.perrad@gadz.org> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-26 15:50:35 +01:00
config BR2_PACKAGE_PERL_DB_FILE
bool "perl-db-file removed"
select BR2_LEGACY
select BR2_PACKAGE_BERKELEYDB
select BR2_PACKAGE_PERL
help
DB_File can be built as a core Perl module, so the separate
perl-db-file package has been removed.
linux-headers: kill 3.14.x and 4.{5, 6, 7}.x series These aren't supported upstream any more so remove the options and add them to legacy. Also switch the older deprecations that used 3.14.x to 3.12.x Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 15:48:26 +01:00
config BR2_KERNEL_HEADERS_4_7
bool "kernel headers version 4.7.x are no longer supported"
select BR2_LEGACY
help
Version 4.7.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: kill 3.14.x and 4.{5, 6, 7}.x series These aren't supported upstream any more so remove the options and add them to legacy. Also switch the older deprecations that used 3.14.x to 3.12.x Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 15:48:26 +01:00
config BR2_KERNEL_HEADERS_4_6
bool "kernel headers version 4.6.x are no longer supported"
select BR2_LEGACY
help
Version 4.6.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: kill 3.14.x and 4.{5, 6, 7}.x series These aren't supported upstream any more so remove the options and add them to legacy. Also switch the older deprecations that used 3.14.x to 3.12.x Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 15:48:26 +01:00
config BR2_KERNEL_HEADERS_4_5
bool "kernel headers version 4.5.x are no longer supported"
select BR2_LEGACY
help
Version 4.5.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: kill 3.14.x and 4.{5, 6, 7}.x series These aren't supported upstream any more so remove the options and add them to legacy. Also switch the older deprecations that used 3.14.x to 3.12.x Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 15:48:26 +01:00
config BR2_KERNEL_HEADERS_3_14
bool "kernel headers version 3.14.x are no longer supported"
select BR2_LEGACY
help
Version 3.14.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: kill 3.14.x and 4.{5, 6, 7}.x series These aren't supported upstream any more so remove the options and add them to legacy. Also switch the older deprecations that used 3.14.x to 3.12.x Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 15:48:26 +01:00
toolchain-external: remove musl-cross prebuilt toolchain The upstream link to download musl-cross prebuilt toolchain is dead [1] and there no new download location. Also the last prebuilt toolchain use musl 1.1.12 version which is not uptodate (currently 1.1.15). Remove this support and recommend to use Buildroot toolchain instead. [1] https://googledrive.com/host/0BwnS5DMB0YQ6bDhPZkpOYVFhbk0 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-16 16:29:45 +01:00
config BR2_TOOLCHAIN_EXTERNAL_MUSL_CROSS
bool "musl-cross 1.1.12 toolchain removed"
select BR2_LEGACY
help
The support for the prebuilt toolchain based on the Musl C
library provided by the musl-cross project has been removed.
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Upstream doesn't provide any prebuilt toolchain anymore, use
the Buildroot toolchain instead.
toolchain-external: remove musl-cross prebuilt toolchain The upstream link to download musl-cross prebuilt toolchain is dead [1] and there no new download location. Also the last prebuilt toolchain use musl 1.1.12 version which is not uptodate (currently 1.1.15). Remove this support and recommend to use Buildroot toolchain instead. [1] https://googledrive.com/host/0BwnS5DMB0YQ6bDhPZkpOYVFhbk0 Signed-off-by: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-16 16:29:45 +01:00
uclibc: update to 1.0.20 The test suite is removed from the package and is already a separate package in buildroot. All patches are upstream, so remove them. The UCLIBC_HAS_LFS option is removed upstream. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> [Thomas: remove BR2_UCLIBC_INSTALL_TEST_SUITE option, add it to Config.in.legacy.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-04 12:20:27 +01:00
config BR2_UCLIBC_INSTALL_TEST_SUITE
bool "uClibc tests now in uclibc-ng-test"
select BR2_LEGACY
select BR2_PACKAGE_UCLIBC_NG_TEST
help
The test suite of the uClibc C library has been moved into a
separate package, uclibc-ng-test.
toolchain: kill ADI Blackfin toolchain This toolchain has many problems which are fixed in contemporary gcc and uClibc-ng. In addition, several hacks are needed to be able to work with this toolchain. All these hacks are removed as well. Also the package exceptions for this toolchain are removed. The BR2_BFIN_INSTALL_FDPIC_SHARED and BR2_BFIN_INSTALL_FLAT_SHARED options don't get a legacy entry. For the ADI toolchain, there already is a legacy entry, so it doesn't make sense to add it twice. For other external toolchains, these options didn't actually work, because they rely on the specific layout of the ADI toolchain. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-24 00:40:35 +01:00
config BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX
bool "Blackfin.uclinux.org 2014R1 toolchain removed"
select BR2_LEGACY
help
The ADI Blackfin toolchain has many bugs which are fixed in
more recent gcc and uClibc-ng releases. Use the Buildroot
toolchain instead.
makedevs: remove target package The makedevs package is a fork of the makedevs tool from busybox. It is part of the Buildroot infrastructure, not something that should be used on the target. It something like this is needed on the target, upstream busybox should be used. And if one of the Buildroot-specific features is needed, then that feature should be upstreamed to busybox. Besides, there were already two things wrong with the target package: - it didn't take into account the overlap with busybox (no depends on BR2_PACKAGE_BUSYBOX_SHOW_OTHERS, no dependency on busybox); - it didn't take into account the libcap feature. The target package was introduced more or less accidentally in 81cd9d45 where the intention was to make it more similar to other packages. So, kill it with fire. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-23 15:14:04 +01:00
config BR2_PACKAGE_MAKEDEVS
bool "makedevs removed"
select BR2_LEGACY
help
The makedevs tool is part of busybox. The Buildroot fork
should not be used outside of the Buildroot infrastructure.
toolchain-external: remove Arago toolchains The Arago toolchains are no longer maintained and haven't been updated for a long time. With this removal, all the legacy toolchain-external support can be removed as well. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-07 02:20:17 +01:00
config BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV7A
bool "Arago ARMv7 2011.09 removed"
select BR2_LEGACY
help
The Arago toolchains are every old and not updated anymore.
config BR2_TOOLCHAIN_EXTERNAL_ARAGO_ARMV5TE
bool "Arago ARMv5 2011.09 removed"
select BR2_LEGACY
help
The Arago toolchains are every old and not updated anymore.
snowball-{hdmiservice, init}: remove packages The snowball_defconfig has been removed one year ago in commit b3fa8e24defb20e1734e7e75f432090fe83c0dd8 ("configs: remove calao_snowball_defconfig"), and it's no longer possible to buy Snowball boards. Therefore, there is no reason to keep the snowball-related packages in our tree. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-11-05 14:32:38 +01:00
config BR2_PACKAGE_SNOWBALL_HDMISERVICE
bool "snowball-hdmiservice removed"
select BR2_LEGACY
help
We no longer have support for the Snowball platform in
Buildroot, so this package was no longer useful.
config BR2_PACKAGE_SNOWBALL_INIT
bool "snowball-init removed"
select BR2_LEGACY
help
We no longer have support for the Snowball platform in
Buildroot, so this package was no longer useful.
package/gdb: remove version 7.9 Now that 7.12 has been added and 7.11 is the default version, let's remove the old 7.9 release. Signed-off-by: Jörg Krause <joerg.krause@embedded.rocks> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-14 14:40:58 +01:00
config BR2_GDB_VERSION_7_9
bool "gdb 7.9 has been removed"
select BR2_LEGACY
help
The 7.9 version of gdb has been removed. Use a newer version
instead.
Revert "Added local directory as source of kernel code" This reverts commit 73da2ff6f718f2889e3c5024d899f8d58f502863. The reason for adding support for a local location was to be able to do development on the Linux kernel source tree on a local directory rather than have to clone it for every build. We already have a mechanism for that, it's called override-srcdir. It's been available since September 2011, more than a year before this patch was committed. Otherwise, we're going to be adding support for local sources in other packages. First was U-Boot as submitted by Adam. But what next? We can't have such support for all packages, especially since override-srcdir does the job. Besides, using a local source tree makes the build non-reproducible, so we don't really want to have this in a .config (or defconfig). We only handle the boolean option in legacy, as there is nothing we can do with the directory path. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Rafal Fabich <rafal.fabich@gmail.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Adam Duskett <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-08-28 01:03:04 +02:00
###############################################################################
comment "Legacy options removed in 2016.11"
php: rework selection of interfaces Following suggestion of Yann Morin, rework selection of php interfaces: use booleans instead of choice to be able to select multiple interfaces as they are not exclusive. We make sure at least one of the options is selected. It should be noted that previously CGI and FPM could not be selected at the same time. This is now possible. Bug that prevented compilation of CGI and FPM binaries at the same time has been fixed since PHP 5.4 (https://github.com/php-build/php-build/issues/101). Legacy handling is added for the two options that are removed, and the appropriate new options are selected. Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-12 23:31:07 +02:00
config BR2_PACKAGE_PHP_SAPI_CLI_CGI
*: fix typo for separate(d|) in text seperate is a common misspelling of separate Fix all the typos in the tree that are not related to patch files. CHANGES seperate -> separate, in the list of changes Config.in.legacy seperate -> separate, in option name and help texts package/leafnode2/leafnode2.mk seperate -> separate, in a comment system/Config.in seperated -> separated, in a help text Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:15 +01:00
bool "PHP CGI and CLI options are now separate"
php: rework selection of interfaces Following suggestion of Yann Morin, rework selection of php interfaces: use booleans instead of choice to be able to select multiple interfaces as they are not exclusive. We make sure at least one of the options is selected. It should be noted that previously CGI and FPM could not be selected at the same time. This is now possible. Bug that prevented compilation of CGI and FPM binaries at the same time has been fixed since PHP 5.4 (https://github.com/php-build/php-build/issues/101). Legacy handling is added for the two options that are removed, and the appropriate new options are selected. Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-12 23:31:07 +02:00
select BR2_PACKAGE_PHP_SAPI_CLI
select BR2_PACKAGE_PHP_SAPI_CGI
legacy: add missing select When adding a boolean option to legacy, it should slect BR2_LEGACY, to trigger the legacy warning. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-24 18:46:00 +02:00
select BR2_LEGACY
php: rework selection of interfaces Following suggestion of Yann Morin, rework selection of php interfaces: use booleans instead of choice to be able to select multiple interfaces as they are not exclusive. We make sure at least one of the options is selected. It should be noted that previously CGI and FPM could not be selected at the same time. This is now possible. Bug that prevented compilation of CGI and FPM binaries at the same time has been fixed since PHP 5.4 (https://github.com/php-build/php-build/issues/101). Legacy handling is added for the two options that are removed, and the appropriate new options are selected. Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-12 23:31:07 +02:00
help
The PHP Interface options have been split up into a
separate option for each interface.
config BR2_PACKAGE_PHP_SAPI_CLI_FPM
bool "PHP CLI and FPM options are now separate"
select BR2_PACKAGE_PHP_SAPI_CLI
select BR2_PACKAGE_PHP_SAPI_FPM
legacy: add missing select When adding a boolean option to legacy, it should slect BR2_LEGACY, to trigger the legacy warning. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Fabrice Fontaine <fontaine.fabrice@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-10-24 18:46:00 +02:00
select BR2_LEGACY
php: rework selection of interfaces Following suggestion of Yann Morin, rework selection of php interfaces: use booleans instead of choice to be able to select multiple interfaces as they are not exclusive. We make sure at least one of the options is selected. It should be noted that previously CGI and FPM could not be selected at the same time. This is now possible. Bug that prevented compilation of CGI and FPM binaries at the same time has been fixed since PHP 5.4 (https://github.com/php-build/php-build/issues/101). Legacy handling is added for the two options that are removed, and the appropriate new options are selected. Signed-off-by: Fabrice Fontaine <fabrice.fontaine@orange.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-12 23:31:07 +02:00
help
The PHP Interface options have been split up into a
separate option for each interface.
wvstreams: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:06 +02:00
config BR2_PACKAGE_WVSTREAMS
bool "wvstreams removed"
select BR2_LEGACY
help
wvstreams is not maintained anymore since about 2009. It also
doesn't build anymore with recent compilers (GCC 5+).
wvdial: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:05 +02:00
config BR2_PACKAGE_WVDIAL
bool "wvdial removed"
select BR2_LEGACY
help
wvdial is not maintained anymore since about 2009. It also
doesn't build anymore with recent compilers (GCC 5+).
webkitgtk24: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:04 +02:00
config BR2_PACKAGE_WEBKITGTK24
bool "webkitgtk 2.4.x removed"
select BR2_LEGACY
help
This legacy package only existed because some other packages
depended on that specific version of webkitgtk. However, the
other packages have been fixed. webkitgtk 2.4 is full of
security issues so it needs to be removed.
torsmo: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:03 +02:00
config BR2_PACKAGE_TORSMO
bool "torsmo removed"
select BR2_LEGACY
help
torsmo has been unmaintained for a long time, and nobody
seems to be interested in it.
sstrip: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:02 +02:00
config BR2_PACKAGE_SSTRIP
bool "sstrip removed"
select BR2_LEGACY
help
sstrip is unmaintained and potentially harmful. It doesn't
save so much compared to normal binutils strip, and there is
a big risk of binaries that don't work. Use normal strip
instead.
linux-headers: remove deprecated version 4.2 and 4.3 We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:01 +02:00
config BR2_KERNEL_HEADERS_4_3
bool "kernel headers version 4.3.x are no longer supported"
select BR2_LEGACY
help
Version 4.3.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: remove deprecated version 4.2 and 4.3 We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:01 +02:00
config BR2_KERNEL_HEADERS_4_2
bool "kernel headers version 4.2.x are no longer supported"
select BR2_LEGACY
help
Version 4.2.x of the Linux kernel headers are no longer
legacy: don't select kernel headers The kernel headers versions are parts of a choice, so we can't select them. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2018-10-04 22:00:29 +02:00
maintained upstream and are now removed.
linux-headers: remove deprecated version 4.2 and 4.3 We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:01 +02:00
kodi-addon-xvdr: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:51:00 +02:00
config BR2_PACKAGE_KODI_ADDON_XVDR
bool "kodi-addon-xvdr removed"
select BR2_LEGACY
help
According to the github project page:
https://github.com/pipelka/xbmc-addon-xvdr
this package is discontinued.
ipkg: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:50:59 +02:00
config BR2_PACKAGE_IPKG
bool "ipkg removed"
select BR2_LEGACY
help
ipkg dates back to the early 2000s when Compaq started the
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
handhelds.org project and it hasn't seen development since
2006. Use opkg as a replacement.
ipkg: remove deprecated package We will remove BR2_DEPRECATED, so remove this deprecated package. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:50:59 +02:00
gcc: remove deprecated 4.7.x We will remove BR2_DEPRECATED, so remove this deprecated option. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:50:58 +02:00
config BR2_GCC_VERSION_4_7_X
bool "gcc 4.7.x support removed"
select BR2_LEGACY
help
Support for gcc version 4.7.x has been removed. The current
default version (4.9.x or later) has been selected instead.
binutils: remove deprecated 2.24.X We will remove BR2_DEPRECATED, so remove this deprecated option. [Peter: drop binutils patches] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-10-15 16:50:57 +02:00
config BR2_BINUTILS_VERSION_2_24_X
bool "binutils version 2.24 support removed"
select BR2_LEGACY
help
Support for binutils version 2.24 has been removed. The
current default version (2.26 or later) has been selected
instead.
weston: bump to version 1.12.0 Also drop upstream patch. Drop propietary RPI support since it's gone upstream. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-24 19:28:36 +02:00
config BR2_PACKAGE_WESTON_RPI
bool "Weston propietary RPI support is gone"
select BR2_LEGACY
help
Upstream decided the propietary (rpi-userland) weston composer
support wasn't worth the effort so it was removed. Switch to
the open VC4 support.
linux/tools: make it a real, separate package The kernel source tree also contains the sources for various userland tools, of which cpupower, perf or selftests. Currently, we have support for building those tools as part of the kernel build procedure. This looked the correct thing to do so far, because, well, they *are* part of the kernel source tree and some really have to be the same version as the kernel that will run. However, this is causing quite a non-trivial-to-break circular dependency in some configurations. For example, this defconfig fails to build (similar to the one reported by Paul): BR2_arm=y BR2_cortex_a7=y BR2_ARM_FPU_NEON_VFPV4=y BR2_TOOLCHAIN_EXTERNAL=y BR2_INIT_SYSTEMD=y BR2_LINUX_KERNEL=y BR2_LINUX_KERNEL_CUSTOM_GIT=y BR2_LINUX_KERNEL_CUSTOM_REPO_URL="https://github.com/raspberrypi/linux.git" BR2_LINUX_KERNEL_CUSTOM_REPO_VERSION="26f3b72a9c049be10e6af196252283e1f6ab9d1f" BR2_LINUX_KERNEL_DEFCONFIG="bcm2709" BR2_PACKAGE_LINUX_TOOLS_CPUPOWER=y BR2_PACKAGE_CRYPTODEV=y BR2_PACKAGE_OPENSSL=y BR2_PACKAGE_LIBCURL=y This causes a circular dependency, as explained by Thomas: - When libcurl is enabled, systemd depends on it - When OpenSSL is enabled, obviously, will use it for SSL support - When cryptodev-linux is enabled, OpenSSL will depend on it to use crypto accelerators supported in the kernel via cryptodev-linux. - cryptodev-linux being a kernel module, it depends on linux - linux by itself (the kernel) does not depend on pciutils, but the linux tool "cpupower" (managed in linux-tool-cpupower) depends on pciutils - pciutils depends on udev when available - udev is provided by systemd. And indeed, during the build, we can see that make warns (it's only reported as a *warning*, not as an actual error): [...] make[1]: Circular /home/ymorin/dev/buildroot/O/build/openssl-1.0.2h/.stamp_configured <- cryptodev-linux dependency dropped. >>> openssl 1.0.2h Downloading [...] So the build fails later on, when openssl is actually built: eng_cryptodev.c:57:31: fatal error: crypto/cryptodev.h: No such file or directory compilation terminated. <builtin>: recipe for target 'eng_cryptodev.o' failed Furthermore, graph-depends also detects the circular dependency, but treats it as a hard-error: Recursion detected for : cryptodev-linux which is a dependency of: openssl which is a dependency of: libcurl which is a dependency of: systemd which is a dependency of: udev which is a dependency of: pciutils which is a dependency of: linux which is a dependency of: cryptodev-linux Makefile:738: recipe for target 'graph-depends' failed Of course, there is no way to break the loop without losing functionality in either one of the involved packages *and* keep our infrastructure and packages as-is. The only solution is to break the loop at the linux-tools level, by moving them away into their own package, so that the linux package will no longer have the opportunity to depend on another package via a dependency of one the tools. All three linux tools are thus moved away to their own package. The package infrastructure only knows of three types of packages: those in package/ , in boot/ , in toolchain/ and the one in linux/ . So we create that new linux-tools package in package/ so that we don't have to fiddle with yet another special case in the infra. Still, we want its configure options to appear in the kernel's sub-menu. So, we make it a prompt-less package, with only the tools visible as options of that package, but without the usual dependency on their master symbol; they only depend on the Linux kernel. Furthermore, because the kernel is such a huge pile of code, we would not be very happy to extract it a second time just for the sake of a few tools. We can't extract only the tools/ sub-directory from the kernel source either, because some tools have hard-coded path to includes from the kernel (arch and stuff). Instead, we just use the linux source tree as our own build tree, and ensure the linux tree is extracted and patched before linux-tools is configured and built. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Paul Ashford <paul.ashford@zurria.co.uk> [Thomas: - fix typo #(@D) -> $(@D) - fix the inclusion of the per-tool .mk files.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-06 16:29:14 +02:00
config BR2_LINUX_KERNEL_TOOL_CPUPOWER
bool "linux-tool cpupower"
depends on BR2_LINUX_KERNEL
select BR2_LEGACY
select BR2_PACKAGE_LINUX_TOOLS_CPUPOWER
help
Linux tool cpupower option was renamed.
config BR2_LINUX_KERNEL_TOOL_PERF
bool "linux-tool perf"
depends on BR2_LINUX_KERNEL
select BR2_LEGACY
select BR2_PACKAGE_LINUX_TOOLS_PERF
help
Linux tool perf option was renamed.
config BR2_LINUX_KERNEL_TOOL_SELFTESTS
bool "linux-tool selftests"
depends on BR2_LINUX_KERNEL
select BR2_LEGACY
select BR2_PACKAGE_LINUX_TOOLS_SELFTESTS
help
Linux tool selftests option was renamed.
gcc: rename option for ARC gcc The ARC gcc version is now based on gcc 6.x and no longer gcc 4.8.x, which makes the option BR2_GCC_VERSION_4_8_ARC a bit irrelevant, as is the prompt of this option. This commit therefore renames this option to BR2_GCC_VERSION_ARC, and adjust its prompt as well. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-08-11 15:25:38 +02:00
config BR2_GCC_VERSION_4_8_ARC
bool "gcc arc option renamed"
select BR2_LEGACY
help
The option that selects the gcc version for the ARC
architecture has been renamed to BR2_GCC_VERSION_ARC.
package/gcc: properly handle legacy for renamed ARC option Commit "50332a530b gcc: rename option for ARC gcc" tried to add legacy handling but the new symbol is part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2016.11, following the example described in the beginning of the file. Cc: Giulio Benetti <giulio.benetti@benettiengineering.com> Cc: Romain Naour <romain.naour@gmail.com> Cc: Thomas Petazzoni <thomas.petazzoni@bootlin.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:33 +01:00
# Note: BR2_GCC_VERSION_4_8_ARC is still referenced from
# package/gcc/Config.in.host
gcc: rename option for ARC gcc The ARC gcc version is now based on gcc 6.x and no longer gcc 4.8.x, which makes the option BR2_GCC_VERSION_4_8_ARC a bit irrelevant, as is the prompt of this option. This commit therefore renames this option to BR2_GCC_VERSION_ARC, and adjust its prompt as well. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-08-11 15:25:38 +02:00
linux-headers: remove deprecated versions Linux headers 3.19.x and 4.0.x have been deprecated for a while now, so it's time to remove them. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-09 17:20:54 +02:00
config BR2_KERNEL_HEADERS_4_0
bool "kernel headers version 4.0.x are no longer supported"
select BR2_LEGACY
help
Version 4.0.x of the Linux kernel headers have been deprecated
for more than four buildroot releases and are now removed.
config BR2_KERNEL_HEADERS_3_19
bool "kernel headers version 3.19.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.19.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated versions Linux headers 3.19.x and 4.0.x have been deprecated for a while now, so it's time to remove them. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-09 17:20:54 +02:00
package/libevas-generic-loaders: remove package libevas-generic-loaders package is not used anymore, remove it. Add a legacy entry. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-02 22:31:32 +02:00
config BR2_PACKAGE_LIBEVAS_GENERIC_LOADERS
bool "libevas-generic-loaders package removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
With EFL 1.18, libevas-generic-loaders is now provided by the
efl package.
package/libevas-generic-loaders: remove package libevas-generic-loaders package is not used anymore, remove it. Add a legacy entry. Signed-off-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-02 22:31:32 +02:00
package/elementary: remove package elementary package is not used anymore, remove it. Add a legacy entry. Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: move the legacy entry at the right place.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-09-02 22:31:31 +02:00
config BR2_PACKAGE_ELEMENTARY
bool "elementary package removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
With EFL 1.18, elementary is now provided by the efl package.
Revert "Added local directory as source of kernel code" This reverts commit 73da2ff6f718f2889e3c5024d899f8d58f502863. The reason for adding support for a local location was to be able to do development on the Linux kernel source tree on a local directory rather than have to clone it for every build. We already have a mechanism for that, it's called override-srcdir. It's been available since September 2011, more than a year before this patch was committed. Otherwise, we're going to be adding support for local sources in other packages. First was U-Boot as submitted by Adam. But what next? We can't have such support for all packages, especially since override-srcdir does the job. Besides, using a local source tree makes the build non-reproducible, so we don't really want to have this in a .config (or defconfig). We only handle the boolean option in legacy, as there is nothing we can do with the directory path. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Rafal Fabich <rafal.fabich@gmail.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Adam Duskett <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-08-28 01:03:04 +02:00
config BR2_LINUX_KERNEL_CUSTOM_LOCAL
bool "Linux kernel local directory option removed"
Config.in.legacy: add missing select BR2_LINUX_KERNEL_CUSTOM_LOCAL was moved to legacy handling during release 2016.11 but does not select BR2_LEGACY. Add the select, like done by all other symbols in the file. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2022-08-15 01:38:19 +02:00
select BR2_LEGACY
Revert "Added local directory as source of kernel code" This reverts commit 73da2ff6f718f2889e3c5024d899f8d58f502863. The reason for adding support for a local location was to be able to do development on the Linux kernel source tree on a local directory rather than have to clone it for every build. We already have a mechanism for that, it's called override-srcdir. It's been available since September 2011, more than a year before this patch was committed. Otherwise, we're going to be adding support for local sources in other packages. First was U-Boot as submitted by Adam. But what next? We can't have such support for all packages, especially since override-srcdir does the job. Besides, using a local source tree makes the build non-reproducible, so we don't really want to have this in a .config (or defconfig). We only handle the boolean option in legacy, as there is nothing we can do with the directory path. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Rafal Fabich <rafal.fabich@gmail.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Adam Duskett <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-08-28 01:03:04 +02:00
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The option to select a local directory as the source of the
Linux kernel has been removed. It hurts reproducibility of
builds.
Revert "Added local directory as source of kernel code" This reverts commit 73da2ff6f718f2889e3c5024d899f8d58f502863. The reason for adding support for a local location was to be able to do development on the Linux kernel source tree on a local directory rather than have to clone it for every build. We already have a mechanism for that, it's called override-srcdir. It's been available since September 2011, more than a year before this patch was committed. Otherwise, we're going to be adding support for local sources in other packages. First was U-Boot as submitted by Adam. But what next? We can't have such support for all packages, especially since override-srcdir does the job. Besides, using a local source tree makes the build non-reproducible, so we don't really want to have this in a .config (or defconfig). We only handle the boolean option in legacy, as there is nothing we can do with the directory path. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Rafal Fabich <rafal.fabich@gmail.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Adam Duskett <aduskett@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-08-28 01:03:04 +02:00
In case you were using this option during development of your
Linux kernel, use the override mechanism instead.
gdb: remove version 7.8 Now that 7.11 has been added and 7.10 is the default version, let's remove the old 7.8 release. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-17 00:12:58 +02:00
###############################################################################
comment "Legacy options removed in 2016.08"
efl: remove broken JP2K loader This option has been marked as broken since 2016.08. Since nobody repaired it, we'll just remove it. Since technically it was already removed in 2016.08, it's added to the 2016.08 section of the legacy menu. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Romain Naour <romain.naour@gmail.com> Cc: Gustavo Sverzut Barbieri <barbieri@profusion.mobi> Reviewed-By: Gustavo Sverzut Barbieri <barbieri@profusion.mobi> Acked-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-08 00:50:54 +01:00
config BR2_PACKAGE_EFL_JP2K
bool "libevas jp2k loader has been removed"
select BR2_LEGACY
Config.in.legacy: add missing help keyword Commit ac1910713ce (efl: remove broken JP2K loader) added a legacy entry for BR2_PACKAGE_EFL_JP2K, but forgot to add the 'help' keyword before the help text, leading to confusing error messages from kconfig: Config.in.legacy:482: syntax error Config.in.legacy:481: unknown option "JP2K" Config.in.legacy:482: unknown option "while" Config.in.legacy:483: unknown option "JP2K" Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2017-03-09 22:52:47 +01:00
help
efl: remove broken JP2K loader This option has been marked as broken since 2016.08. Since nobody repaired it, we'll just remove it. Since technically it was already removed in 2016.08, it's added to the 2016.08 section of the legacy menu. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Cc: Romain Naour <romain.naour@gmail.com> Cc: Gustavo Sverzut Barbieri <barbieri@profusion.mobi> Reviewed-By: Gustavo Sverzut Barbieri <barbieri@profusion.mobi> Acked-by: Romain Naour <romain.naour@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-03-08 00:50:54 +01:00
JP2K support in EFL requires openjpeg 1.x (libopenjpeg1.pc)
while Buildroot only packages openjpeg 2.x. Therefore, the
JP2K loader has been removed from EFL.
package/systemd: Remove SYSTEMD_COMPAT option Since v230 of systemd, the compat libraries have been fully removed. https://github.com/systemd/systemd/commit/4de282cf9324ab13d17ac334244d0d7cae2df37d Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> [Thomas: rewrap Config.in help text in Config.in.legacy and put the option at the right place.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-02 15:59:12 +02:00
config BR2_PACKAGE_SYSTEMD_COMPAT
bool "systemd compatibility libraries have been removed"
legacy: properly handle systemd compatibility libs The legacy symbol for systemd compatibility libraries was not selecting the BR2_LEGACY symbol, so the buld-time check would not kick in. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-08 23:00:20 +02:00
select BR2_LEGACY
package/systemd: Remove SYSTEMD_COMPAT option Since v230 of systemd, the compat libraries have been fully removed. https://github.com/systemd/systemd/commit/4de282cf9324ab13d17ac334244d0d7cae2df37d Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> [Thomas: rewrap Config.in help text in Config.in.legacy and put the option at the right place.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-02 15:59:12 +02:00
help
Config.in.legacy: fix typo Thanks to Ben Boeckel who noticed it. Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-06 10:50:47 +02:00
The systemd option to enable the compatibility libraries has
package/systemd: Remove SYSTEMD_COMPAT option Since v230 of systemd, the compat libraries have been fully removed. https://github.com/systemd/systemd/commit/4de282cf9324ab13d17ac334244d0d7cae2df37d Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> [Thomas: rewrap Config.in help text in Config.in.legacy and put the option at the right place.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-07-02 15:59:12 +02:00
been removed. Theses libraries have been useless since a few
version, and have been fully dropped from the source since
v230.
gst1-plugins-bad: cleanup of build options Remove non-existing options: * --disable-wsap * --disable-direct3d * --disable-gsettings Remove options that are already handled later in the .mk file, using optional dependencies: * --disable-rtmp * --disable-hls * --disable-dash Rename disable->strp to disable-srtp, which essentially fixes a typo. Remove liveadder plugin - no longer a separate built option, it's been merged into audiomixer. Config.in.legacy handling is added for the removed option. Signed-off-by: Marcin Nowakowski <marcin.nowakowski@imgtec.com> [Thomas: add Config.in.legacy handling for the liveaddr plugin option, tweaks to the commit log.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-24 08:12:21 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_LIVEADDER
bool "gst1-plugins-bad liveadder plugin removed"
select BR2_LEGACY
select BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_AUDIOMIXER
help
The functionality of the liveadder plugin of the
gst1-plugins-bad package has been merged into audiomixer.
imx-vpuwrap: rename from libfslvpuwrap and bump version to 1.0.65 Changelog: --Update 'nLastFrameEndPosPhy' in seqinit stage to avoid feed the same SPS to vpu repeatedly. This patch is based on the Yocto equivalent: https://github.com/Freescale/meta-fsl-arm/commit/d6b9490 Implicitly tested through gstreamer as the 0.10 plugin relies on it: # gst-launch-0.10 playbin uri=file:///root/tears_of_steel_1080p.webm Signed-off-by: Andrew Webster <awebster@arcx.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com> Tested-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-10 20:13:29 +02:00
config BR2_PACKAGE_LIBFSLVPUWRAP
bool "libfslvpuwrap has been renamed to imx-vpuwrap"
select BR2_LEGACY
select BR2_PACKAGE_IMX_VPUWRAP
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The libfslvpuwrap has been renamed to match the renamed
package.
imx-vpuwrap: rename from libfslvpuwrap and bump version to 1.0.65 Changelog: --Update 'nLastFrameEndPosPhy' in seqinit stage to avoid feed the same SPS to vpu repeatedly. This patch is based on the Yocto equivalent: https://github.com/Freescale/meta-fsl-arm/commit/d6b9490 Implicitly tested through gstreamer as the 0.10 plugin relies on it: # gst-launch-0.10 playbin uri=file:///root/tears_of_steel_1080p.webm Signed-off-by: Andrew Webster <awebster@arcx.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com> Tested-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-10 20:13:29 +02:00
imx-parser: rename from libfslparser and bump version to 4.0.9 Changelog: --Add aac latm parser in parser_libs, support aac latm in mpeg2 parser This patch is based on the Yocto equivalent: https://github.com/Freescale/meta-fsl-arm/commit/e2c6f10 Implicitly tested through gstreamer as the 0.10 plugin relies on it: # gst-launch-0.10 playbin uri=file:///root/tears_of_steel_1080p.webm Signed-off-by: Andrew Webster <awebster@arcx.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com> Tested-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-10 20:13:18 +02:00
config BR2_PACKAGE_LIBFSLPARSER
bool "libfslparser has been renamed to imx-parser"
select BR2_LEGACY
select BR2_PACKAGE_IMX_PARSER
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The libfslparser has been renamed to match the renamed
package.
imx-parser: rename from libfslparser and bump version to 4.0.9 Changelog: --Add aac latm parser in parser_libs, support aac latm in mpeg2 parser This patch is based on the Yocto equivalent: https://github.com/Freescale/meta-fsl-arm/commit/e2c6f10 Implicitly tested through gstreamer as the 0.10 plugin relies on it: # gst-launch-0.10 playbin uri=file:///root/tears_of_steel_1080p.webm Signed-off-by: Andrew Webster <awebster@arcx.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com> Tested-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-10 20:13:18 +02:00
imx-codec: rename from libfslcodec and bump version to 4.0.9 Changelog: --[aac_dec] refine the code for pure c build aac decoder c build need float point support, which use some float point function. This patch is based on the Yocto equivalent: https://github.com/Freescale/meta-fsl-arm/commit/4b91194 Implicitly tested through gstreamer as the 0.10 plugin relies on it: # gst-launch-0.10 playbin uri=file:///root/tears_of_steel_1080p.webm Signed-off-by: Andrew Webster <awebster@arcx.com> Reviewed-by: Gary Bisson <gary.bisson@boundarydevices.com> Tested-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-10 20:13:05 +02:00
config BR2_PACKAGE_LIBFSLCODEC
bool "libfslcodec has been renamed to imx-codec"
select BR2_LEGACY
select BR2_PACKAGE_IMX_CODEC
help
The libfslcodec has been renamed to match the renamed package.
uboot-tools: fix FIT support and make it optional Fix several issues regarding the support for Flat Image Trees (FIT). - Add a patch to really allow turning FIT support on/off, which was not possible due to bugs in the code and in the tools Makefile. This patch has been sent upstream but not applied there, yet. - Use independent options to control FIT support on host and target packages. - Subordinate FIT signature support to the activation of FIT support, in the target package, not to mkimage installation. - Add a dependence on the dtc utilities because mkimage needs it when FIT is enabled; otherwise mkimage fails like this: $ mkimage -f firmware.its firmware.im sh: dtc: command not found - Add BR2_PACKAGE_UBOOT_TOOLS_MKIMAGE_FIT_SIGNATURE_SUPPORT to the Config.in.legacy file. Signed-off-by: Carlos Santos <casantos@datacom.ind.br> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-06-03 21:35:39 +02:00
config BR2_PACKAGE_UBOOT_TOOLS_MKIMAGE_FIT_SIGNATURE_SUPPORT
bool "FIT support in uboot-tools has been refactored"
select BR2_LEGACY
select BR2_PACKAGE_DTC
select BR2_PACKAGE_DTC_PROGRAMS
select BR2_PACKAGE_UBOOT_TOOLS_FIT_SUPPORT
select BR2_PACKAGE_UBOOT_TOOLS_FIT_SIGNATURE_SUPPORT
select BR2_PACKAGE_UBOOT_TOOLS_MKIMAGE
help
This option has been removed in favor of a more fine-grained
configuration, which is recommended. Selecting this option
enables FIT and FIT signature support for the target packages.
It will also select the dtc and openssl packages.
uclibc: update to 1.0.15 The Linuxthreads support got reorganized. LT.new is removed, LT.old is the default for Linuxthreads. Signed-off-by: Waldemar Brodkorb <wbx@openadk.org> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-06-01 20:40:25 +02:00
config BR2_PTHREADS_OLD
bool "linuxthreads (stable/old)"
select BR2_LEGACY
help
Linuxthreads have been reworked, BR2_PTHREADS_OLD is now
BR2_PTHREADS and the old BR2_PTHREADS - LT.new got removed.
binutils: remove support for version 2.23 Now that we have added support for the lastest binutils version 2.26, it is time to remove the oldest version we currently support, 2.23, in order to keep only 3 versions: 2.24, 2.25 and 2.26. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-17 00:13:01 +02:00
config BR2_BINUTILS_VERSION_2_23_X
bool "binutils 2.23 removed"
select BR2_LEGACY
help
Binutils 2.23 has been removed, using a newer version is
recommended.
toolchain: remove eglibc support The eglibc support has been marked deprecated since 2015.08, so it's time to remove it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-17 00:13:00 +02:00
config BR2_TOOLCHAIN_BUILDROOT_EGLIBC
bool "eglibc support has been removed"
select BR2_LEGACY
help
The eglibc project no longer exists, as it has been merged
back into the glibc project. Therefore, support for eglibc
has been removed, and glibc should be used instead.
gdb: remove version 7.8 Now that 7.11 has been added and 7.10 is the default version, let's remove the old 7.8 release. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-17 00:12:58 +02:00
config BR2_GDB_VERSION_7_8
bool "gdb 7.8 has been removed"
select BR2_LEGACY
help
The 7.8 version of gdb has been removed. Use a newer version
instead.
infozip: rename to zip We currently have a package named "infozip" for Info-Zip's Zip. With the upcoming addition of a package the Info-Zip's UnZip the name is becoming ambiguous. Rename it to the more specific name "zip". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Jan Pedersen <jp@jp-embedded.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-11-27 18:38:00 +01:00
###############################################################################
Config.in.legacy: fix separator for 2016.05 legacy options Since we opened up the next branch, a number of options have been added to Config.in.legacy. However, they are located under the "legacy options removed in 2016.02", which is not correct. This commit fixes that by adding the "legacy options removed in 2016.05" header, and restoring the one related to 2016.02 at the right location. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-29 23:11:38 +01:00
comment "Legacy options removed in 2016.05"
infozip: rename to zip We currently have a package named "infozip" for Info-Zip's Zip. With the upcoming addition of a package the Info-Zip's UnZip the name is becoming ambiguous. Rename it to the more specific name "zip". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Jan Pedersen <jp@jp-embedded.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-11-27 18:38:00 +01:00
openvpn: remove polarssl crypto backend option Now that we need to bump openvpn to version 2.3.11 for security fixes the time has come to remove the polarssl option. Add legacy handling explaining the situation: PolarSSL 1.2.x can coexist with mbedTLS 2.x+, but OpenVPN requires PolarSSL/mbedTLS 1.3.x (the transition branch) >= 1.3.8 but doesn't build/work with the 2.x series. And PolarSSL/mbedTLS 1.3.x can't coexist with mbedTLS 2.x on the same target. So, unfortunately, openssl is now the only option (until libressl arrives) which means no more backend options in general. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-14 15:33:47 +02:00
config BR2_PACKAGE_OPENVPN_CRYPTO_POLARSSL
bool "openvpn polarssl crypto backend removed"
select BR2_LEGACY
help
The OpenVPN polarssl crypto backend option has been removed.
Version from 2.3.10 onwards need polarssl >= 1.3.8 but aren't
compatible with mbedtls (polarssl) series 2.x which is the
version provided in buildroot. And both can't coexist.
It now uses OpenSSL as the only option.
package/nginx: bump version to 1.10.0 The ngx_http_spdy_module has been superseded by the ngx_http_v2_module so BR2_PACKAGE_NGINX_HTTP_SPDY_MODULE has changed to BR2_PACKAGE_NGINX_HTTP_V2_MODULE Signed-off-by: Martin Bark <martin@barkynet.com> [Thomas: rewrap Config.in.legacy help text.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-03 11:36:54 +02:00
config BR2_PACKAGE_NGINX_HTTP_SPDY_MODULE
bool "nginx http spdy module removed"
select BR2_LEGACY
select BR2_PACKAGE_NGINX_HTTP_V2_MODULE
help
The ngx_http_spdy_module has been superseded by the
ngx_http_v2_module since nginx v1.9.5. The
ngx_http_v2_module modules has been automatically selected
in your configuration.
gst1-plugins-bad: remove rtp plugin option The plugin was moved from -bad to -good so remove the option. Support in -good was added via 301e8ffb. Add legacy entry to notify users of this, however we can't automatically select the good variant since good might be disabled. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-03 21:44:15 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_RTP
bool "gst1-plugins-bad rtp plugin moved to good"
select BR2_LEGACY
help
The rtp plugin has been moved from gst1-plugins-base to
gst1-plugins-good.
gst1-plugins-bad: remove mpg123 plugin option The plugin was moved from -bad to -ugly so remove the option. Support in -ugly was added via 30cde9a3. Add legacy entry to notify users of this, however we can't automatically select the ugly variant since ugly might be disabled. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-03 21:44:14 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_MPG123
bool "gst1-plugins-bad mpg123 plugin moved to ugly"
select BR2_LEGACY
help
The mpg123 plugin has been moved from gst1-plugins-bad to
gst1-plugins-ugly.
toolchain-external: remove Sourcery PowerPC toolchains These are running long on the teeth - the bundled (e)glibc versions are very old with several security bugs, they don't work reliably with -Os and have several build failures related to internal compiler errors such as: http://autobuild.buildroot.net/results/fe7/fe7bdba5faf199275aedea2918705b5d19d228bf/ http://autobuild.buildroot.net/results/935/935ac42c30ed893939c06c077534f060aed80e9a/ http://autobuild.buildroot.net/results/a47/a476af82c8fe4a279117314b278b08af9a08fe54/ http://autobuild.buildroot.net/results/cae/cae720b5096be2672b4dc1311ae3fc4ed06a3b53/ The situation will not provide, and will in fact get worse with older kernel headers precluding modern package versions and the old gcc version doing as well so remove them. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Reviewed-by: Romain Naour <romain.naour@gmail.com> [Thomas: - remove no longer needed comment in liquid-dsp Config.in file, as noticed by Romain Naour. - add Config.in.legacy options, as noticed by Romain Naour.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-29 15:18:56 +02:00
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_POWERPC
bool "PowerPC Sourcery toolchain has been removed"
select BR2_LEGACY
help
The Sourcery CodeBench toolchain for the PowerPC
architecture has been removed, as it was very old, not
maintained, and causing numerous build failures with modern
userspace packages.
config BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_POWERPC_E500V2
bool "PowerPC Sourcery E500v2 toolchain has been removed"
select BR2_LEGACY
help
The Sourcery CodeBench toolchain for the PowerPC E500v2
architecture has been removed, as it was very old, not
maintained, and causing numerous build failures with modern
userspace packages.
arch/x86: remove support for i386 The Linux kernel doesn't even support i386 anymore, there is no NPTL support for i386 and uClibc-ng only supports NPTL on x86, so there is essentially no usable thread implementation. Most likely glibc and musl also don't support i386 either. So it's time to remove the support for this architecture variant. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-17 23:31:34 +02:00
config BR2_x86_i386
bool "x86 i386 support removed"
legacy: i386 is legacy, inform the user When we dropped support for i386, we added the corresponding opiton to the legacy menu, but forgot to select BR2_LEGACY. Fix that. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-05-08 17:41:49 +02:00
select BR2_LEGACY
arch/x86: remove support for i386 The Linux kernel doesn't even support i386 anymore, there is no NPTL support for i386 and uClibc-ng only supports NPTL on x86, so there is essentially no usable thread implementation. Most likely glibc and musl also don't support i386 either. So it's time to remove the support for this architecture variant. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-04-17 23:31:34 +02:00
help
The support for the i386 processors of the x86 architecture
has been removed.
package/qt5quick1: remove obsolete package Signed-off-by: Julien Corjon <corjon.j@ecagroup.com> [Thomas: add removed option to Config.in.legacy.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-03-17 10:42:25 +01:00
config BR2_PACKAGE_QT5QUICK1
bool "qt5quick1 package removed"
select BR2_LEGACY
help
The qt5quick1 package has been removed, since it was removed
from upstream starting from Qt 5.6.
uboot: remove deprecated BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR option It's been deprecated for a year now so remove it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:24 +01:00
config BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR
uboot: fix custom patch dir legacy handling Commit 3e3fef39e71ed0426130b36aa00e4630ebb537ae added new and improved patch handling, with BR2_TARGET_UBOOT_PATCH. This was in addition to the existing BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR option, that only handled directories. Later, commit 21b25d28fc7af3bb1b2c55e4a46e0d067ebc0081 moved the old BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR to legacy options. But on the way, bad things happened: * The original option was a string, while the one added to Config.in.legacy is a bool. This results in a warning from defconfigs that actually define the old BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR (because a string is not a valid value for a bool), but it does not result in the legacy option being selected. Consequently, BR2_LEGACY is not selected either. * The advice at the top of Config.in.legacy to add a hidden WRAP option to select BR2_LEGACY was not heeded. * The advice at the top of Config.in.legacy to use the old string option as the default for the new string option was not heeded. In this case, the variable was not just renamed, as the old option supported directories only, while the new one supports files too. But since the old option is a subset of the new option, it can still be used to set a useful default. So, this mod turns the legacy option back to a string, adds a hidden bool WRAP option to set BR2_LEGACY when the string is non emoty, and uses the legacy option to set the default for the new option. Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 04:10:12 +01:00
string "uboot custom patch dir has been removed"
uboot: remove deprecated BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR option It's been deprecated for a year now so remove it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:24 +01:00
help
The uboot custom patch directory option has been removed. Use
the improved BR2_TARGET_UBOOT_PATCH option instead.
uboot: fix custom patch dir legacy handling Commit 3e3fef39e71ed0426130b36aa00e4630ebb537ae added new and improved patch handling, with BR2_TARGET_UBOOT_PATCH. This was in addition to the existing BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR option, that only handled directories. Later, commit 21b25d28fc7af3bb1b2c55e4a46e0d067ebc0081 moved the old BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR to legacy options. But on the way, bad things happened: * The original option was a string, while the one added to Config.in.legacy is a bool. This results in a warning from defconfigs that actually define the old BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR (because a string is not a valid value for a bool), but it does not result in the legacy option being selected. Consequently, BR2_LEGACY is not selected either. * The advice at the top of Config.in.legacy to add a hidden WRAP option to select BR2_LEGACY was not heeded. * The advice at the top of Config.in.legacy to use the old string option as the default for the new string option was not heeded. In this case, the variable was not just renamed, as the old option supported directories only, while the new one supports files too. But since the old option is a subset of the new option, it can still be used to set a useful default. So, this mod turns the legacy option back to a string, adds a hidden bool WRAP option to set BR2_LEGACY when the string is non emoty, and uses the legacy option to set the default for the new option. Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 04:10:12 +01:00
config BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR_WRAP
bool
default y if BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR != ""
select BR2_LEGACY
# Note: BR2_TARGET_UBOOT_CUSTOM_PATCH_DIR is still referenced from
# boot/uboot/Config.in
xf86-input-void: remove deprecated It's been deprecated for a year now so remove it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:23 +01:00
config BR2_PACKAGE_XDRIVER_XF86_INPUT_VOID
bool "xf86-input-void removed"
select BR2_LEGACY
help
The xf86-input-void package has been removed, there's no need
for it in any modern (post-2007) xorg server.
linux-headers: remove deprecated version 3.17.x Remove for the upcoming 2016.05 release, it's been deprecated for a year now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:22 +01:00
config BR2_KERNEL_HEADERS_3_17
bool "kernel headers version 3.17.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.17.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated version 3.17.x Remove for the upcoming 2016.05 release, it's been deprecated for a year now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:22 +01:00
gdb: remove deprecated version 7.7 It's been deprecated for a year now so remove it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:21 +01:00
config BR2_GDB_VERSION_7_7
bool "gdb 7.7 has been removed"
select BR2_LEGACY
help
The 7.7 version of gdb has been removed. Use a newer version
instead.
foomatic-filters: remove deprecated It's been deprecated for a year now so remove it. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:20 +01:00
config BR2_PACKAGE_FOOMATIC_FILTERS
bool "foomatic-filters"
select BR2_LEGACY
help
The foomatic-filters package was removed.
samba: remove deprecated It's been deprecated for a year now so remove it. [Peter: drop !samba dependency from samba4] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-03-11 15:32:19 +01:00
config BR2_PACKAGE_SAMBA
bool "samba"
select BR2_LEGACY
help
The samba package was removed in favour of samba4 since the
3.x series isn't supported by upstream any longer.
package/kodi: bump version to 16.0-Jarvis Add two new hard dependencies: - libdcadec https://github.com/xbmc/xbmc/commit/0997117a659a09e7b1c5bcb110f3526ea16698be - libcrossguid https://github.com/xbmc/xbmc/commit/6f8171f53992fc2eaabf71f6fa47ebed1da0d43d Kodi moved to C++11 so we need gcc >= 4.7: https://github.com/xbmc/xbmc/pull/6412 wavpack support was removed in favour of ffmpeg: https://github.com/xbmc/xbmc/commit/7916902c9e6f7a523265594f3ad7f921f93f1cd4 Enabled giflib support by default. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-20 23:09:11 +01:00
config BR2_PACKAGE_KODI_WAVPACK
bool "wavpack"
select BR2_LEGACY
help
wavpack support was removed in favour of ffmpeg:
https://github.com/xbmc/xbmc/commit/7916902c9e6f7a523265594f3ad7f921f93f1cd4
package/kodi-screensaver-rsxs: new package Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-20 23:09:07 +01:00
config BR2_PACKAGE_KODI_RSXS
bool "rsxs support in Kodi was moved to an addon"
select BR2_LEGACY
select BR2_PACKAGE_KODI_SCREENSAVER_RSXS
help
rsxs support in Kodi was moved to an addon
package/kodi-visualisation-goom: new package Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-20 23:09:06 +01:00
config BR2_PACKAGE_KODI_GOOM
bool "Goom support in Kodi was moved to an addon"
select BR2_LEGACY
select BR2_PACKAGE_KODI_VISUALISATION_GOOM
help
Goom support in Kodi was moved to an addon
package/systemd: remove BR2_PACKAGE_SYSTEMD_ALL_EXTRAS The option was a bit misleading since it only selected additional libraries without --enable/disabling any features. Including all of them here would add a lot of bloat so instead, it is replaced with notes detailing which features each library enables. Signed-off-by: Gabe Evans <gabe@hashrabbit.co> [Thomas: - slightly tweak Config.in help text, as suggested by Arnout. - add Config.in.legacy handling for BR2_PACKAGE_SYSTEMD_ALL_EXTRAS, as suggested by Arnout.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-25 22:55:11 +01:00
config BR2_PACKAGE_SYSTEMD_ALL_EXTRAS
bool "systemd all extras option has been removed"
select BR2_LEGACY
select BR2_PACKAGE_XZ
select BR2_PACKAGE_LIBGCRYPT
help
The systemd option to enable "all extras" has been
removed. To get the same features, the libgcrypt and xz
package should now be enabled.
gcc: remove 4.5.x It's been deprecated for some time now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> [Thomas: move option to Config.in.legacy, as noticed by Peter.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-24 21:25:50 +01:00
config BR2_GCC_VERSION_4_5_X
bool "gcc 4.5.x has been removed"
select BR2_LEGACY
help
The 4.5.x version of gcc has been removed. Use a newer
version instead.
package/sqlite: add optional support for libedit Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-08 20:56:41 +01:00
config BR2_PACKAGE_SQLITE_READLINE
legacy/sqlite: add "sqlite" to legacy option name The "command-line editing support was updated" does not indicate the package name, unlike the other legacy options. This commit adds "sqlite", to be nicer. Signed-off-by: Danomi Manchego <danomimanchego123@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-12-20 04:12:32 +01:00
bool "sqlite command-line editing support was updated"
package/sqlite: add optional support for libedit Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-08 20:56:41 +01:00
select BR2_PACKAGE_NCURSES
select BR2_PACKAGE_READLINE
select BR2_LEGACY
help
This option was removed in favour of the sqlite package
deciding itself depending on the enabled packages whether
command-line editing should be enabled, it also also takes
libedit into account.
infozip: rename to zip We currently have a package named "infozip" for Info-Zip's Zip. With the upcoming addition of a package the Info-Zip's UnZip the name is becoming ambiguous. Rename it to the more specific name "zip". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Jan Pedersen <jp@jp-embedded.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-11-27 18:38:00 +01:00
###############################################################################
comment "Legacy options removed in 2016.02"
package/dovecot: Remove bzip2 and zlib options The next patch of this series will add optional xz and lz4 support, to avoid adding new options for these compression packages simplify the configuration of dovecot by removing the options handling optional compression support. Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-10 21:58:17 +01:00
config BR2_PACKAGE_DOVECOT_BZIP2
bool "bzip2 support option has been removed"
select BR2_LEGACY
select BR2_PACKAGE_BZIP2
help
Bzip2 support is built if the bzip2 package is selected.
config BR2_PACKAGE_DOVECOT_ZLIB
bool "zlib support option has been removed"
select BR2_LEGACY
select BR2_PACKAGE_ZLIB
help
Zlib support is built if the zlib package is selected.
e2fsprogs: remove findfs option The e2fsprogs package's findfs option provides no capabilities. When the option is selected, a symbolic link is generated from findfs to e2label; however, e2label will not handle findfs since the respective code is explicitly disabled when `--disable-libblkid` is passed in. At this time, the e2fsprogs package only supports findfs capabilities when building its "private blkid library". Note that the `--disable-libblkid` configuration argument must remain to prevent conflicts with util-linux's libblkid and an e2fsprogs- generated variant (see e1ffc2f791b336339909c90559b7db40b455f172). Since e2fsprogs cannot provide findfs capabilities, the option is being removed in this change. A following change will be introduced to include util-linux's findfs utility. Signed-off-by: James Knight <james.knight@rockwellcollins.com> Cc: Zheng Yi <yzheng@techyauld.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-12 17:40:05 +01:00
config BR2_PACKAGE_E2FSPROGS_FINDFS
bool "e2fsprogs findfs option has been removed"
select BR2_LEGACY
help
This option attempted to enable findfs capabilities from
e2fsprogs but has not worked since July 2015 (due to
packaging changes). One can use BusyBox's findfs support or
Config.in.legacy: findfs is available in BR2_PACKAGE_UTIL_LINUX_BINARIES 031659024b3cf27bb68dc58d07519b563ef472a1 removed the option BR2_PACKAGE_UTIL_LINUX_FINDFS as it is always built by default. Signed-off-by: Phil Eichinger <phil@zankapfel.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-12-01 15:45:33 +01:00
enable the BR2_PACKAGE_UTIL_LINUX_BINARIES option.
e2fsprogs: remove findfs option The e2fsprogs package's findfs option provides no capabilities. When the option is selected, a symbolic link is generated from findfs to e2label; however, e2label will not handle findfs since the respective code is explicitly disabled when `--disable-libblkid` is passed in. At this time, the e2fsprogs package only supports findfs capabilities when building its "private blkid library". Note that the `--disable-libblkid` configuration argument must remain to prevent conflicts with util-linux's libblkid and an e2fsprogs- generated variant (see e1ffc2f791b336339909c90559b7db40b455f172). Since e2fsprogs cannot provide findfs capabilities, the option is being removed in this change. A following change will be introduced to include util-linux's findfs utility. Signed-off-by: James Knight <james.knight@rockwellcollins.com> Cc: Zheng Yi <yzheng@techyauld.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-12 17:40:05 +01:00
package/openpowerlink: bump to v2.2.2 From [1]: With version 2.0, the source code has been cleanly split into an application-oriented user library and a time-critical stack driver. The latter may be moved to a dedicated communication processor or into a kernel module to deliver enhanced performance while still keeping the API in user space. This new version break the API used in the v1.x but this is a complete rewrite of the Powerlink EPSG DS 301 implementation. The v1.x is deprecated anyway. The new build system has been split in several CMake projects which makes it difficult to package with the Buildroot CMake infra. So add a top level CMakeLists.txt to build each openpowerlink component without having to package each of them in a separate Buildroot packages. Also we need to fix the build system to support the top level CMake build. [1] http://sourceforge.net/projects/openpowerlink/ Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: - rename patches to not contain the [FIX] part in their title. - rewrap Config.in help text - rename "openPOWERLINK stack type" to "stack type" - rename ""openpowerlink demos" to "demos"] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-07 17:56:56 +01:00
config BR2_PACKAGE_OPENPOWERLINK_DEBUG_LEVEL
bool "openpowerlink debug option has been removed"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
This option depends on BR2_ENABLE_DEBUG which should not be
used by packages anymore.
package/openpowerlink: bump to v2.2.2 From [1]: With version 2.0, the source code has been cleanly split into an application-oriented user library and a time-critical stack driver. The latter may be moved to a dedicated communication processor or into a kernel module to deliver enhanced performance while still keeping the API in user space. This new version break the API used in the v1.x but this is a complete rewrite of the Powerlink EPSG DS 301 implementation. The v1.x is deprecated anyway. The new build system has been split in several CMake projects which makes it difficult to package with the Buildroot CMake infra. So add a top level CMakeLists.txt to build each openpowerlink component without having to package each of them in a separate Buildroot packages. Also we need to fix the build system to support the top level CMake build. [1] http://sourceforge.net/projects/openpowerlink/ Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: - rename patches to not contain the [FIX] part in their title. - rewrap Config.in help text - rename "openPOWERLINK stack type" to "stack type" - rename ""openpowerlink demos" to "demos"] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-07 17:56:56 +01:00
config BR2_PACKAGE_OPENPOWERLINK_KERNEL_MODULE
bool "openpowerlink package has been updated"
select BR2_LEGACY
help
openpowerlink kernel modules are built if the
kernel stack library is selected.
package/openpowerlink: properly handle legacy options Commit "b1063a0136 package/openpowerlink: bump to v2.2.2" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2016.02, following the example described in the beginning of the file. Cc: Romain Naour <romain.naour@gmail.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:32 +01:00
# Note: BR2_PACKAGE_OPENPOWERLINK_KERNEL_MODULE is still referenced from
# package/openpowerlink/Config.in
package/openpowerlink: bump to v2.2.2 From [1]: With version 2.0, the source code has been cleanly split into an application-oriented user library and a time-critical stack driver. The latter may be moved to a dedicated communication processor or into a kernel module to deliver enhanced performance while still keeping the API in user space. This new version break the API used in the v1.x but this is a complete rewrite of the Powerlink EPSG DS 301 implementation. The v1.x is deprecated anyway. The new build system has been split in several CMake projects which makes it difficult to package with the Buildroot CMake infra. So add a top level CMakeLists.txt to build each openpowerlink component without having to package each of them in a separate Buildroot packages. Also we need to fix the build system to support the top level CMake build. [1] http://sourceforge.net/projects/openpowerlink/ Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: - rename patches to not contain the [FIX] part in their title. - rewrap Config.in help text - rename "openPOWERLINK stack type" to "stack type" - rename ""openpowerlink demos" to "demos"] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-07 17:56:56 +01:00
config BR2_PACKAGE_OPENPOWERLINK_LIBPCAP
bool "openpowerlink package has been updated"
select BR2_LEGACY
help
The user space support has been split in two part:
package, legacy: fix typo for "daemon" on help text deamon -> daemon At same time, in Config.in.legacy fix other typos in the same help text: spae -> space monolitic -> monolithic Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:16 +01:00
- a monolithic user space library
- a user space daemon driver
package/openpowerlink: properly handle legacy options Commit "b1063a0136 package/openpowerlink: bump to v2.2.2" tried to add legacy handling but the new symbols are part of a choice, and Kconfig does not enforce the select of a option from a choice. Update the legacy entry for 2016.02, following the example described in the beginning of the file. Cc: Romain Naour <romain.naour@gmail.com> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:32 +01:00
# Note: BR2_PACKAGE_OPENPOWERLINK_LIBPCAP is still referenced from
# package/openpowerlink/Config.in
package/openpowerlink: bump to v2.2.2 From [1]: With version 2.0, the source code has been cleanly split into an application-oriented user library and a time-critical stack driver. The latter may be moved to a dedicated communication processor or into a kernel module to deliver enhanced performance while still keeping the API in user space. This new version break the API used in the v1.x but this is a complete rewrite of the Powerlink EPSG DS 301 implementation. The v1.x is deprecated anyway. The new build system has been split in several CMake projects which makes it difficult to package with the Buildroot CMake infra. So add a top level CMakeLists.txt to build each openpowerlink component without having to package each of them in a separate Buildroot packages. Also we need to fix the build system to support the top level CMake build. [1] http://sourceforge.net/projects/openpowerlink/ Signed-off-by: Romain Naour <romain.naour@gmail.com> [Thomas: - rename patches to not contain the [FIX] part in their title. - rewrap Config.in help text - rename "openPOWERLINK stack type" to "stack type" - rename ""openpowerlink demos" to "demos"] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-07 17:56:56 +01:00
linux: drop the option to use the same version as that of the headers It is no longer meaningful, now that we have the option to use the kernel version for the linux headers, as it is more logical and more versatile. Add it to legacy. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Peter Korsgaard <peter@korsgaard.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-02-06 00:06:17 +01:00
config BR2_LINUX_KERNEL_SAME_AS_HEADERS
bool "using the linux headers version for the kernel has been removed"
select BR2_LEGACY
help
The option to use the version of the kernel headers for the
kernel to build has been removed.
There is now the converse, better-suited and more versatile
option to use the kernel version for the linux headers.
package/cups: Un-deprecate, and update CUPS to 2.1.2 - Remove 0001-fix-static.patch - Fixed upstream - Remove 0002-fix-stack-protector-check.patch - Fixed upstream - Remove 0003-mantohtml.patch - Replaced by 0001-Remove-man-from-BUILDDIRS-in- configure.patch - Add 0002-Do-not-use-genstrings.patch - Add CUPS_PDFTOPS option to Config.in.legacy - This support was moved to the cups-filters package. Signed-off-by: Olivier Schonken <olivier.schonken@gmail.com> [Thomas: - rewrap patch description in patch 0001 - adjust patch 0002 to completely remove the call to genstrings instead of commenting it, and remove the potentially confusing 'echo' above it - add a third patch that sanitizes the installation process to avoid non-working stripping, owernship changes, etc.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-20 23:17:43 +01:00
config BR2_PACKAGE_CUPS_PDFTOPS
bool "Pdftops support has been removed from Cups"
cups-filters: new package Signed-off-by: Olivier Schonken <olivier.schonken@gmail.com> [Thomas: - add missing select BR2_PACKAGE_JPEG - use jpeg instead of libjpeg - sort selects alphabetically - fix Config.in comment dependencies.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2017-10-23 15:26:11 +02:00
select BR2_PACKAGE_CUPS_FILTERS
package/cups: Un-deprecate, and update CUPS to 2.1.2 - Remove 0001-fix-static.patch - Fixed upstream - Remove 0002-fix-stack-protector-check.patch - Fixed upstream - Remove 0003-mantohtml.patch - Replaced by 0001-Remove-man-from-BUILDDIRS-in- configure.patch - Add 0002-Do-not-use-genstrings.patch - Add CUPS_PDFTOPS option to Config.in.legacy - This support was moved to the cups-filters package. Signed-off-by: Olivier Schonken <olivier.schonken@gmail.com> [Thomas: - rewrap patch description in patch 0001 - adjust patch 0002 to completely remove the call to genstrings instead of commenting it, and remove the potentially confusing 'echo' above it - add a third patch that sanitizes the installation process to avoid non-working stripping, owernship changes, etc.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-20 23:17:43 +01:00
select BR2_LEGACY
help
Pdftops support has been removed from the cups package
It is now part of the cups-filters package.
linux-headers: remove deprecated version 3.16.x Remove for the upcoming 2016.02 release, it's been deprecated for a year now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-20 17:53:39 +01:00
config BR2_KERNEL_HEADERS_3_16
bool "kernel headers version 3.16.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.16.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated version 3.16.x Remove for the upcoming 2016.02 release, it's been deprecated for a year now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-20 17:53:39 +01:00
python-pyxml: remove obsolete package PyXML is bitrotten and obsolete. You'll find the functionality it previously provided is now included in the Python standard library. So no need to keep this package in Buildroot anymore. Signed-off-by: Yegor Yefremov <yegorslists@googlemail.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-12-19 21:42:53 +01:00
config BR2_PACKAGE_PYTHON_PYXML
bool "python-pyxml package has been removed"
select BR2_LEGACY
help
PyXML is obsolete and its functionality is covered either via
native Python XML support or python-lxml package.
toolchain: granular choice for stack protector Currently, we only support two levels of stach-smashing protection: - entirely disabled, - protect _all_ functions with -fstack-protector-all. -fstack-protector-all tends to be far too aggressive and impacts performance too much to be worth on a real product. Add a choice that allows us to select between different levels of stack-smashing protection: - none - basic (NEW) - strong (NEW) - all The differences are documented in the GCC online documentation: https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html Signed-off-by: Steven Noonan <steven@uplinklabs.net> [yann.morin.1998@free.fr: - rebase - add legacy handling - SSP-strong depends on gcc >= 4.9 - slightly simple ifeq-block in package/Makefile.in - keep the comment in the choice; add a comment shen strong is not available - drop the defaults (only keep the legacy) - update commit log ] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> [Thomas: - only show the choice if the toolchain has SSP support - add details for the BR2_SSP_ALL option that it has a significant performance impact.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-27 12:07:31 +01:00
# BR2_ENABLE_SSP is still referenced in Config.in (default in choice)
config BR2_ENABLE_SSP
bool "Stack Smashing protection now has different levels"
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The protection offered by SSP can now be selected from
different protection levels. Be sure to review the SSP level
in the build options menu.
toolchain: granular choice for stack protector Currently, we only support two levels of stach-smashing protection: - entirely disabled, - protect _all_ functions with -fstack-protector-all. -fstack-protector-all tends to be far too aggressive and impacts performance too much to be worth on a real product. Add a choice that allows us to select between different levels of stack-smashing protection: - none - basic (NEW) - strong (NEW) - all The differences are documented in the GCC online documentation: https://gcc.gnu.org/onlinedocs/gcc-4.9.2/gcc/Optimize-Options.html Signed-off-by: Steven Noonan <steven@uplinklabs.net> [yann.morin.1998@free.fr: - rebase - add legacy handling - SSP-strong depends on gcc >= 4.9 - slightly simple ifeq-block in package/Makefile.in - keep the comment in the choice; add a comment shen strong is not available - drop the defaults (only keep the legacy) - update commit log ] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> [Thomas: - only show the choice if the toolchain has SSP support - add details for the BR2_SSP_ALL option that it has a significant performance impact.] Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-27 12:07:31 +01:00
directfb: remove cle266 and unichrome support They're broken for the latest version and directfb upstream is gone. cle266 is an old chipset for AMD K7 (32 bit) athlons with integrated graphics - very odd hardware. unichrome is another VIA graphics standalone chip/chipset used for some odd video cards and VIA CPUs (x86-based: C7, Nano and so on). Add options to legacy as well. Fixes: http://autobuild.buildroot.net/results/ab9/ab9a6dd044b5f3e8e42629a2aaf598fd0e0357ed/ Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-20 13:44:37 +01:00
config BR2_PACKAGE_DIRECTFB_CLE266
directfb/legacy: add that it was removed As pointed by Yann. Signed-off-by: Gustavo Zacarias <gustavo.zacarisa@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-21 23:11:08 +01:00
bool "cle266 driver for directfb removed"
directfb: remove cle266 and unichrome support They're broken for the latest version and directfb upstream is gone. cle266 is an old chipset for AMD K7 (32 bit) athlons with integrated graphics - very odd hardware. unichrome is another VIA graphics standalone chip/chipset used for some odd video cards and VIA CPUs (x86-based: C7, Nano and so on). Add options to legacy as well. Fixes: http://autobuild.buildroot.net/results/ab9/ab9a6dd044b5f3e8e42629a2aaf598fd0e0357ed/ Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-20 13:44:37 +01:00
select BR2_LEGACY
help
The cle266 directfb driver support has been removed.
It doesn't build in the latest version and it's unlikely
anyone has any use for it.
config BR2_PACKAGE_DIRECTFB_UNICHROME
directfb/legacy: add that it was removed As pointed by Yann. Signed-off-by: Gustavo Zacarias <gustavo.zacarisa@free-electrons.com> Acked-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-21 23:11:08 +01:00
bool "unichrome driver for directfb removed"
directfb: remove cle266 and unichrome support They're broken for the latest version and directfb upstream is gone. cle266 is an old chipset for AMD K7 (32 bit) athlons with integrated graphics - very odd hardware. unichrome is another VIA graphics standalone chip/chipset used for some odd video cards and VIA CPUs (x86-based: C7, Nano and so on). Add options to legacy as well. Fixes: http://autobuild.buildroot.net/results/ab9/ab9a6dd044b5f3e8e42629a2aaf598fd0e0357ed/ Signed-off-by: Gustavo Zacarias <gustavo.zacarias@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-20 13:44:37 +01:00
select BR2_LEGACY
help
The unichrome directfb driver support has been removed.
It doesn't build in the latest version and it's unlikely
anyone has any use for it.
package/elementary: rename libelementary to elementary The upstream name is elementary so use it. Even if this package provide libelementary.so, it also provide elementary_codegen, elementary_run and elm_prefs_cc tools. Add a legacy entry. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:14 +01:00
config BR2_PACKAGE_LIBELEMENTARY
bool "libelementary has been renamed to elementary"
select BR2_LEGACY
select BR2_PACKAGE_ELEMENTARY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
The libelementary package has been renamed to match the
upstream name.
package/elementary: rename libelementary to elementary The upstream name is elementary so use it. Even if this package provide libelementary.so, it also provide elementary_codegen, elementary_run and elm_prefs_cc tools. Add a legacy entry. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:14 +01:00
package/efl/libeina: remove package Libeina is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:38 +01:00
config BR2_PACKAGE_LIBEINA
bool "libeina package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libeina is now provided by the efl package.
package/efl/libeina: remove package Libeina is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:38 +01:00
package/efl/libeet: remove package Libeet is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:37 +01:00
config BR2_PACKAGE_LIBEET
bool "libeet package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libeet is now provided by the efl package.
package/efl/libeet: remove package Libeet is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:37 +01:00
package/efl/libevas: remove package Libevas is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:36 +01:00
config BR2_PACKAGE_LIBEVAS
bool "libevas package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libevas is now provided by the efl package.
package/efl/libevas: remove package Libevas is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:36 +01:00
package/efl/libecore: remove package Libecore is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:35 +01:00
config BR2_PACKAGE_LIBECORE
bool "libecore package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libecore is now provided by the efl package.
package/efl/libecore: remove package Libecore is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:35 +01:00
package/efl/libedbus: remove package Libedbus is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:34 +01:00
config BR2_PACKAGE_LIBEDBUS
bool "libedbus package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libedbus is now provided by the efl package.
package/efl/libedbus: remove package Libedbus is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:34 +01:00
package/efl/libefreet: remove package Libefreet is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:33 +01:00
config BR2_PACKAGE_LIBEFREET
bool "libefreet package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libefreet is now provided by the efl package.
package/efl/libefreet: remove package Libefreet is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:33 +01:00
package/efl/libeio: remove package Libeio is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:32 +01:00
config BR2_PACKAGE_LIBEIO
bool "libeio package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libeio is now provided by the efl package.
package/efl/libeio: remove package Libeio is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:32 +01:00
package/efl/libembryo: remove package Libembryo is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:31 +01:00
config BR2_PACKAGE_LIBEMBRYO
bool "libembryo package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libembryo is now provided by the efl package.
package/efl/libembryo: remove package Libembryo is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:31 +01:00
package/efl/libedje: remove package Libedje is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:30 +01:00
config BR2_PACKAGE_LIBEDJE
bool "libedje package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libedje is now provided by the efl package.
package/efl/libedje: remove package Libedje is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:30 +01:00
package/efl/libethumb: remove package Libethumb is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:29 +01:00
config BR2_PACKAGE_LIBETHUMB
bool "libethumb package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_EFL
help
package/efl: rename libefl to efl This allow to keep backward compatibility with older defconfig files that used BR2_PACKAGE_EFL. Don't add Config.in.legacy entry for libefl since it's not part of any Buildroot release. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-19 17:39:16 +01:00
With EFL 1.15, libethumb is now provided by the efl package.
package/efl/libethumb: remove package Libethumb is now available in efl package. Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-15 23:40:29 +01:00
infozip: rename to zip We currently have a package named "infozip" for Info-Zip's Zip. With the upcoming addition of a package the Info-Zip's UnZip the name is becoming ambiguous. Rename it to the more specific name "zip". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Jan Pedersen <jp@jp-embedded.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-11-27 18:38:00 +01:00
config BR2_PACKAGE_INFOZIP
bool "infozip option has been renamed to zip"
select BR2_LEGACY
select BR2_PACKAGE_ZIP
help
Info-Zip's Zip package has been renamed from infozip to zip,
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
to avoid ambiguities with Info-Zip's UnZip which has been
added in the unzip package.
infozip: rename to zip We currently have a package named "infozip" for Info-Zip's Zip. With the upcoming addition of a package the Info-Zip's UnZip the name is becoming ambiguous. Rename it to the more specific name "zip". Signed-off-by: Luca Ceresoli <luca@lucaceresoli.net> Cc: Romain Naour <romain.naour@openwide.fr> Cc: Jan Pedersen <jp@jp-embedded.com> Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Reviewed-by: Romain Naour <romain.naour@openwide.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-11-27 18:38:00 +01:00
package/nodejs: correct 0.10.x option name The nodejs options incorrectly started BR2_BR2_xxx. This change corrects the name for 0.10.x releases to BR2_PACKAGE_NODEJS_0_10_X Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-23 13:16:04 +01:00
config BR2_BR2_PACKAGE_NODEJS_0_10_X
package/nodejs: remove version choice Remove the choice of nodejs version. Now automatically pick nodejs 0.10.x for armv5 architectures only and the latest nodejs for all other supported architectures. Note that the removal of BR2_PACKAGE_NODEJS_5_X is not handled in Config.in.legacy because buildroot has never been released with this option included. Signed-off-by: Martin Bark <martin@barkynet.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-30 15:51:00 +01:00
bool "nodejs 0.10.x option removed"
package/nodejs: correct 0.10.x option name The nodejs options incorrectly started BR2_BR2_xxx. This change corrects the name for 0.10.x releases to BR2_PACKAGE_NODEJS_0_10_X Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-23 13:16:04 +01:00
select BR2_LEGACY
select BR2_PACKAGE_NODEJS
help
package/nodejs: remove version choice Remove the choice of nodejs version. Now automatically pick nodejs 0.10.x for armv5 architectures only and the latest nodejs for all other supported architectures. Note that the removal of BR2_PACKAGE_NODEJS_5_X is not handled in Config.in.legacy because buildroot has never been released with this option included. Signed-off-by: Martin Bark <martin@barkynet.com> Cc: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Cc: Arnout Vandecappelle <arnout@mind.be> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2016-01-30 15:51:00 +01:00
nodejs 0.10.x option has been removed. 0.10.x is now
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
automatically chosen for ARMv5 architectures only and the
latest nodejs for all other supported architectures. The
correct nodejs version has been automatically selected in your
configuration.
package/nodejs: correct 0.10.x option name The nodejs options incorrectly started BR2_BR2_xxx. This change corrects the name for 0.10.x releases to BR2_PACKAGE_NODEJS_0_10_X Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-23 13:16:04 +01:00
package/nodejs: removed version 0.12.9 Remove 0.12.9 to rationalise the number of nodejs releases supported by buildroot. Going forward buildroot will only support the latest release of nodejs and the 0.10.x branch for armv5 support. Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-23 13:16:03 +01:00
config BR2_BR2_PACKAGE_NODEJS_0_12_X
bool "nodejs version 0.12.x has been removed"
select BR2_LEGACY
select BR2_PACKAGE_NODEJS
help
nodejs version 0.12.x has been removed. As an alternative,
the latest nodejs version has been automatically selected in
your configuration.
package/nodejs: bump version to 5.3.0 Replace 4.2.3 with 5.3.0. 5.3.0 is the current Stable release. See https://nodejs.org/en/blog/release/v5.3.0 for details on the release. Copied 4.2.3 patched to 5.3.0 with the following exceptions: - Removed 0004-fix-arm-vfpv2.patch, committed upstream and included in 5.3.0. See https://github.com/nodejs/node/commit/84dea1bd0c - Added 0004-Fix-va_list-not-declared.patch, fix for a new bug. This has already been fixed upstream but is not in 5.3.0 Signed-off-by: Martin Bark <martin@barkynet.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-12-23 13:16:02 +01:00
config BR2_BR2_PACKAGE_NODEJS_4_X
bool "nodejs version 4.x has been removed"
select BR2_LEGACY
select BR2_PACKAGE_NODEJS
help
nodejs version 4.x has been removed. As an alternative,
the latest nodejs version has been automatically selected in
your configuration.
boot/uboot: remove deprecated network settings option It's been deprecated since the 2014.05 release, so a year has passed. Add legacy info as well to raise a warning when it's used. [Peter: Remove entire config.h fixup handling] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-06-02 19:52:12 +02:00
###############################################################################
divine: remove package This commit removes the divine package, since the corresponding functionality has been merged in DirectFB itself since 1.7.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:10 +02:00
comment "Legacy options removed in 2015.11"
gst1-plugins-bad: update configure options - add new onvif option - add new dtls option - add new openh264 option - add new x265 option - removed real plugin option - add new rtp option - remove always disabled legacy options: directdraw, osx_video, quicktime and mythtv - add '--disable-bs2b' and '--disable-libde265' to options which require currently unpackaged libraries - add '--disable-gtk3' and '--disable-qt' [Thomas: improve wording of Config.in.legacy option.] Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-15 21:42:43 +02:00
config BR2_PACKAGE_GST1_PLUGINS_BAD_PLUGIN_REAL
bool "gst1-plugins-bad real plugin has been removed"
select BR2_LEGACY
help
The real plugin from GStreamer 1 bad plugins has been
removed.
media-ctl: remove package Package media-ctl is out-dated, source (and developement) have been moved to v4l-utils since June 2014. Up-to-date version is available in the libv4l package (BR2_PACKAGE_LIBV4L/BR2_PACKAGE_LIBV4L_UTILS). Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:48 +02:00
config BR2_PACKAGE_MEDIA_CTL
bool "media-ctl package has been removed"
select BR2_LEGACY
select BR2_PACKAGE_LIBV4L
select BR2_PACKAGE_LIBV4L_UTILS
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
media-ctl source and developement have been moved to v4l-utils
since June 2014. For an up-to-date media-ctl version select
BR2_PACKAGE_LIBV4L and BR2_PACKAGE_LIBV4L_UTILS.
media-ctl: remove package Package media-ctl is out-dated, source (and developement) have been moved to v4l-utils since June 2014. Up-to-date version is available in the libv4l package (BR2_PACKAGE_LIBV4L/BR2_PACKAGE_LIBV4L_UTILS). Signed-off-by: Peter Seiderer <ps.report@gmx.net> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:48 +02:00
package/schifra: remove package Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Arnaud Rébillout <rebillout@syscom.ch> Cc: Simon Dawson <spdawson@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-10-03 18:35:05 +02:00
config BR2_PACKAGE_SCHIFRA
bool "schifra package has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
package/schifra: remove package Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Arnaud Rébillout <rebillout@syscom.ch> Cc: Simon Dawson <spdawson@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-10-03 18:35:05 +02:00
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Schifra package has been maked broken since 2014.11 release
and haven't been fixed since then.
package/schifra: remove package Signed-off-by: Romain Naour <romain.naour@openwide.fr> Cc: Arnaud Rébillout <rebillout@syscom.ch> Cc: Simon Dawson <spdawson@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-10-03 18:35:05 +02:00
zxing-cpp: new package, replacing zxing ZXing was hosted on Google Code, which is a closing. The current link was already redirecting to the github repo. But upstream is no longer supporting the cpp bindings, it's now a Java library/application. A fork has been created from the latest cpp source of the original upstream. So this commit creates a new package, zxing-cpp, and adds Config.in.legacy handling for the old zxing pakcage that is removed. [Thomas: - add a patch that improves the CMakeLists.txt file to add installation rules. This allows to remove the manual installation logic from zxing-cpp.mk. - make libiconv a normal optional dependency. No need to involve BR2_ENABLE_LOCALE in the condition, since libiconv can only be enabled when !BR2_ENABLE_LOCALE. - bump to the latest upstream version. - add hash file.] Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-26 22:38:27 +02:00
config BR2_PACKAGE_ZXING
bool "zxing option has been renamed"
select BR2_LEGACY
select BR2_PACKAGE_ZXING_CPP
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
ZXing no longer provides the cpp bindings, it has been renamed
to BR2_PACKAGE_ZXING_CPP which uses a new upstream.
zxing-cpp: new package, replacing zxing ZXing was hosted on Google Code, which is a closing. The current link was already redirecting to the github repo. But upstream is no longer supporting the cpp bindings, it's now a Java library/application. A fork has been created from the latest cpp source of the original upstream. So this commit creates a new package, zxing-cpp, and adds Config.in.legacy handling for the old zxing pakcage that is removed. [Thomas: - add a patch that improves the CMakeLists.txt file to add installation rules. This allows to remove the manual installation logic from zxing-cpp.mk. - make libiconv a normal optional dependency. No need to involve BR2_ENABLE_LOCALE in the condition, since libiconv can only be enabled when !BR2_ENABLE_LOCALE. - bump to the latest upstream version. - add hash file.] Signed-off-by: Maxime Hadjinlian <maxime.hadjinlian@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-26 22:38:27 +02:00
package/freerdp: prepare for adding another client Currently, the only client we can build is the X11 client. FreeRDP now has support for building a wayland client. However, that means we need to rethink the way we build FreeRDP, because of some "inconsistencies" in its build system. This is because FreeRDP's buildsystem does not have orthogonal options; some of the options can be used for different components. For example, the set of X11 libraries needed to build the server is a superset of the X11 libraries needed to build the X11 client. So, whenever the server is enabled, it means the X11 libraries required to build the X11 client are available. Now, if the user also wants to build the waland client (but not the X11 client), there is no way to tell FreeRDP not to build the X11 client, because there is a single option, WITH_CLIENT, to drive whether any of the clients is built. The decision is made on the availability of the required libraries. And since the server is enabled, the X11 libs required to build the X11 client are available. So, we end up with the X11 client, even though it is not wanted. And conversely with wayland... So, we redesign the way we build FreeRDP. WE do not care what is actually built; we just build whatever is buildable with the current set of enabled libraries. But at install time (both in staging/ and target/) we remove whatever the user does not want. We also take the opportunity to rename the X11 client option, so it is coherent with the soon-to-be-introduced wayland client. Note: since FreeRDP has gained new dependencies, we can not just introduce the legacy option as-is, otherwise we run the risk that it selects the new option even though the new FreeRDP dependencies are not enabled, spitting out the infamous 'unmet direct dependencies" kconfig error. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-06 21:54:21 +02:00
# Since FreeRDP has new dependencies, protect this legacy to avoid the
# infamous "unmet direct dependencies" kconfig error.
config BR2_PACKAGE_FREERDP_CLIENT
bool "freerdp client option renamed"
depends on BR2_PACKAGE_FREERDP
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
package/freerdp: prepare for adding another client Currently, the only client we can build is the X11 client. FreeRDP now has support for building a wayland client. However, that means we need to rethink the way we build FreeRDP, because of some "inconsistencies" in its build system. This is because FreeRDP's buildsystem does not have orthogonal options; some of the options can be used for different components. For example, the set of X11 libraries needed to build the server is a superset of the X11 libraries needed to build the X11 client. So, whenever the server is enabled, it means the X11 libraries required to build the X11 client are available. Now, if the user also wants to build the waland client (but not the X11 client), there is no way to tell FreeRDP not to build the X11 client, because there is a single option, WITH_CLIENT, to drive whether any of the clients is built. The decision is made on the availability of the required libraries. And since the server is enabled, the X11 libs required to build the X11 client are available. So, we end up with the X11 client, even though it is not wanted. And conversely with wayland... So, we redesign the way we build FreeRDP. WE do not care what is actually built; we just build whatever is buildable with the current set of enabled libraries. But at install time (both in staging/ and target/) we remove whatever the user does not want. We also take the opportunity to rename the X11 client option, so it is coherent with the soon-to-be-introduced wayland client. Note: since FreeRDP has gained new dependencies, we can not just introduce the legacy option as-is, otherwise we run the risk that it selects the new option even though the new FreeRDP dependencies are not enabled, spitting out the infamous 'unmet direct dependencies" kconfig error. Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-06 21:54:21 +02:00
select BR2_PACKAGE_FREERDP_CLIENT_X11
blackbox: remove deprecated package Also update legacy as well. And remove the BR2_DEPRECATED_SINCE_2014_08 symbol since it's unused now. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-01 20:45:32 +02:00
config BR2_PACKAGE_BLACKBOX
bool "blackbox package has been removed"
select BR2_LEGACY
help
Upstream is dead and the package has been deprecated for
some time. There are other alternative maintained WMs.
linux-headers: remove deprecated versions 3.{0, 11, 13, 15} Remove for the upcoming 2015.11 release, they've been deprecated for a year now. Also remove some previously forgotten selection removals in legacy. [Peter: drop 3.0.x kernel patch] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-01 20:45:31 +02:00
config BR2_KERNEL_HEADERS_3_0
bool "kernel headers version 3.0.x are no longer supported"
select BR2_LEGACY
help
Version 3.0.x of the Linux kernel headers have been deprecated
for more than four buildroot releases and are now removed.
config BR2_KERNEL_HEADERS_3_11
bool "kernel headers version 3.11.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.11.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated versions 3.{0, 11, 13, 15} Remove for the upcoming 2015.11 release, they've been deprecated for a year now. Also remove some previously forgotten selection removals in legacy. [Peter: drop 3.0.x kernel patch] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-01 20:45:31 +02:00
config BR2_KERNEL_HEADERS_3_13
bool "kernel headers version 3.13.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.13.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated versions 3.{0, 11, 13, 15} Remove for the upcoming 2015.11 release, they've been deprecated for a year now. Also remove some previously forgotten selection removals in legacy. [Peter: drop 3.0.x kernel patch] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-01 20:45:31 +02:00
config BR2_KERNEL_HEADERS_3_15
bool "kernel headers version 3.15.x are no longer supported"
select BR2_LEGACY
help
Config.in*: re-wrap help text ... to follow the convention <tab><2 spaces><62 chars>. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:39 +02:00
Version 3.15.x of the Linux kernel headers have been
deprecated for more than four buildroot releases and are now
removed.
linux-headers: remove deprecated versions 3.{0, 11, 13, 15} Remove for the upcoming 2015.11 release, they've been deprecated for a year now. Also remove some previously forgotten selection removals in legacy. [Peter: drop 3.0.x kernel patch] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-01 20:45:31 +02:00
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
config BR2_PACKAGE_DIRECTFB_EXAMPLES_ANDI
bool "DirectFB example df_andi has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_BLTLOAD
bool "DirectFB example df_bltload has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_CPULOAD
bool "DirectFB example df_cpuload has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_DATABUFFER
bool "DirectFB example df_databuffer has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_DIOLOAD
bool "DirectFB example df_dioload has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_DOK
bool "DirectFB example df_dok has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_DRIVERTEST
bool "DirectFB example df_drivertest has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_FIRE
bool "DirectFB example df_fire has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_FLIP
bool "DirectFB example df_flip has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_FONTS
bool "DirectFB example df_fonts has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_INPUT
bool "DirectFB example df_input has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_JOYSTICK
bool "DirectFB example df_joystick has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_KNUCKLES
bool "DirectFB example df_knuckles has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_LAYER
bool "DirectFB example df_layer has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_MATRIX
bool "DirectFB example df_matrix has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_MATRIX_WATER
bool "DirectFB example df_matrix_water has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_NEO
bool "DirectFB example df_neo has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_NETLOAD
bool "DirectFB example df_netload has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_PALETTE
bool "DirectFB example df_palette has been removed"
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_PARTICLE
bool "DirectFB example df_particle has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_PORTER
bool "DirectFB example df_porter has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_STRESS
bool "DirectFB example df_stress has been removed"
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_TEXTURE
bool "DirectFB example df_texture has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_VIDEO
bool "DirectFB example df_video has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_VIDEO_PARTICLE
bool "DirectFB example df_video_particle has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
config BR2_PACKAGE_DIRECTFB_EXAMPLES_WINDOW
bool "DirectFB example df_window has been removed"
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
directfb-examples: remove options for each example For some historical reasons, the directfb-examples package has one sub-option for each example, and the .mk files go through some great lengths to install only the needed data files for each example. This is a bit silly for several reasons: * In no other Buildroot package we do offer such a fine-grained selection of what the package installs; * directfb-examples are examples, they are therefore typically not meant to be used on a final production system, but more during development or for demonstration. Those are situations where size generally isn't that critical (all installed, the package takes 2.4 MB on the rootfs); * Those options and the .mk file logic has to be updated whenever the package is bumped; * Users can always use a post-build script to keep only the examples they are interested in. All the options are moved to Config.in.legacy. However, we could debate on whether this is actually useful, since the main option BR2_PACKAGE_DIRECTFB_EXAMPLES will now install a superset of whatever was selected before through sub-options. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:14 +02:00
select BR2_PACKAGE_DIRECTFB_EXAMPLES
help
The per-DirectFB example options have been removed. The
BR2_PACKAGE_DIRECTFB_EXAMPLES option now installs all
examples.
kobs-ng: remove obsolete package In favor of imx-kobs maintained by Freescale. Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-09-23 15:39:27 +02:00
config BR2_PACKAGE_KOBS_NG
bool "kobs-ng was replaced by imx-kobs"
select BR2_LEGACY
select BR2_PACKAGE_IMX_KOBS
help
The outdated kobs-ng has been replaced by the Freescale-
maintained imx-kobs package.
sawman: remove package This commit removes the sawman package, since the corresponding functionality has been merged in DirectFB itself since 1.7.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:11 +02:00
config BR2_PACKAGE_SAWMAN
bool "sawman package removed"
select BR2_LEGACY
select BR2_PACKAGE_DIRECTFB_SAWMAN
help
This option has been removed because the sawman package no
longer exists: it was merged inside DirectFB itself. This
feature can now be enabled using the
BR2_PACKAGE_DIRECTFB_SAWMAN option.
divine: remove package This commit removes the divine package, since the corresponding functionality has been merged in DirectFB itself since 1.7.x. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-09-02 00:01:10 +02:00
config BR2_PACKAGE_DIVINE
bool "divine package removed"
select BR2_LEGACY
select BR2_PACKAGE_DIRECTFB_DIVINE
help
This option has been removed because the divine package no
longer exists: it was merged inside DirectFB itself. This
feature can now be enabled using the
BR2_PACKAGE_DIRECTFB_DIVINE option.
###############################################################################
boot/uboot: remove deprecated network settings option It's been deprecated since the 2014.05 release, so a year has passed. Add legacy info as well to raise a warning when it's used. [Peter: Remove entire config.h fixup handling] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-06-02 19:52:12 +02:00
comment "Legacy options removed in 2015.08"
package/kodi-pvr-addons: Prepare to split into addon-specific packages The PVR addons formerly being part of the xbmc-pvr-addons package were split into seperate packages being hosted on https://github.com/kodi-pvr This patch removes the old PVR addon package to prepare for the new PVR addon packages being added as subsequent patches. [Thomas: keep alphabetic ordering for addons, as noticed by Yann E. Morin.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:34 +02:00
config BR2_PACKAGE_KODI_PVR_ADDONS
bool "Kodi PVR addon was split"
select BR2_LEGACY
package/kodi-pvr-argustv: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:36 +02:00
select BR2_PACKAGE_KODI_PVR_ARGUSTV
package/kodi-pvr-dvblink: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:37 +02:00
select BR2_PACKAGE_KODI_PVR_DVBLINK
package/kodi-pvr-dvbviewer: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:38 +02:00
select BR2_PACKAGE_KODI_PVR_DVBVIEWER
package/kodi-pvr-filmon: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:39 +02:00
select BR2_PACKAGE_KODI_PVR_FILMON
package/kodi-pvr-hts: new package [Thomas: - use a shorter file as the license file, client.h - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:40 +02:00
select BR2_PACKAGE_KODI_PVR_HTS
package/kodi-pvr-iptvsimple: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:41 +02:00
select BR2_PACKAGE_KODI_PVR_IPTVSIMPLE
package/kodi-pvr-mediaportal-tvserver: new package [Thomas: - change <pkg>_LICENSE_FILES to a file that actually exists. - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:42 +02:00
select BR2_PACKAGE_KODI_PVR_MEDIAPORTAL_TVSERVER
package/kodi-pvr-mythtv: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:43 +02:00
select BR2_PACKAGE_KODI_PVR_MYTHTV
package/kodi-pvr-nextpvr: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:44 +02:00
select BR2_PACKAGE_KODI_PVR_NEXTPVR
package/kodi-pvr-njoy: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:45 +02:00
select BR2_PACKAGE_KODI_PVR_NJOY
package/kodi-pvr-pctv: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:46 +02:00
select BR2_PACKAGE_KODI_PVR_PCTV
package/kodi-pvr-stalker: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:47 +02:00
select BR2_PACKAGE_KODI_PVR_STALKER
package/kodi-pvr-vbox: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:48 +02:00
select BR2_PACKAGE_KODI_PVR_VBOX
package/kodi-pvr-vdr-vnsi: new package [Thomas: - use a shorter file as the license file, client.h - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:49 +02:00
select BR2_PACKAGE_KODI_PVR_VDR_VNSI
package/kodi-pvr-vuplus: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:50 +02:00
select BR2_PACKAGE_KODI_PVR_VUPLUS
package/kodi-pvr-wmc: new package [Thomas: - use a shorter file as the license file, client.h instead of client.cpp - do not pass -DCMAKE_MODULE_PATH, no longer needed.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:51 +02:00
select BR2_PACKAGE_KODI_PVR_WMC
package/kodi-pvr-addons: Prepare to split into addon-specific packages The PVR addons formerly being part of the xbmc-pvr-addons package were split into seperate packages being hosted on https://github.com/kodi-pvr This patch removes the old PVR addon package to prepare for the new PVR addon packages being added as subsequent patches. [Thomas: keep alphabetic ordering for addons, as noticed by Yann E. Morin.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:34 +02:00
help
*: fix typo for separate(d|) in text seperate is a common misspelling of separate Fix all the typos in the tree that are not related to patch files. CHANGES seperate -> separate, in the list of changes Config.in.legacy seperate -> separate, in option name and help texts package/leafnode2/leafnode2.mk seperate -> separate, in a comment system/Config.in seperated -> separated, in a help text Cc: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2022-11-27 14:07:15 +01:00
Kodi PVR addon was split into separate modules
package/kodi-pvr-addons: Prepare to split into addon-specific packages The PVR addons formerly being part of the xbmc-pvr-addons package were split into seperate packages being hosted on https://github.com/kodi-pvr This patch removes the old PVR addon package to prepare for the new PVR addon packages being added as subsequent patches. [Thomas: keep alphabetic ordering for addons, as noticed by Yann E. Morin.] Signed-off-by: Bernd Kuhls <bernd.kuhls@t-online.de> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-22 22:30:34 +02:00
binutils: rename config option Rename the binutils configuration option to match that one used by gcc where the patchlevel is explicitly left out. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-28 15:48:21 +02:00
config BR2_BINUTILS_VERSION_2_23_2
bool "binutils 2.23 option renamed"
select BR2_LEGACY
help
binutils: remove support for version 2.23 Now that we have added support for the lastest binutils version 2.26, it is time to remove the oldest version we currently support, 2.23, in order to keep only 3 versions: 2.24, 2.25 and 2.26. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2016-05-17 00:13:01 +02:00
Binutils 2.23.2 has been removed, using a newer version is
recommended.
binutils: rename config option Rename the binutils configuration option to match that one used by gcc where the patchlevel is explicitly left out. Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-28 15:48:21 +02:00
config BR2_BINUTILS_VERSION_2_24
bool "binutils 2.24 option renamed"
select BR2_LEGACY
select BR2_BINUTILS_VERSION_2_24_X
help
The binutils version option has been renamed to match the
same patchlevel logic used by gcc. The new option is now
BR2_BINUTILS_VERSION_2_24_X.
config BR2_BINUTILS_VERSION_2_25
bool "binutils 2.25 option renamed"
select BR2_LEGACY
select BR2_BINUTILS_VERSION_2_25_X
help
The binutils version option has been renamed to match the
same patchlevel logic used by gcc. The new option is now
BR2_BINUTILS_VERSION_2_25_X.
package/perf: migrate perf to use the new linux-tools infrastructure Remove the perf package and add legacy handling. [Thomas: - improve the Config.in.legacy help text - improve the comment explaining why we pass O= when building perf] Signed-off-by: Romain Naour <romain.naour@openwide.fr> Reviewed-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-07-14 19:35:14 +02:00
config BR2_PACKAGE_PERF
bool "perf option has been renamed"
select BR2_LEGACY
select BR2_LINUX_KERNEL_TOOL_PERF
help
The perf package has been moved as a Linux tools package,
and the option to enable it is now
BR2_LINUX_KERNEL_TOOL_PERF.
binutils: remove version 2.22 We already use 2.24 as the default, 2.25 has been around for some time, and 2.22 is clearly very old, so let's get rid of it. Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
2015-07-11 14:52:53 +02:00
config BR2_BINUTILS_VERSION_2_22
bool "binutils 2.22 removed"
select BR2_LEGACY
help
Binutils 2.22 has been removed, using a newer version is
recommended.
gpu-viv-bin-mx6q: rename package to imx-gpu-viv In order to be in line with new Freescale naming convention: https://github.com/Freescale/meta-fsl-arm/commit/74c86aa9 "Graphics recipe is renamed from gpu-viv-bin-mx6q to imx-gpu-viv" Signed-off-by: Gary Bisson <gary.bisson@boundarydevices.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-05-26 10:19:37 +02:00
config BR2_PACKAGE_GPU_VIV_BIN_MX6Q
bool "gpu-viv-bin-mx6q"
select BR2_LEGACY
select BR2_PACKAGE_IMX_GPU_VIV
help
Vivante graphics libraries have been renamed to
BR2_PACKAGE_IMX_GPU_VIV to be aligned with upstream package
name.
libsemanage: cleanup python use and license definition The original package supported python on target, now we just use it as part of the host tools. The license was also mis-assigned. [Thomas: add removed option to Config.in.legacy.] Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-02 15:28:35 +02:00
config BR2_PACKAGE_LIBSEMANAGE_PYTHON_BINDINGS
bool "libsemanage python bindings removed"
Config.in*: fix attributes order ... to follow the convention: type, default, depends on, select, help. Signed-off-by: Ricardo Martincoski <ricardo.martincoski@gmail.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
2018-04-01 07:08:33 +02:00
depends on BR2_PACKAGE_PYTHON
Config.in.legacy: add missing select BR2_LEGACY Signed-off-by: Peter Seiderer <ps.report@gmx.net> Acked-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-10-07 23:56:49 +02:00
select BR2_LEGACY
libsemanage: cleanup python use and license definition The original package supported python on target, now we just use it as part of the host tools. The license was also mis-assigned. [Thomas: add removed option to Config.in.legacy.] Signed-off-by: Matthew Weber <matthew.weber@rockwellcollins.com> Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
2015-06-02 15:28:35 +02:00
help
This option has been removed, since the libsemanage Python
bindings on the target were not useful.
boot/uboot: remove deprecated network settings option It's been deprecated since the 2014.05 release, so a year has passed. Add legacy info as well to raise a warning when it's used. [Peter: Remove entire config.h fixup handling] Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-06-02 19:52:12 +02:00
config BR2_TARGET_UBOOT_NETWORK
bool "U-Boot custom network settings removed"
select BR2_LEGACY
help
U-Boot's custom network settings options have been removed.
Legacy: make the menu a normal menu. The help text is moved to comments. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> Signed-off-by: Peter Korsgaard <jacmet@sunsite.dk>
2013-02-05 06:34:32 +01:00
endmenu
*config: improve handling of BR2_LEGACY In 8a46d4bf1f the randpackageconfig and allpackageyesconfig were extended with disabling all the legacy options, otherwise the resulting config couldn't be built. However, that didn't work for randconfig and allyesconfig. This commit reverts 8a46d4bf1f and replaces it with a different approach: skipping of the legacy config options is passed explicitly through the environment variable SKIP_LEGACY, which forces BR2_SKIP_LEGACY to y. The new option BR2_SKIP_LEGACY completely disables the legacy handling, which effectively removes all the legacy options from the .config. However, in that case no values are set for the legacy options so a subsequent oldconfig will query them. Therefore, run an additional olddefconfig. [Peter: fix s/BR2_LEGACY/SKIP_LEGACY/ typo] Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> [yann.morin.1998@free.fr: do not rely on a user-visible option, works perfectly well with only blind options set from the environment] Signed-off-by: "Yann E. MORIN" <yann.morin.1998@free.fr> Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
2015-04-11 01:49:02 +02:00
endif # !SKIP_LEGACY
Reference in New Issue Copy Permalink