From: Daniel Sabogal <dsabogalcc@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] bash: disable bash malloc by default
Date: Tue, 23 May 2017 13:19:31 -0400 [thread overview]
Message-ID: <20170523171931.18744-1-dsabogalcc@gmail.com> (raw)
Bash's malloc relies on sbrk which is implemented as
a fail-only stub in musl. Presently, it is disabled
when configured for static libs. Instead, default to
using libc malloc.
Fixes:
# bash
bash: xmalloc: locale.c:81: cannot allocate 18 bytes (0 bytes allocated)
Signed-off-by: Daniel Sabogal <dsabogalcc@gmail.com>
---
package/bash/bash.mk | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/package/bash/bash.mk b/package/bash/bash.mk
index 639f01204..32c87a659 100644
--- a/package/bash/bash.mk
+++ b/package/bash/bash.mk
@@ -9,7 +9,7 @@ BASH_SITE = $(BR2_GNU_MIRROR)/bash
# Build after since bash is better than busybox shells
BASH_DEPENDENCIES = ncurses readline host-bison \
$(if $(BR2_PACKAGE_BUSYBOX),busybox)
-BASH_CONF_OPTS = --with-installed-readline
+BASH_CONF_OPTS = --with-installed-readline --without-bash-malloc
BASH_LICENSE = GPL-3.0+
BASH_LICENSE_FILES = COPYING
@@ -24,7 +24,7 @@ BASH_CONF_ENV += \
# The static build needs some trickery
ifeq ($(BR2_STATIC_LIBS),y)
-BASH_CONF_OPTS += --enable-static-link --without-bash-malloc
+BASH_CONF_OPTS += --enable-static-link
# 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.
--
2.13.0
next reply other threads:[~2017-05-23 17:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-23 17:19 Daniel Sabogal [this message]
2017-05-31 20:37 ` [Buildroot] [PATCH] bash: disable bash malloc by default Thomas Petazzoni
2017-06-01 14:44 ` Peter Korsgaard
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=20170523171931.18744-1-dsabogalcc@gmail.com \
--to=dsabogalcc@gmail.com \
--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