WireGuard Archive on lore.kernel.org
 help / color / Atom feed
From: Ulrich Kalloch <ulli@noc23.de>
To: Janne Johansson <icepic.dz@gmail.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Build fail on OpenBSD 6.5 amd64
Date: Wed, 25 Sep 2019 16:23:45 +0200
Message-ID: <0a591f71-8387-a9fa-1097-ff654445bdae@noc23.de> (raw)
In-Reply-To: <CAA6-MF8c+yxrzR_boA4zhd0-7X2zxJfk8rt9NiysJ87-qXr3eg@mail.gmail.com>

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

  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
2019-09-25 14:23       ` Ulrich Kalloch [this message]
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=0a591f71-8387-a9fa-1097-ff654445bdae@noc23.de \
    --to=ulli@noc23.de \
    --cc=icepic.dz@gmail.com \
    --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
	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