From: Ulrich Kalloch <ulli@noc23.de>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: Build fail on OpenBSD 6.5 amd64
Date: Wed, 25 Sep 2019 10:51:41 +0200 [thread overview]
Message-ID: <97473dc6-22d5-0a13-f0e6-9ce6767f0ff7@noc23.de> (raw)
In-Reply-To: <CAA6-MF-nK3Jm6jzdXuhk62cqfD4XACtG1md3jvUBCix3fcnuFw@mail.gmail.com>
[-- 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
next prev parent reply other threads:[~2019-09-25 8:52 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
Reply instructions:
You may reply publicly 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=97473dc6-22d5-0a13-f0e6-9ce6767f0ff7@noc23.de \
--to=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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).