buildroot/package/bash/bash.mk, branch 2018.02

package/bash: remove dead comment

2018-02-03T18:55:51+00:00

Commit 02e5cef1 (system: add option to choose what /bin/sh points to) removed the symlink creation, but forgot to remove the corresponding comment, which is now more puzzling than amusing... Remove the comment. Signed-off-by: "Yann E. MORIN" Cc: Romain Naour Cc: Peter Korsgaard Signed-off-by: Peter Korsgaard

package/bash: add /bin/bash to /etc/shells

2018-01-14T14:04:20+00:00

When bash is selected, /bin/bash is not added to /etc/shells (see man shells). So, login tools like dropbear reject the ssh connexions for users using bash as shell in /etc/passwd. buildroot authpriv.warn dropbear[853]: User 'kubu' has invalid shell, rejected Reported-by: Jeremy Rosen Signed-off-by: Romain Naour Cc: "Yann E. MORIN" Acked-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

bash: bump to 4.4.12

2017-11-22T21:19:09+00:00

In addition, remove upstreamed patches and add a hash for the license file. Signed-off-by: Adam Duskett [Thomas: indicate pgp signature file address in hash file, as suggested by Baruch.] Signed-off-by: Thomas Petazzoni

bash: fix static build

2017-09-24T13:22:13+00:00

When building bash statically, configure does not initialize the SHOBJ_STATUS variable. The SHOBJ_STATUS make variable in examples/loadables/Makefile.in must resolve to either 'supported' or 'unsupported'. Otherwise, the install-$(SHOBJ_STATUS) target does not exist. This leads to the following build failure: make[2]: Entering directory '.../output/build/bash-4.4/examples/loadables' make[2]: *** No rule to make target 'install-', needed by 'install'. Stop. make[2]: Leaving directory '.../output/build/bash-4.4/examples/loadables' Makefile:793: recipe for target 'install' failed with the following defconfig: BR2_arm=y BR2_STATIC_LIBS=y BR2_PACKAGE_BUSYBOX_SHOW_OTHERS=y BR2_PACKAGE_BASH=y Note that this doesn't terminate the build so it's not detected as an error by the autobuilders. Set SHOBJ_STATUS in the configure environment as a workaround. Signed-off-by: Baruch Siach Signed-off-by: Arnout Vandecappelle (Essensium/Mind)

bash: disable bash malloc by default

2017-05-31T20:36:15+00:00

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 Signed-off-by: Thomas Petazzoni

boot, package: use SPDX short identifier for GPLv3/GPLv3+

2017-04-01T13:17:59+00:00

We want to use SPDX identifier for license string as much as possible. SPDX short identifier for GPLv3/GPLv3+ is GPL-3.0/GPL-3.0+. This change is done using following command. find . -name "*.mk" | xargs sed -ri '/LICENSE( )?[\+:]?=/s/\/GPL-3.0/g' Signed-off-by: Rahul Bedarkar Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Thomas Petazzoni

bash: bump version to 4.4

2016-11-30T11:02:19+00:00

Signed-off-by: Vicente Olivert Riera Signed-off-by: Peter Korsgaard

bash re-enable parallel builds

2016-03-12T22:55:06+00:00

They don't seem to be causing any issues after bumping to the 4.3.x series and several tests. Signed-off-by: Gustavo Zacarias Tested-by: "Yann E. MORIN" Reviewed-by: "Yann E. MORIN" Signed-off-by: Thomas Petazzoni

package/bash: indicate getcwd is malloc-supported

2015-09-04T14:45:42+00:00

When Bash attempts to find the current working directory, it uses a C library call `getcwd` to resolve it. When cross-compiling, the configuration process cannot determine if the target system's C library can support an "unfixed" path length. Therefore, Bash will fallback to a size of `PATH_MAX` for determining the current working directory. When using OverlayFS (and possible other file systems), this becomes an issue since file paths can commonly exceed standard `PATH_MAX` length. This typically results in the following error appearing: error retrieving current directory: [...] Common C library `getcwd` calls can default to a higher limit (usually the system's page size). The current configurable C libraries (as of at least 2015.08) support a zero (0) size buffer length. Most use the system's page size; musl, being an exception, which defaults to `PATH_MAX` (as Bash was doing). Since these C libraries support allocating buffer space with a zero (0) provided size, the following configuration change allows Bash to support getting a larger-length'ed working directory on target's that support it. Signed-off-by: James Knight Acked-by: Arnout Vandecappelle (Essensium/Mind) Signed-off-by: Peter Korsgaard

Rename BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS

2014-12-11T21:48:13+00:00

Since a while, the semantic of BR2_PREFER_STATIC_LIB has been changed from "prefer static libraries when possible" to "use only static libraries". The former semantic didn't make much sense, since the user had absolutely no control/idea of which package would use static libraries, and which packages would not. Therefore, for quite some time, we have been starting to enforce that BR2_PREFER_STATIC_LIB should really build everything with static libraries. As a consequence, this patch renames BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS, and adjust the Config.in option accordingly. This also helps preparing the addition of other options to select shared, shared+static or just static. Note that we have verified that this commit can be reproduced by simply doing a global rename of BR2_PREFER_STATIC_LIB to BR2_STATIC_LIBS plus adding BR2_PREFER_STATIC_LIB to Config.in.legacy. Signed-off-by: Thomas Petazzoni Reviewed-by: "Yann E. MORIN"