Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch : > >> if you have installed firmware remove it if possible. > > The install Process check that /usr/include/machine is empty. > >> then check that the directory /usr/include/machine is empty. > > If not clean it. > > I think this part is way off and probably all the way into "bad advice". > > > > Cleaning /usr/include/machine is wrong, and fw_update seems completely > > unrelated to either the contents of the C includes or building WG. > > but without cleaning /usr/include/machine the install Process fails ... > I made an amd64 VM to test and it went fine: ... golang.zx2c4.com/wireguard/tun golang.zx2c4.com/wireguard/device golang.zx2c4.com/wireguard install -d "/usr/local/bin" && install -m 0755 "wireguard-go" "/usr/local/bin/wireguard-go" gmake: Leaving directory '/usr/src/wireguard/wireguard-go-0.0.20190908' [+] Cleaning up build directory comptest# ls /usr/include/machine/ _float.h exec.h limits.h rbus_machdep.h _types.h fenv.h loadfile_machdep.h reg.h ... I think your comp-less box was messed up in more ways than you know, probably because of the random "lets poke here, rerun unrelated fw_update there" and you had no idea which of your actions made it back into a usable shape again. Redo your test from scratch (without skipping the compiler set) and post the output on a pastebin. If there is an error it needs to get fixed for real and not with hand-wavingly delete include files needed for other things. -- May the most significant bit of your life be positive.