From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] bash: Adding features that can not be automatically detected while cross-compiling
Date: Wed, 18 Jan 2012 00:07:43 +0100 [thread overview]
Message-ID: <87wr8qnd1c.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <1326821128-29133-1-git-send-email-arnout@mind.be> (Arnout Vandecappelle's message of "Tue, 17 Jan 2012 18:25:28 +0100")
>>>>> "Arnout" == Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> writes:
Arnout> From: Arkady Gilinsky <arcadyg@gmail.com>
Arnout> There are some bash features that can not be detected
Arnout> automatically during configure stage while
Arnout> cross-compiling. This commit adds the ability to force support
Arnout> of such features.
Ok, but does it make sense to make these things configurable? I haven't
checked, but presumably these are supported on all Linux archs, and
don't affect the binary size significantly (compared to bash size)?
Couldn't we just always forcibly enable these instead?
Arnout> Signed-off-by: Arkady Gilinsky <arcadyg@gmail.com>
Arnout> Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Arnout> ---
Arnout> package/bash/Config.in | 26 ++++++++++++++++++++++++++
Arnout> package/bash/bash.mk | 6 +++++-
Arnout> 2 files changed, 31 insertions(+), 1 deletions(-)
Arnout> diff --git a/package/bash/Config.in b/package/bash/Config.in
Arnout> index 9ee46e8..74f03e0 100644
Arnout> --- a/package/bash/Config.in
Arnout> +++ b/package/bash/Config.in
Arnout> @@ -5,3 +5,29 @@ config BR2_PACKAGE_BASH
Arnout> The standard GNU Bourne again shell.
Arnout> http://tiswww.case.edu/php/chet/bash/bashtop.html
Arnout> +
Arnout> +if BR2_PACKAGE_BASH
Arnout> +
Arnout> +comment "Bash features that cannot be derived automatically when cross-compiling"
Arnout> +
Arnout> +config BR2_PACKAGE_BASH_JOB_CONTROL
Arnout> + bool "job_control"
Arnout> + help
Arnout> + The job control feature (Ctrl-Z and etc.)
Arnout> +
Arnout> +config BR2_PACKAGE_BASH_NAMED_PIPES
Arnout> + bool "named_pipes"
Arnout> + help
Arnout> + Named pipe presence
Arnout> +
Arnout> +config BR2_PACKAGE_BASH_SIG_SET_JUMP
Arnout> + bool "sigsetjmp"
Arnout> + help
Arnout> + POSIX-style sigsetjmp/siglongjmp
Arnout> +
Arnout> +config BR2_PACKAGE_BASH_PRINTF_A_FORMAT
Arnout> + bool "printf_a_format"
Arnout> + help
Arnout> + Printf floating point output in hex notation
Arnout> +
Arnout> +endif
Arnout> diff --git a/package/bash/bash.mk b/package/bash/bash.mk
Arnout> index f1f951c..78face7 100644
Arnout> --- a/package/bash/bash.mk
Arnout> +++ b/package/bash/bash.mk
Arnout> @@ -7,7 +7,11 @@
Arnout> BASH_VERSION = 4.2
Arnout> BASH_SITE = $(BR2_GNU_MIRROR)/bash
Arnout> BASH_DEPENDENCIES = ncurses
Arnout> -BASH_CONF_ENV = bash_cv_job_control_missing=no
Arnout> +BASH_CONF_ENV += \
Arnout> + bash_cv_job_control_missing=$(if $(BR2_PACKAGE_BASH_JOB_CONTROL),present,no) \
Arnout> + $(if $(BR2_PACKAGE_BASH_NAMED_PIPES), bash_cv_sys_named_pipes=present,) \
Arnout> + $(if $(BR2_PACKAGE_BASH_SIG_SET_JUMP), bash_cv_func_sigsetjmp=present,) \
Arnout> + $(if $(BR2_PACKAGE_BASH_PRINTF_A_FORMAT), bash_cv_printf_a_format=yes,)
Arnout> # Make sure we build after busybox so that /bin/sh links to bash
Arnout> ifeq ($(BR2_PACKAGE_BUSYBOX),y)
Arnout> --
Arnout> 1.7.8.3
Arnout> _______________________________________________
Arnout> buildroot mailing list
Arnout> buildroot at busybox.net
Arnout> http://lists.busybox.net/mailman/listinfo/buildroot
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2012-01-17 23:07 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 17:14 [Buildroot] [PATCH] BASH: Adding features that can not be automatically detected while cross-compiling Arkady Gilinsky
2012-01-17 17:18 ` Arnout Vandecappelle
2012-01-17 22:40 ` Michael S. Zick
2012-01-17 22:49 ` Steve Calfee
2012-01-17 17:22 ` [Buildroot] [PATCH] BASH: Adding features that can not be automatically detected Arnout Vandecappelle
2012-01-17 17:25 ` [Buildroot] [PATCH v2] bash: Adding features that can not be automatically detected while cross-compiling Arnout Vandecappelle
2012-01-17 23:07 ` Peter Korsgaard [this message]
2012-01-18 6:37 ` Arkady Gilinsky
2012-01-18 11:30 ` Arnout Vandecappelle
2012-01-18 11:31 ` [Buildroot] [PATCH v3] " Arnout Vandecappelle
2012-01-18 12:42 ` Arkady Gilinsky
2012-01-19 12:22 ` [Buildroot] [PATCH v4] " Arnout Vandecappelle
2012-01-19 12:27 ` Arnout Vandecappelle
2012-01-20 8:23 ` Peter Korsgaard
2012-01-20 20:54 ` Arnout Vandecappelle
2012-01-22 20:57 ` Peter Korsgaard
2012-01-20 8:19 ` Peter Korsgaard
2012-01-18 11:36 ` [Buildroot] [PATCH v2] " Arnout Vandecappelle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87wr8qnd1c.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox