From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-0.5 required=3.0 tests=DKIM_ADSP_CUSTOM_MED, DKIM_INVALID,DKIM_SIGNED,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,HTML_MESSAGE,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4C31BC432C2 for ; Wed, 25 Sep 2019 18:27:13 +0000 (UTC) Received: from krantz.zx2c4.com (krantz.zx2c4.com [192.95.5.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id A6BAE21655 for ; Wed, 25 Sep 2019 18:27:12 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="vS20TquT" DMARC-Filter: OpenDMARC Filter v1.3.2 mail.kernel.org A6BAE21655 Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=wireguard-bounces@lists.zx2c4.com Received: from krantz.zx2c4.com (localhost [IPv6:::1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id e91292d7; Wed, 25 Sep 2019 18:27:11 +0000 (UTC) Received: from krantz.zx2c4.com (localhost [127.0.0.1]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id 25c499ab for ; Wed, 25 Sep 2019 18:27:09 +0000 (UTC) Received: from mail-io1-xd2e.google.com (mail-io1-xd2e.google.com [IPv6:2607:f8b0:4864:20::d2e]) by krantz.zx2c4.com (ZX2C4 Mail Server) with ESMTP id c6b7f387 for ; Wed, 25 Sep 2019 18:27:09 +0000 (UTC) Received: by mail-io1-xd2e.google.com with SMTP id u8so1337566iom.5 for ; Wed, 25 Sep 2019 11:27:09 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ygkpQETyUfroj7qj4sdduKRw1FfVxm25FAoj9Nc0eIE=; b=vS20TquTNE9J+EVR53qrqdzQ7G6Q605mkY3Lkhv2kS1zWCAwi+FdZeJ2wihcQExVSJ vMtUOVa8llPS9Fh7D+yLSjzhzZHTBLpaGML9XwB4LyKCtSWz3H3tB7BcgktVJr+uHL4f lO8rro/GN7hjTyMU7C2OyqU0wmXy5DbIhhSOLd/0Na4aOncxEOtTjpXVmxKy+zAWXzSo LqK/jZHccm4k/M4MYmWTRhRcsV5mbHVFyt7Szy1BTuNxZMgBCW7rFVQ9omrXYke4JblY Uwxu+ydJP6yf6zPm1ycPS0tXhs1ez1oWwcV+HVbSKTWcYPyS+MfHK5yeuY88uhiBhFT9 UaYA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ygkpQETyUfroj7qj4sdduKRw1FfVxm25FAoj9Nc0eIE=; b=i2C7Jtij9Lp7t+gVMwg9wAYR87CPkREergwnscO/N6NGX5iiEGuVEv0wv+/ZwE3ZFW 1NNi+6y4a7mui9p9umt815h4w7H91AC0b1pa/f03fdjfZTt8ka+UQXvDCqA76tyskJk2 RjjLMlY1mkuxftNLehFVcxxE0b3gWdzslcCflCKPjEvq749El5od6mWNecLh06kV8jXy 7fdD1e+N5Qg6p8rT1rpTksKgUhKWTsvF3HKEWslCii92mG41ptwprEjkoMKBB+C5aB40 z4YCV6bhCKNCvvU0fyah0X1nnE4SgUgkUVgyJ5V0l34qQ6ntMHjh9QNkHms16kUt5LYz aB5A== X-Gm-Message-State: APjAAAWPeapkVCs4sQxKibjHXM+QBm8427xRKUMVgqpuSkyPHEzzKwmr si8evDmmcXmNJrqXvNBq2KLKa+zcS4dmoeuOOpw70BKV3Jo= X-Google-Smtp-Source: APXvYqwPK/goG+VP03TnWgP2gWiqaFn8obkPyPGfWOwuY0liKztS8C5Z3bNZpOctbo2QoVjfxselNeOrJI1ZoLPYtVI= X-Received: by 2002:a92:3854:: with SMTP id f81mr1456497ila.31.1569436028592; Wed, 25 Sep 2019 11:27:08 -0700 (PDT) MIME-Version: 1.0 References: <573fbdd7-cc13-ee2a-e9a7-eaf095471e3a@noc23.de> <97473dc6-22d5-0a13-f0e6-9ce6767f0ff7@noc23.de> <0a591f71-8387-a9fa-1097-ff654445bdae@noc23.de> In-Reply-To: <0a591f71-8387-a9fa-1097-ff654445bdae@noc23.de> From: Janne Johansson Date: Wed, 25 Sep 2019 20:26:57 +0200 Message-ID: Subject: Re: Build fail on OpenBSD 6.5 amd64 To: Ulrich Kalloch Cc: WireGuard mailing list X-BeenThere: wireguard@lists.zx2c4.com X-Mailman-Version: 2.1.15 Precedence: list List-Id: Development discussion of WireGuard List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============2580572361268962612==" Errors-To: wireguard-bounces@lists.zx2c4.com Sender: "WireGuard" --===============2580572361268962612== Content-Type: multipart/alternative; boundary="000000000000fb6801059364cc07" --000000000000fb6801059364cc07 Content-Type: text/plain; charset="UTF-8" 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 : > Am 25.09.19 um 13:01 schrieb Janne Johansson: > > Den ons 25 sep. 2019 kl 10:52 skrev Ulrich Kalloch : > > > >>>> 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. --000000000000fb6801059364cc07 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
I have no control over that script, but I think having a c= ompiler 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 <u= lli@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.<= br> >>>> then check that the directory /usr/include/machine is empt= y.
>>> If not clean it.
>>> I think this part is way off and probably all the way into &qu= ot;bad advice".
>>>
>>> Cleaning /usr/include/machine is wrong, and fw_update seems co= mpletely
>>> unrelated to either the contents of the C includes or building= WG.
>> but without cleaning /usr/include/machine the install Process fail= s ...
>>
> 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.2019= 0908'
>
> [+] Cleaning up build directory
>
> comptest# ls /usr/include/machine/
>
>
> _float.h=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 exec.h=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 limits.h=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2= =A0 =C2=A0 rbus_machdep.h
> _types.h=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 fenv.h=C2=A0 =C2=A0 = =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 loadfile_machdep.h=C2=A0 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 f= w_update
> there" and you had no idea which of your actions made it back int= o a usable
> shape again. Redo your test from scratch (without skipping the compile= r
> 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 pos= itive.
--000000000000fb6801059364cc07-- --===============2580572361268962612== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ WireGuard mailing list WireGuard@lists.zx2c4.com https://lists.zx2c4.com/mailman/listinfo/wireguard --===============2580572361268962612==--