From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] BASH: Adding features that can not be automatically detected while cross-compiling
Date: Sun, 15 Jan 2012 07:30:57 -0600 [thread overview]
Message-ID: <201201150730.59076.minimod@morethan.org> (raw)
In-Reply-To: <CA+gTGJGUmtWp2cnyrP=Za7=ySQmiQ3REWxJatydJCKv6et-OzQ@mail.gmail.com>
On Sun January 15 2012, Arkady Gilinsky wrote:
> From: Arkady Gilinsky <arcadyg@gmail.com>
> Date: Sat, 14 Jan 2012 11:27:11 +0200
> Subject: [PATCH] BASH: Adding features that can not be automatically
> detected
> while cross-compiling
>
A note on your post -
When you write the post in HTML and then rely on your e-mail
client to create a plain-text version, the usual result is
garbage-text, unusable by the patch program.
Please author your post as plain text to begin with.
This mailing list prefers a plain-text file (makes it easier
to review, both now and in the archives).
If using an e-mail client that you can't control enough to
ensure a plain-text post, at least attach the plain-text file.
Mike
> There are some bash features that can not be detected automatically during
> configure stage while cross-compiling. This commit add ability to force
> support of such a features.
>
> Signed-off-by: Arkady Gilinsky <arcadyg@gmail.com>
> ---
> package/bash/Config.in | 33 +++++++++++++++++++++++++++++++++
> package/bash/bash.mk | 6 +++++-
> 2 files changed, 38 insertions(+), 1 deletions(-)
>
> diff --git a/package/bash/Config.in b/package/bash/Config.in
> index 9ee46e8..b7cc27d 100644
> --- a/package/bash/Config.in
> +++ b/package/bash/Config.in
> @@ -5,3 +5,36 @@ config BR2_PACKAGE_BASH
> The standard GNU Bourne again shell.
>
> http://tiswww.case.edu/php/chet/bash/bashtop.html
> +
> +menu "BASH cross compile features selection"
> + depends on BR2_PACKAGE_BASH
> +
> +config BR2_PACKAGE_BASH_JOB_CONTROL
> + bool "job_control"
> + depends on BR2_PACKAGE_BASH
> + help
> + The job control feature (Ctrl-Z and etc.)
> + Configure variable - bash_cv_job_control_missing
> +
> +config BR2_PACKAGE_BASH_NAMED_PIPES
> + bool "named_pipes"
> + depends on BR2_PACKAGE_BASH
> + help
> + Named pipe presence
> + Configure variable - bash_cv_sys_named_pipes
> +
> +config BR2_PACKAGE_BASH_SIG_SET_JUMP
> + bool "sigsetjmp"
> + depends on BR2_PACKAGE_BASH
> + help
> + POSIX-style sigsetjmp/siglongjmp
> + Configure variable - bash_cv_func_sigsetjmp
> +
> +config BR2_PACKAGE_BASH_PRINTF_A_FORMAT
> + bool "printf_a_format"
> + depends on BR2_PACKAGE_BASH
> + help
> + Printf floating point output in hex notation
> + Configure variable - bash_cv_printf_a_format
> +
> +endmenu
> diff --git a/package/bash/bash.mk b/package/bash/bash.mk
> index f1f951c..78face7 100644
> --- a/package/bash/bash.mk
> +++ b/package/bash/bash.mk
> @@ -7,7 +7,11 @@
> BASH_VERSION = 4.2
> BASH_SITE = $(BR2_GNU_MIRROR)/bash
> BASH_DEPENDENCIES = ncurses
> -BASH_CONF_ENV = bash_cv_job_control_missing=no
> +BASH_CONF_ENV
> += \
> + bash_cv_job_control_missing=$(if
> $(BR2_PACKAGE_BASH_JOB_CONTROL),present,no) \
> + $(if $(BR2_PACKAGE_BASH_NAMED_PIPES),
> bash_cv_sys_named_pipes=present,) \
> + $(if $(BR2_PACKAGE_BASH_SIG_SET_JUMP),
> bash_cv_func_sigsetjmp=present,) \
> + $(if $(BR2_PACKAGE_BASH_PRINTF_A_FORMAT), bash_cv_printf_a_format=yes,)
>
> # Make sure we build after busybox so that /bin/sh links to bash
> ifeq ($(BR2_PACKAGE_BUSYBOX),y)
> --
> 1.7.7
>
>
>
next prev parent reply other threads:[~2012-01-15 13:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-15 6:11 [Buildroot] [PATCH] BASH: Adding features that can not be automatically detected while cross-compiling Arkady Gilinsky
2012-01-15 13:30 ` Michael S. Zick [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-01-15 17:14 Arkady Gilinsky
2012-01-17 17:18 ` Arnout Vandecappelle
2012-01-17 22:40 ` Michael S. Zick
2012-01-17 22:49 ` Steve Calfee
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=201201150730.59076.minimod@morethan.org \
--to=minimod@morethan.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