summary refs log tree commit diff
path: root/timezone
diff options
context:
space:
mode:
authorRomain GEISSLER <romain.geissler@amadeus.com>2021-05-12 07:45:33 +0530
committerSiddhesh Poyarekar <siddhesh@sourceware.org>2021-05-12 07:47:11 +0530
commit5188a9d0265cc6f7235a8af1d31ab02e4a24853d (patch)
tree048496f1c8a02ab8db081ee3f016be726514a39f /timezone
parentfec776b827755a0aac17a0745bc38c2329aad5ca (diff)
downloadglibc-5188a9d0265cc6f7235a8af1d31ab02e4a24853d.tar.gz
glibc-5188a9d0265cc6f7235a8af1d31ab02e4a24853d.tar.xz
glibc-5188a9d0265cc6f7235a8af1d31ab02e4a24853d.zip
Remove all usage of @BASH@ or ${BASH} in installed files, and hardcode /bin/bash instead
(FYI, this is a repost of
https://sourceware.org/pipermail/libc-alpha/2019-July/105035.html now
that FSF papers have been signed and confirmed on FSF side).

This trivial patch attemps to fix BZ 24106. Basically the bash locally
used when building glibc on the host shall not leak on the installed
glibc, as the system where it is installed might be different and use
another bash location.

So I have looked for all occurences of @BASH@ or $(BASH) in installed
files, and replaced it by /bin/bash. This was suggested by Florian
Weimer in the bug report.

Reviewed-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Diffstat (limited to 'timezone')
-rw-r--r--timezone/Makefile3
1 files changed, 1 insertions, 2 deletions
diff --git a/timezone/Makefile b/timezone/Makefile
index 395abfeebd..c624a189b3 100644
--- a/timezone/Makefile
+++ b/timezone/Makefile
@@ -123,8 +123,7 @@ $(testdata)/XT%: testdata/XT%
 	cp $< $@
 
 $(objpfx)tzselect: tzselect.ksh $(common-objpfx)config.make
-	sed -e 's|/bin/bash|$(BASH)|' \
-	    -e 's|TZDIR=[^}]*|TZDIR=$(zonedir)|' \
+	sed -e 's|TZDIR=[^}]*|TZDIR=$(zonedir)|' \
 	    -e '/TZVERSION=/s|see_Makefile|"$(version)"|' \
 	    -e '/PKGVERSION=/s|=.*|="$(PKGVERSION)"|' \
 	    -e '/REPORT_BUGS_TO=/s|=.*|="$(REPORT_BUGS_TO)"|' \