WireGuard Archive on lore.kernel.org
 help / color / Atom feed
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 13:01:38 +0200
Message-ID: <CAA6-MF8c+yxrzR_boA4zhd0-7X2zxJfk8rt9NiysJ87-qXr3eg@mail.gmail.com> (raw)
In-Reply-To: <97473dc6-22d5-0a13-f0e6-9ce6767f0ff7@noc23.de>

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

  reply index

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-23 13:09 Ulrich Kalloch
2019-09-25  5:47 ` Janne Johansson
2019-09-25  8:51   ` Ulrich Kalloch
2019-09-25 11:01     ` Janne Johansson [this message]
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

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAA6-MF8c+yxrzR_boA4zhd0-7X2zxJfk8rt9NiysJ87-qXr3eg@mail.gmail.com \
    --to=icepic.dz@gmail.com \
    --cc=ulli@noc23.de \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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 zx2c4-wireguard@archiver.kernel.org
	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