ff12a7954c
As in2a5fcfae02and in3e67e5c992using /usr/bin/env allows bash to be looked up in PATH rather than being hard-coded. As with the previous changes the same arguments apply - distributions have scripts to rewrite shebangs on installation and they know what locations to rely on. - For tests/compilation we should rather rely on the user to have setup there PATH correctly. In particular this makes testing from git easier on NixOS where do not provide /bin/bash to improve compose-ability.
14 lines
374 B
Bash
Executable file
14 lines
374 B
Bash
Executable file
#!/usr/bin/env bash
|
|
|
|
set -eu
|
|
|
|
for i in *.h */*.h; do
|
|
if [[ $i == 'wireguard.h' ]]; then
|
|
curl https://raw.githubusercontent.com/WireGuard/WireGuard/master/src/uapi/$i -o $i
|
|
else
|
|
curl https://raw.githubusercontent.com/torvalds/linux/master/include/uapi/linux/$i -o $i
|
|
fi
|
|
|
|
sed -i -e 's/__user //g' -e '/^#include <linux\/compiler.h>/ d' $i
|
|
done
|