esden
commented
3 years ago Thank you for bringing up this issue.
The script itself does not use sed. So I assume this issue appears from the incompatible use of sed inside one of the tools we build. I think it would be better to address the issue up stream inside the respective project to update the way sed is being used so that it works with the gnu and bsd sed versions.
On MacOS/BSD sed has a slightly different syntax that breaks the script.
To fix this:
brew install gnu-sed PATH="/usr/local/opt/gnu-sed/libexec/gnubin:$PATH"
and then run the script.
This will use gsed, the gnu version of sed for the install which runs through as it has standard sed command line parameters