about summary refs log tree commit diff
diff options
context:
space:
mode:
authorNilstrieb <48135649+Nilstrieb@users.noreply.github.com>2023-09-08 22:30:50 +0200
committerGitHub <noreply@github.com>2023-09-08 22:30:50 +0200
commit5864245d89b664fce9014bea811e6e6720dd949d (patch)
tree08650e953cb3ccf925c2e7760bc96d92b3791a50
parent6e4fd87002c7ebf24a8c97dfad0f0df2701cfb4c (diff)
downloadrust-5864245d89b664fce9014bea811e6e6720dd949d.tar.gz
rust-5864245d89b664fce9014bea811e6e6720dd949d.zip
Use `#!/usr/bin/env` shebang
```
$ ls /bin/bash
ls: cannot access '/bin/bash': No such file or directory
```

On certain systems, `/bin` and `/usr/bin` are nothing but wastelands, with just `env`around as the last survivor of the great purge. The binaries have cowardly hidden away and only `env` can show us the way to greatness (bash).
❄️
-rwxr-xr-xsrc/tools/miri/miri2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/tools/miri/miri b/src/tools/miri/miri
index 938df9799da..e21738c3618 100755
--- a/src/tools/miri/miri
+++ b/src/tools/miri/miri
@@ -1,4 +1,4 @@
-#!/bin/bash
+#!/usr/bin/env bash
 set -e
 # Instead of doing just `cargo run --manifest-path .. $@`, we invoke miri-script binary directly. Invoking `cargo run` goes through
 # rustup (that sets it's own environmental variables), which is undesirable.