summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--config/binutils/binutils.in19
1 files changed, 12 insertions, 7 deletions
diff --git a/config/binutils/binutils.in b/config/binutils/binutils.in
index 91b5e9f..511f0b2 100644
--- a/config/binutils/binutils.in
+++ b/config/binutils/binutils.in
@@ -43,15 +43,15 @@ config CC_BINUTILS_SHOW_LINARO
help
Linaro is maintaining some advanced/more stable/experimental versions
of binutils, especially for the ARM architecture.
-
+
Those versions have not been blessed by the binutils comunity (nor have they
been cursed either!), but they look to be pretty much stable, and even
more stable than the upstream versions. YMMV...
-
+
If you do not know what this Linaro stuff is, then simply say 'n' here,
and rest in peace. OTOH, if you know what you are doing, you will be
able to use and enjoy :-) the Linaro versions by saying 'y' here.
-
+
Linaro: http://www.linaro.org/
choice
@@ -60,6 +60,11 @@ choice
# Don't remove next line
# CT_INSERT_VERSION_BELOW
+config BINUTILS_V_2_27
+ bool
+ prompt "2.27"
+ select BINUTILS_2_27_or_later
+
config BINUTILS_V_2_26
bool
prompt "2.26"
@@ -192,7 +197,7 @@ config BINUTILS_LINKER_LD_GOLD
help
Both the historical ld and the new gold linkers will be
installed, with ld being the default linker used.
-
+
See help for gold, above.
config BINUTILS_LINKER_GOLD_LD
@@ -205,7 +210,7 @@ config BINUTILS_LINKER_GOLD_LD
help
Both the historical ld and the new gold linkers will be
installed, with gold being the default linker used.
-
+
See help for gold, above.
endchoice # Enable linkers
@@ -242,7 +247,7 @@ config BINUTILS_LD_WRAPPER
depends on BINUTILS_LINKER_BOTH
help
Add an ld wrapper that calls to either gold or ld.
-
+
By default, the wrapper will call to the default wrapper,
but if you set the environment variable CTNG_LD_IS, you
can change which linker will get called:
@@ -270,7 +275,7 @@ config BINUTILS_EXTRA_CONFIG_ARRAY
default ""
help
Extra flags passed onto ./configure when configuring
-
+
You can enter multiple arguments here, and arguments can contain spaces
if they are properly quoted (or escaped, but prefer quotes). Eg.:
--with-foo="1st arg with 4 spaces" --with-bar=2nd-arg-without-space