WireGuard Archive on lore.kernel.org
 help / color / Atom feed
* Build fail on OpenBSD 6.5 amd64
@ 2019-09-23 13:09 Ulrich Kalloch
  2019-09-25  5:47 ` Janne Johansson
  0 siblings, 1 reply; 7+ messages in thread
From: Ulrich Kalloch @ 2019-09-23 13:09 UTC (permalink / raw)
  To: WireGuard mailing list

[-- Attachment #1.1.1.1: Type: text/plain, Size: 495 bytes --]

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


[-- Attachment #1.1.1.2: 0x44BE4EB74E7625C8.asc --]
[-- Type: application/pgp-keys, Size: 3987 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Build fail on OpenBSD 6.5 amd64
  2019-09-23 13:09 Build fail on OpenBSD 6.5 amd64 Ulrich Kalloch
@ 2019-09-25  5:47 ` Janne Johansson
  2019-09-25  8:51   ` Ulrich Kalloch
  0 siblings, 1 reply; 7+ messages in thread
From: Janne Johansson @ 2019-09-25  5:47 UTC (permalink / raw)
  To: Ulrich Kalloch; +Cc: WireGuard mailing list

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

Den tis 24 sep. 2019 kl 11:00 skrev Ulrich Kalloch <ulli@noc23.de>:

> Hello @ all
> 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.

You didn't have the compiler installed which what was causing your issues
with building wg and I think that's it, nothing more.

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

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

<div dir="ltr"><div dir="ltr">Den tis 24 sep. 2019 kl 11:00 skrev Ulrich Kalloch &lt;<a href="mailto:ulli@noc23.de">ulli@noc23.de</a>&gt;:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello @ all<br>if you have installed firmware remove it if possible.</blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
The install Process check that /usr/include/machine is empty.<br>then check that the directory /usr/include/machine is empty. </blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">If not clean it.<br></blockquote><div><br></div><div>I think this part is way off and probably all the way into &quot;bad advice&quot;.</div><div><br></div><div>Cleaning /usr/include/machine is wrong, and fw_update seems completely</div><div>unrelated to either the contents of the C includes or building WG.</div><div><br></div><div>You didn&#39;t have the compiler installed which what was causing your issues</div><div>with building wg and I think that&#39;s it, nothing more.</div></div><div><br></div>-- <br><div dir="ltr" class="gmail_signature">May the most significant bit of your life be positive.<br></div></div>

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Build fail on OpenBSD 6.5 amd64
  2019-09-25  5:47 ` Janne Johansson
@ 2019-09-25  8:51   ` Ulrich Kalloch
  2019-09-25 11:01     ` Janne Johansson
  0 siblings, 1 reply; 7+ messages in thread
From: Ulrich Kalloch @ 2019-09-25  8:51 UTC (permalink / raw)
  To: WireGuard mailing list

[-- Attachment #1.1.1.1: Type: text/plain, Size: 789 bytes --]

Am 25.09.19 um 07:47 schrieb Janne Johansson:
> Den tis 24 sep. 2019 kl 11:00 skrev Ulrich Kalloch <ulli@noc23.de>:
>
>> Hello @ all
>> 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 ... 

>
> You didn't have the compiler installed which what was causing your issues
> with building wg and I think that's it, nothing more.
>


[-- Attachment #1.1.1.2: 0x44BE4EB74E7625C8.asc --]
[-- Type: application/pgp-keys, Size: 3987 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Build fail on OpenBSD 6.5 amd64
  2019-09-25  8:51   ` Ulrich Kalloch
@ 2019-09-25 11:01     ` Janne Johansson
  2019-09-25 14:23       ` Ulrich Kalloch
  0 siblings, 1 reply; 7+ messages in thread
From: Janne Johansson @ 2019-09-25 11:01 UTC (permalink / raw)
  To: Ulrich Kalloch; +Cc: WireGuard mailing list

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

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.

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

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

<div dir="ltr"><div dir="ltr">Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch &lt;<a href="mailto:ulli@noc23.de">ulli@noc23.de</a>&gt;:<br></div><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">&gt;&gt; if you have installed firmware remove it if possible.<br>
&gt; The install Process check that /usr/include/machine is empty.<br>
&gt;&gt; then check that the directory /usr/include/machine is empty.<br>
&gt; If not clean it.<br>
&gt; I think this part is way off and probably all the way into &quot;bad advice&quot;.<br>
&gt;<br>
&gt; Cleaning /usr/include/machine is wrong, and fw_update seems completely<br>
&gt; unrelated to either the contents of the C includes or building WG.<br>
<br>
but without cleaning /usr/include/machine the install Process fails ... <br></blockquote><div><br></div><div>I made an amd64 VM to test and it went fine:</div>





<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">...</span></p><p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures"><a href="http://golang.zx2c4.com/wireguard/tun">golang.zx2c4.com/wireguard/tun</a></span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures"><a href="http://golang.zx2c4.com/wireguard/device">golang.zx2c4.com/wireguard/device</a></span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures"><a href="http://golang.zx2c4.com/wireguard">golang.zx2c4.com/wireguard</a></span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">install -d &quot;/usr/local/bin&quot; &amp;&amp; install -m 0755 &quot;wireguard-go&quot; &quot;/usr/local/bin/wireguard-go&quot;</span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">gmake: Leaving directory &#39;/usr/src/wireguard/wireguard-go-0.0.20190908&#39;</span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">[+] Cleaning up build directory</span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">comptest# ls /usr/include/machine/<span class="gmail-Apple-converted-space">                                             </span></span></p>
<p class="gmail-p1" style="margin:0px;font-variant-numeric:normal;font-variant-east-asian:normal;font-stretch:normal;font-size:11px;line-height:normal;font-family:Menlo;color:rgb(0,0,0)"><span class="gmail-s1" style="font-variant-ligatures:no-common-ligatures">_float.h<span class="gmail-Apple-converted-space">            </span>exec.h<span class="gmail-Apple-converted-space">              </span>limits.h<span class="gmail-Apple-converted-space">            </span>rbus_machdep.h</span></p>
<div><span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">_types.h</span><span class="gmail-Apple-converted-space" style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">            </span><span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">fenv.h</span><span class="gmail-Apple-converted-space" style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">              </span><span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">loadfile_machdep.h</span><span class="gmail-Apple-converted-space" style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">  </span><span style="font-variant-ligatures:no-common-ligatures;color:rgb(0,0,0);font-family:Menlo;font-size:11px">reg.h</span></div><div>...</div><div> </div></div><div>I think your comp-less box was messed up in more ways than you know, probably because of the random &quot;lets poke here, rerun unrelated fw_update there&quot; 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.</div><div><br></div><div>If there is an error it needs to get fixed for real and not with hand-wavingly delete include files needed for other things.</div><div>  </div>-- <br><div dir="ltr" class="gmail_signature">May the most significant bit of your life be positive.<br></div></div>

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Build fail on OpenBSD 6.5 amd64
  2019-09-25 11:01     ` Janne Johansson
@ 2019-09-25 14:23       ` Ulrich Kalloch
  2019-09-25 18:26         ` Janne Johansson
  0 siblings, 1 reply; 7+ messages in thread
From: Ulrich Kalloch @ 2019-09-25 14:23 UTC (permalink / raw)
  To: Janne Johansson; +Cc: WireGuard mailing list

[-- Attachment #1.1.1.1: Type: text/plain, Size: 2088 bytes --]

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


[-- Attachment #1.1.1.2: 0x44BE4EB74E7625C8.asc --]
[-- Type: application/pgp-keys, Size: 3987 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Re: Build fail on OpenBSD 6.5 amd64
  2019-09-25 14:23       ` Ulrich Kalloch
@ 2019-09-25 18:26         ` Janne Johansson
  0 siblings, 0 replies; 7+ messages in thread
From: Janne Johansson @ 2019-09-25 18:26 UTC (permalink / raw)
  To: Ulrich Kalloch; +Cc: WireGuard mailing list

[-- 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 --]

<div dir="ltr">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.<div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Den ons 25 sep. 2019 kl 16:23 skrev Ulrich Kalloch &lt;<a href="mailto:ulli@noc23.de">ulli@noc23.de</a>&gt;:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Am 25.09.19 um 13:01 schrieb Janne Johansson:<br>
&gt; Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch &lt;<a href="mailto:ulli@noc23.de" target="_blank">ulli@noc23.de</a>&gt;:<br>
&gt;<br>
&gt;&gt;&gt;&gt; if you have installed firmware remove it if possible.<br>
&gt;&gt;&gt; The install Process check that /usr/include/machine is empty.<br>
&gt;&gt;&gt;&gt; then check that the directory /usr/include/machine is empty.<br>
&gt;&gt;&gt; If not clean it.<br>
&gt;&gt;&gt; I think this part is way off and probably all the way into &quot;bad advice&quot;.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; Cleaning /usr/include/machine is wrong, and fw_update seems completely<br>
&gt;&gt;&gt; unrelated to either the contents of the C includes or building WG.<br>
&gt;&gt; but without cleaning /usr/include/machine the install Process fails ...<br>
&gt;&gt;<br>
&gt; I made an amd64 VM to test and it went fine:<br>
&gt;<br>
&gt; ...<br>
&gt;<br>
&gt; <a href="http://golang.zx2c4.com/wireguard/tun" rel="noreferrer" target="_blank">golang.zx2c4.com/wireguard/tun</a><br>
&gt;<br>
&gt; <a href="http://golang.zx2c4.com/wireguard/device" rel="noreferrer" target="_blank">golang.zx2c4.com/wireguard/device</a><br>
&gt;<br>
&gt; <a href="http://golang.zx2c4.com/wireguard" rel="noreferrer" target="_blank">golang.zx2c4.com/wireguard</a><br>
&gt;<br>
&gt; install -d &quot;/usr/local/bin&quot; &amp;&amp; install -m 0755 &quot;wireguard-go&quot;<br>
&gt; &quot;/usr/local/bin/wireguard-go&quot;<br>
&gt;<br>
&gt; gmake: Leaving directory &#39;/usr/src/wireguard/wireguard-go-0.0.20190908&#39;<br>
&gt;<br>
&gt; [+] Cleaning up build directory<br>
&gt;<br>
&gt; comptest# ls /usr/include/machine/<br>
&gt;<br>
&gt;<br>
&gt; _float.h            exec.h              limits.h            rbus_machdep.h<br>
&gt; _types.h            fenv.h              loadfile_machdep.h  reg.h<br>
&gt; ...<br>
&gt;<br>
&gt; I think your comp-less box was messed up in more ways than you know,<br>
&gt; probably because of the random &quot;lets poke here, rerun unrelated fw_update<br>
&gt; there&quot; and you had no idea which of your actions made it back into a usable<br>
&gt; shape again. Redo your test from scratch (without skipping the compiler<br>
&gt; set) and post the output on a pastebin.<br>
&gt;<br>
&gt; If there is an error it needs to get fixed for real and not with<br>
&gt; hand-wavingly delete include files needed for other things.<br>
&gt;<br>
yes .. you are right. Thanks for your time to check.<br>
<br>
If i have a Server or VM with comp installed all is fine.<br>
<br>
but my first setup was without comp installed and the script fails.<br>
<br>
maybe you can build in a check for installed comp before?<br>
<br>
The Problem is only if comp is not installed.<br>
<br>
Thanks and sorry for the communication madness.<br>
<br>
Regards<br>
<br>
Ulli<br>
<br>
</blockquote></div><br clear="all"><div><br></div>-- <br><div dir="ltr" class="gmail_signature">May the most significant bit of your life be positive.<br></div>

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

* Build fail on OpenBSD 6.5 amd64
@ 2019-09-23 12:18 Ulrich Kalloch
  0 siblings, 0 replies; 7+ messages in thread
From: Ulrich Kalloch @ 2019-09-23 12:18 UTC (permalink / raw)
  To: WireGuard mailing list

[-- Attachment #1.1.1.1: Type: text/plain, Size: 6507 bytes --]

Hello @ all

the build script -> https://xn--4db.cc/IKuBc62Z fails on OpenBSD 6.5

The Output :


foo# ./install.sh    
[+] Preparing build directory in /usr/src/wireguard
[+] Installing dependencies
quirks-3.124 signed on 2019-09-22T21:00:10Z
[+] Fetching latest versions
Trying 147.75.105.169...
Requesting https://build.wireguard.com/distros.txt
1978 bytes received in 0.00 seconds (12.69 MB/s)
[+] Fetching and unpacking archives
Trying 147.75.77.251...
Requesting
https://git.zx2c4.com/WireGuard/snapshot/WireGuard-0.0.20190913.tar.xz
330788 bytes received in 1.55 seconds (208.92 KB/s)
Trying 147.75.77.251...
Requesting
https://git.zx2c4.com/wireguard-go/snapshot/wireguard-go-0.0.20190908.tar.xz
79212 bytes received in 0.51 seconds (150.46 KB/s)
[+] Building wg(8) and wg-quick(8) tools
gmake: Entering directory
'/usr/src/wireguard/WireGuard-0.0.20190913/src/tools'
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/wg.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/set.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/mnlg.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/pubkey.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/showconf.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/genkey.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/setconf.o
  CC      /usr/src/wireguard/WireGuard-0.0.20190913/src/tools/curve25519.o
wg.c:6:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
         ^~~~~~~~~~
set.c:6:10: fatal error: 'stdio.h' file not found
#include <stdio.h>
         ^~~~~~~~~
1 error generated.
1 error generated.
showconf.c:6:10: fatal error: 'arpa/inet.h' file not found
#include <arpa/inet.h>
         ^~~~~~~~~~~~~
genkey.c:6:10: fatal error: 'errno.h' file not found
#include <errno.h>
         ^~~~~~~~~
pubkey.c:6:10: fatal error: 'errno.h' file not found
#include <errno.h>
         ^~~~~~~~~
1 error generated.
1 error generated.
setconf.c:6:10: fatal error: 'stddef.h' file not found
#include <stddef.h>
         ^~~~~~~~~~
1 error generated.
In file included from curve25519.c:6:
./curve25519.h:9:10: fatal error: 'stdint.h' file not found
1 error#include <stdint.h> generated
.
         ^~~~~~~~~~
1 error generated.
gmake: *** [<builtin>: set.o] Error 1
gmake: *** Waiting for unfinished jobs....
gmake: *** [<builtin>: wg.o] Error 1
gmake: *** [<builtin>: pubkey.o] Error 1
gmake: *** [<builtin>: curve25519.o] Error 1
gmake: *** [<builtin>: setconf.o] Error 1
gmake: *** [<builtin>: genkey.o] Error 1
gmake: *** [<builtin>: showconf.o] Error 1
gmake: Leaving directory
'/usr/src/wireguard/WireGuard-0.0.20190913/src/tools'
[+] Cleaning up build directory
foo#


The System is a Plain OpenBSD with this Packages.total 212
drwxr-xr-x  53 root  wheel  1536 Sep 23 14:05 .
drwxr-xr-x   7 root  wheel   512 Sep 23 11:49 ..
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 acx-firmware-1.4p5
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 amdgpu-firmware-20181218
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 athn-firmware-1.1p4
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 bash-5.0.3
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 bwfm-firmware-20171125
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 bwi-firmware-1.4p4
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 bzip2-1.0.6p10
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 curl-7.64.1p1
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 cvsps-2.1p2
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 desktop-file-utils-0.23p10
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 gettext-0.19.8.1p3
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 git-2.21.0
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 glib2-2.58.3p9
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 gmake-4.2.1p0
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 go-1.12.1
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 htop-2.2.0p8
drwxr-xr-x   2 root  wheel   512 Sep 23 11:41 intel-firmware-20190514p0v0
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 inteldrm-firmware-20181218
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 ipw-firmware-1.3p2
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 iwi-firmware-3.1p2
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 iwm-firmware-0.20170105
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 iwn-firmware-5.11p1
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 libffi-3.2.1p5
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 libiconv-1.14p3
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 libidn2-2.0.0p0
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 libpsl-0.20.2
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 libunistring-0.9.7
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 malo-firmware-1.4p4
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 nano-4.0
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 nghttp2-1.37.0
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 nload-0.7.4p4
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 otus-firmware-1.0p1
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 p5-Error-0.17025
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 pcre-8.41p2
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 pcre2-10.32
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 pgt-firmware-1.2p4
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 python-3.6.8p0
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 quirks-3.124
drwxr-xr-x   2 root  wheel   512 Sep 23 11:41 radeondrm-firmware-20181218
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 rsu-firmware-1.2p1
drwxr-xr-x   2 root  wheel   512 Sep 23 14:05 rsync-3.1.3
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 rtwn-firmware-20180103
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 sqlite3-3.27.2p0
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 uath-firmware-2.0p1
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 upgt-firmware-1.1p4
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 urtwn-firmware-20180103
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 uvideo-firmware-1.2p2
drwxr-xr-x   2 root  wheel   512 Sep 23 11:41 vmm-firmware-1.11.0p1
drwxr-xr-x   2 root  wheel   512 Sep 23 14:03 wget-1.20.3
drwxr-xr-x   2 root  wheel   512 Sep 23 12:05 wpi-firmware-3.2p1
drwxr-xr-x   2 root  wheel   512 Sep 23 11:51 xz-5.2.4

Regards

Ulli


[-- Attachment #1.1.1.2: 0x44BE4EB74E7625C8.asc --]
[-- Type: application/pgp-keys, Size: 3987 bytes --]

[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

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

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

^ permalink raw reply	[flat|nested] 7+ messages in thread

end of thread, back to index

Thread overview: 7+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-09-23 13:09 Build fail on OpenBSD 6.5 amd64 Ulrich Kalloch
2019-09-25  5:47 ` Janne Johansson
2019-09-25  8:51   ` Ulrich Kalloch
2019-09-25 11:01     ` Janne Johansson
2019-09-25 14:23       ` Ulrich Kalloch
2019-09-25 18:26         ` Janne Johansson
  -- strict thread matches above, loose matches on Subject: below --
2019-09-23 12:18 Ulrich Kalloch

WireGuard Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/wireguard/0 wireguard/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 wireguard wireguard/ https://lore.kernel.org/wireguard \
		wireguard@lists.zx2c4.com
	public-inbox-index wireguard

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/com.zx2c4.lists.wireguard


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git