Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Manikandan Thiagarajan <tmani@prosimo.io>
To: wireguard@lists.zx2c4.com
Subject: [Windows] Unable to build latest wireguard missing i686-w64-mingw32-windres
Date: Thu, 28 Jan 2021 15:24:02 -0800	[thread overview]
Message-ID: <CAJV1VRDbW+LWhy_zA5VqvdiVc_-S28M5Lv1L30j9JGC5ZcTKfg@mail.gmail.com> (raw)

Hi,

I am trying to update Wireguard to latest version on windows but could
not build because of missing dependencies i686-w64-mingw32-windres.
I can't go back to older commit such as 0.3.4 (a5102ca - version:
bump) because of go mod has reference to unknown revision
76ef01985b1c.
Please suggest how to fix either one of these issues. I can use either
of these commits.

Building off of commit 5f420f6 - manager: pipeline UAPI requests
'i686-w64-mingw32-windres' is not recognized as an internal or external command,
operable program or batch file.
[-] Failed with error #1.

Building off of commit a5102ca - version: bump
[+] Building library x86
get "golang.zx2c4.com/wireguard/windows": found meta tag
get.metaImport{Prefix:"golang.zx2c4.com/wireguard/windows", VCS:"git",
RepoRoot:"https://git.zx2c4.com/wireguard-windows"} at
//golang.zx2c4.com/wireguard/windows?go-get=1
go: golang.zx2c4.com/wireguard/windows@v0.0.0-20201130211600-76ef01985b1c:
invalid version: unknown revision 76ef01985b1c
[-] Failed with error #1.
[+] Rendering icons
[+] Assembling resources x86
[+] Building program x86
get "golang.zx2c4.com/wireguard/windows": found meta tag
get.metaImport{Prefix:"golang.zx2c4.com/wireguard/windows", VCS:"git",
RepoRoot:"https://git.zx2c4.com/wireguard-windows"} at
//golang.zx2c4.com/wireguard/windows?go-get=1
go: golang.zx2c4.com/wireguard/windows@v0.0.0-20201130211600-76ef01985b1c:
invalid version: unknown revision 76ef01985b1c
[-] Failed with error #1

Thanks,
Mani

             reply	other threads:[~2021-01-28 23:24 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-28 23:24 Manikandan Thiagarajan [this message]
2021-02-01 14:08 Vladyslav Ivasyuk

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=CAJV1VRDbW+LWhy_zA5VqvdiVc_-S28M5Lv1L30j9JGC5ZcTKfg@mail.gmail.com \
    --to=tmani@prosimo.io \
    --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).