diff options
| author | Romain GEISSLER <romain.geissler@amadeus.com> | 2021-05-12 07:45:33 +0530 |
|---|---|---|
| committer | Siddhesh Poyarekar <siddhesh@sourceware.org> | 2021-05-12 07:47:11 +0530 |
| commit | 5188a9d0265cc6f7235a8af1d31ab02e4a24853d (patch) | |
| tree | 048496f1c8a02ab8db081ee3f016be726514a39f /stdio-common/scanf14a.c | |
| parent | fec776b827755a0aac17a0745bc38c2329aad5ca (diff) | |
| download | glibc-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 'stdio-common/scanf14a.c')
0 files changed, 0 insertions, 0 deletions