Build fail on OpenBSD 6.5 amd64
Hello @ all
i found the Solution.
But first the Problem.
The set comp65 is not installed.
Solution :
if you have installed firmware remove it if possible.
The install Process check that /usr/include/machine is empty.
My way was.
foo#fw_update -ad
then check that the directory /usr/include/machine is empty.
If not clean it.
reboot to bsd.rd
install the set comp65
reboot
then
foo#fw_update -a
then the script run Perfect.
Regards
Ulli
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
Den tis 24 sep. 2019 kl 11:00 skrev Ulrich Kalloch <[email protected]>:
Quoted 2 lines
Hello @ all
if you have installed firmware remove it if possible.
The install Process check that /usr/include/machine is empty.
Quoted 1 line
then check that the directory
/usr/include/machineis empty.
If not clean it.
Quoted 1 line
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.
You didn't have the compiler installed which what was causing your issues with building wg and I think that's it, nothing more.
Signature · 1 line
May the most significant bit of your life be positive.
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
Am 25.09.19 um 07:47 schrieb Janne Johansson:
Quoted 11 lines
Den tis 24 sep. 2019 kl 11:00 skrev Ulrich Kalloch <[email protected]>:
Quoted 2 lines
Hello @ all
if you have installed firmware remove it if possible.The install Process check that
/usr/include/machineis empty.Quoted 1 line
then check that the directory
/usr/include/machineis empty.If not clean it.
I think this part is way off and probably all the way into "bad advice".Cleaning
/usr/include/machineis wrong, andfw_updateseems completely unrelated to either the contents of the C includes or building WG.
but without cleaning /usr/include/machine the install Process fails ...
Quoted 4 lines
You didn't have the compiler installed which what was causing your issues with building wg and I think that's it, nothing more.
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch <[email protected]>:
Quoted 11 lines
Quoted 8 lines
Quoted 1 line
if you have installed firmware remove it if possible.
The install Process check that
/usr/include/machineis empty.Quoted 1 line
then check that the directory
/usr/include/machineis empty.If not clean it.
I think this part is way off and probably all the way into "bad advice".Cleaning
/usr/include/machineis wrong, andfw_updateseems completely unrelated to either the contents of the C includes or building WG.but without cleaning
/usr/include/machinethe 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.
Signature · 1 line
May the most significant bit of your life be positive.
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
Am 25.09.19 um 13:01 schrieb Janne Johansson:
Quoted 36 lines
Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch <[email protected]>:
Quoted 10 lines
Quoted 8 lines
Quoted 1 line
if you have installed firmware remove it if possible.
The install Process check that
/usr/include/machineis empty.Quoted 1 line
then check that the directory
/usr/include/machineis empty.If not clean it.
I think this part is way off and probably all the way into "bad advice".Cleaning
/usr/include/machineis wrong, andfw_updateseems completely unrelated to either the contents of the C includes or building WG.but without cleaning
/usr/include/machinethe 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...
Quoted 9 lines
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_updatethere" 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.
yes .. you are right. Thanks for your time to check.
If i have a Server or VM with comp installed all is fine.
but my first setup was without comp installed and the script fails.
maybe you can build in a check for installed comp before?
The Problem is only if comp is not installed.
Thanks and sorry for the communication madness.
Regards
Ulli
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard
I have no control over that script, but I think having a compiler in place when building stuff is such a reasonable pre-requisite so that the script would not have to look for it.
Den ons 25 sep. 2019 kl 16:23 skrev Ulrich Kalloch <[email protected]>:
Quoted 66 lines
Am 25.09.19 um 13:01 schrieb Janne Johansson:
Quoted 7 lines
Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch <[email protected]>:
Quoted 5 lines
Quoted 5 lines
Quoted 1 line
if you have installed firmware remove it if possible.
The install Process check that
/usr/include/machineis empty.Quoted 1 line
then check that the directory
/usr/include/machineis empty.If not clean it.
I think this part is way off and probably all the way into "badadvice".
Quoted 18 lines
Quoted 5 lines
Quoted 3 lines
Cleaning
/usr/include/machineis wrong, andfw_updateseems completely unrelated to either the contents of the C includes or building WG.but without cleaning
/usr/include/machinethe 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"Quoted 8 lines
gmake: Leaving directory '
/usr/src/wireguard/wireguard-go-0.0.20190908'[+] Cleaning up build directory
comptest# ls
/usr/include/machine/
_float.hexec.hlimits.h
rbus_machdep.hQuoted 6 lines
_types.hfenv.hloadfile_machdep.hreg.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_updatethere" and you had no idea which of your actions made it back into ausable
Quoted 6 lines
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.
yes .. you are right. Thanks for your time to check.
If i have a Server or VM with comp installed all is fine.
but my first setup was without comp installed and the script fails.
maybe you can build in a check for installed comp before?
The Problem is only if comp is not installed.
Thanks and sorry for the communication madness.
Regards
Ulli
Signature · 1 line
May the most significant bit of your life be positive.
_______________________________________________
WireGuard mailing list
[email protected]
https://lists.zx2c4.com/mailman/listinfo/wireguard