>> Solution: replace >> the #!/bin/sh with #!/usr/bin/env -c /bin/bash. Why not? > > Because there are plenty of systems out there without env or bash.
Worth a try, though! There is very little shell code left in the Go release. Maybe I'll give it a try on my pristine NetBSD machine. But note that even if it does work, it is still not possible for the Go Team to release the scripts as /bin/sh scripts because, as you have clearly not yet grasped, not all /bin/sh instances out there can be shown to be compatible with any one /bin/sh script, not matter how "portable"! Maybe the following illustration will help: Given Unix, Plan 9 and Windows as target platforms, how does one go about releasing a single build environment for all of them that on invocation automatically produces the target package? I didn't give it a lot of thought, but it seems to me that the totally general build (bootstrap?) operation for this purpose does not (and, it seems to me, cannot) exist. ++L
