From: Arnout Vandecappelle <arnout@mind.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v4] bash: fix linking for static builds with uClibc toolchains
Date: Wed, 22 Oct 2014 18:27:30 +0200 [thread overview]
Message-ID: <5447DAF2.1070504@mind.be> (raw)
In-Reply-To: <1413970840-17304-1-git-send-email-Vincent.Riera@imgtec.com>
On 22/10/14 11:40, Vicente Olivert Riera wrote:
> bash fails to link for static builds with uClibc toolchains due to
> getenv redefinitions. This is caused because bash is unable to check if
> getenv is already defined when cross-compiling, so it defaults to 'yes':
>
> configure:14438: WARNING: cannot check getenv redefinition if cross
> compiling -- defaulting to yes
>
> We can avoid this redefinition by passing bash_cv_getenv_redef=no to the
> configure script.
>
> Related:
> http://lists.gnu.org/archive/html/bug-bash/2012-03/msg00052.html
>
> Fixes:
> http://autobuild.buildroot.net/results/a20/a2007e6dbcfe53e7cd837ae642869ee26376826a/
>
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
Reviewed-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be>
Small additional remark...
> ---
> package/bash/bash.mk | 11 +++++++++++
> 1 files changed, 11 insertions(+), 0 deletions(-)
>
> diff --git a/package/bash/bash.mk b/package/bash/bash.mk
> index 34a3a73..5eec3cc 100644
> --- a/package/bash/bash.mk
> +++ b/package/bash/bash.mk
> @@ -28,6 +28,17 @@ BASH_MAKE = $(MAKE1)
> # The static build needs some trickery
> ifeq ($(BR2_PREFER_STATIC_LIB),y)
> BASH_CONF_OPTS += --enable-static-link --without-bash-malloc
> +# bash wants to redefine the getenv() function. To check whether this is
> +# possible, AC_TRY_RUN is used which is not possible in
> +# cross-compilation.
> +# On uClibc, redefining getenv is not possible; on glibc and musl it is.
I failed to notice earlier: glibc is not available on static builds so it
doesn't make a lot of sense to mention it here.
Regards,
Arnout
> +# Related:
> +# http://lists.gnu.org/archive/html/bug-bash/2012-03/msg00052.html
> +ifeq ($(BR2_TOOLCHAIN_USES_UCLIBC),y)
> +BASH_CONF_ENV += bash_cv_getenv_redef=no
> +else
> +BASH_CONF_ENV += bash_cv_getenv_redef=yes
> +endif
> endif
>
> # Make /bin/sh -> bash (no other shell, better than busybox shells)
>
--
Arnout Vandecappelle arnout at mind be
Senior Embedded Software Architect +32-16-286500
Essensium/Mind http://www.mind.be
G.Geenslaan 9, 3001 Leuven, Belgium BE 872 984 063 RPR Leuven
LinkedIn profile: http://www.linkedin.com/in/arnoutvandecappelle
GPG fingerprint: 7CB5 E4CC 6C2E EFD4 6E3D A754 F963 ECAB 2450 2F1F
next prev parent reply other threads:[~2014-10-22 16:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-22 9:40 [Buildroot] [PATCH v4] bash: fix linking for static builds with uClibc toolchains Vicente Olivert Riera
2014-10-22 10:39 ` Markos Chandras
2014-10-22 10:42 ` Vicente Olivert Riera
2014-10-22 16:27 ` Arnout Vandecappelle [this message]
2014-10-25 10:45 ` Thomas Petazzoni
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=5447DAF2.1070504@mind.be \
--to=arnout@mind.be \
--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