Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: Jonathon Fernyhough <jonathon.fernyhough@york.ac.uk>,
	wireguard@lists.zx2c4.com
Subject: Re: wireguard-tools Ubuntu package missing the binaries
Date: Sun, 16 Apr 2017 17:47:16 +0200	[thread overview]
Message-ID: <1492357636.1445.6.camel@eggiecode.org> (raw)
In-Reply-To: <b58aaa20-6b03-5501-3cad-f791cfd2319a@york.ac.uk>

Hey Jonathon and Ryan,

This problem got previously with my RaspPi. That tools binaries build
are not in de build of armv6 and think that is the same with i386.

This was a old item in the mailing list about arm packages in ubuntu
repo: https://lists.zx2c4.com/pipermail/wireguard/2017-February/001050.
html
Coud not figer out what the problem was.

And a great time to add ubuntu 17.04 (zesty) and test it on my pi.

hda (cryptofuture) is testing it now on his own ppa, see here the
github issue: https://github.com/EggieCode/wireguard-ppa/issues/13 and
the fix https://github.com/EggieCode/wireguard-ppa/pull/14

Greetz,
Egbert

On Sun, 2017-04-16 at 12:24 +0100, Jonathon Fernyhough wrote:
> On 16/04/17 12:06, Ryan Riley wrote:
> > The i386 wireguard-tools package on the PPA for Ubuntu Xenial
> > doesn't
> > actually contain any of the binaries, just documentation.
> 
> It's not just i386 - each of the arm and ppc64 packages are also
> missing
> binaries.
> 
> Debian's packages (and my testing backports based on those) don't
> have
> that issue - might be time to check a diff or do a merge. :)
> 
> Looks like it's down to `make install`ing the tools during install-
> indep
> rather than install-arch.
> 
> 
> Working (Debian use a different flags setup, that's not the important
> bit):
> 
> > override_dh_auto_install-indep:
> > 	$(MAKE) -C src DESTDIR=../debian/wireguard-dkms
> > DKMSDIR=/usr/src/wireguard-$(DEB_VERSION)/ dkms-install
> > 
> > override_dh_auto_build-arch:
> > 	$(MAKE) -C src/tools $(WIREGUARD_ARGS)
> > 
> > override_dh_auto_install-arch:
> > 	$(MAKE) -C src/tools DESTDIR=../../debian/wireguard-tools
> > $(WIREGUARD_ARGS) install
> 
> 
> Non-working:
> 
> > override_dh_auto_install-indep:
> > 	$(MAKE) -C wireguard-src/src
> > DESTDIR=$(CURDIR)/debian/wireguard-dkms DKMSDIR=/usr/src/wireguard-
> > $(DEB_VERSION_UPSTREAM)/ dkms-install
> > 	$(MAKE) -C wireguard-src/src/tools
> > DESTDIR=$(CURDIR)/debian/wireguard-tools WITH_SYSTEMDUNITS=yes
> > WITH_WGQUICK=yes WITH_BASHCOMPLETION=yes install
> > 
> > override_dh_auto_build-arch:
> >  	$(MAKE) -C wireguard-src/src/tools
> 
> 
> 
> J
> 
> _______________________________________________
> WireGuard mailing list
> WireGuard@lists.zx2c4.com
> https://lists.zx2c4.com/mailman/listinfo/wireguard

  reply	other threads:[~2017-04-16 15:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-16 11:06 Ryan Riley
2017-04-16 11:24 ` Jonathon Fernyhough
2017-04-16 15:47   ` Egbert Verhage [this message]
2017-04-16 15:50     ` Jason A. Donenfeld
2017-04-16 16:04       ` Egbert Verhage
2017-04-16 17:50   ` wireguard-tools Ubuntu package missing the binaries; Fixed Egbert Verhage
2017-04-17  6:19     ` Ryan Riley

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=1492357636.1445.6.camel@eggiecode.org \
    --to=egbert@eggiecode.org \
    --cc=jonathon.fernyhough@york.ac.uk \
    --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).