Re: Build fail on OpenBSD 6.5 amd64

From: Janne Johansson <icepic.dz@gmail.com>
To: Ulrich Kalloch <ulli@noc23.de>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Build fail on OpenBSD 6.5 amd64
Date: Wed, 25 Sep 2019 20:26:57 +0200	[thread overview]
Message-ID: <CAA6-MF9pHX4vvKSu+dLmSSx+K6hiaUpNCwkstuRsZfe3Nm=EBQ@mail.gmail.com> (raw)
In-Reply-To: <0a591f71-8387-a9fa-1097-ff654445bdae@noc23.de>

[-- Attachment #1.1: Type: text/plain, Size: 2450 bytes --]

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 <ulli@noc23.de>:

> Am 25.09.19 um 13:01 schrieb Janne Johansson:
> > Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch <ulli@noc23.de>:
> >
> >>>> 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.
> >
> 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
>
>

-- 
May the most significant bit of your life be positive.

[-- Attachment #1.2: Type: text/html, Size: 3620 bytes --]

[-- Attachment #2: Type: text/plain, Size: 148 bytes --]

_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard