From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Outback Dingo <outbackdingo@gmail.com>, wireguard@lists.zx2c4.com
Subject: Re: wg on arm 32-bit
Date: Sat, 30 Dec 2017 19:29:45 -0500 [thread overview]
Message-ID: <87incnhh8m.fsf@fifthhorseman.net> (raw)
In-Reply-To: <CAKYr3zwZC7QMyLZJT55MquxSOuJsvBO3JrNntFEp23egqJAeKw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 496 bytes --]
On Wed 2017-12-27 12:57:47 -0500, Outback Dingo wrote:
> seems that wireguard is not capabl;e of building for 32bit arm?
here's a list of successful 32-bit little-endian arm builds for debian:
https://buildd.debian.org/status/logs.php?pkg=wireguard&arch=armel&suite=sid
if you click on the "Maybe-Successful" links, you can see logs of each
build.
So there's something else weird about your build environment that's the
issue here, not the fact that it's 32-bit arm.
Regards,
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]
prev parent reply other threads:[~2017-12-31 0:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-27 17:57 Outback Dingo
2017-12-27 22:24 ` Peter Korsgaard
2017-12-28 14:25 ` Outback Dingo
2017-12-30 15:12 ` Jason A. Donenfeld
2017-12-31 0:29 ` Daniel Kahn Gillmor [this message]
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=87incnhh8m.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=outbackdingo@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
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).