Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Jaron Kent-Dobias <jaron-wg@kent-dobias.com>
To: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: DKMS build problem on Pinephone with UBports (xenial)
Date: Sat, 22 Feb 2020 14:58:59 -0500	[thread overview]
Message-ID: <0fbfcb28-47c3-5aa0-1699-e3bcd7ca7f6d@kent-dobias.com> (raw)

Hello,

Installing the wireguard-dkms package (0.0.20200215-0ppa1~16.04) on a
Pinephone running UBports (xenial with custom repositories) results in a
DKMS build error. The shell output and make.log are below. Seems like a
syntax error in a build script, not sure if this belongs here or downstream.

Jaron

> phablet@ubuntu-phablet ~ % sudo apt install wireguard-dkms
> Reading package lists... Done
> Building dependency tree       
> Reading state information... Done
> Recommended packages:
>   wireguard
> The following NEW packages will be installed:
>   wireguard-dkms
> 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
> Need to get 259 kB of archives.
> After this operation, 1,765 kB of additional disk space will be used.
> Get:1 http://ppa.launchpad.net/wireguard/wireguard/ubuntu xenial/main arm64 wireguard-dkms all 0.0.20200215-0ppa1~16.04 [259 kB] 
> Fetched 259 kB in 0s (279 kB/s)         
> Selecting previously unselected package wireguard-dkms.
> (Reading database ... 83056 files and directories currently installed.)
> Preparing to unpack .../wireguard-dkms_0.0.20200215-0ppa1~16.04_all.deb ...
> Unpacking wireguard-dkms (0.0.20200215-0ppa1~16.04) ...
> Setting up wireguard-dkms (0.0.20200215-0ppa1~16.04) ...
> Loading new wireguard-0.0.20200215 DKMS files...
> First Installation: checking all kernels...
> Building only for 5.4.0-pine64
> Building initial module for 5.4.0-pine64
> Error! Bad return status for module build on kernel: 5.4.0-pine64 (aarch64)
> Consult /var/lib/dkms/wireguard/0.0.20200215/build/make.log for more information.
> W: No sandbox user '_apt' on the system, can not drop privileges
>   11.03s user 4.14s system 83% cpu 18.115 total

> DKMS make.log for wireguard-0.0.20200215 for kernel 5.4.0-pine64 (aarch64)
> Sat Feb 22 19:47:26 UTC 2020
> make: Entering directory '/usr/src/linux-headers-5.4.0-pine64'
>   AR      /var/lib/dkms/wireguard/0.0.20200215/build/built-in.a
>   CC [M]  /var/lib/dkms/wireguard/0.0.20200215/build/main.o
> scripts/basic/fixdep: 1: scripts/basic/fixdep: Syntax error: ")" unexpected
> scripts/Makefile.build:265: recipe for target '/var/lib/dkms/wireguard/0.0.20200215/build/main.o' failed
> make[1]: *** [/var/lib/dkms/wireguard/0.0.20200215/build/main.o] Error 2
> make[1]: *** Deleting file '/var/lib/dkms/wireguard/0.0.20200215/build/main.o'
> Makefile:1652: recipe for target '/var/lib/dkms/wireguard/0.0.20200215/build' failed
> make: *** [/var/lib/dkms/wireguard/0.0.20200215/build] Error 2
> make: Leaving directory '/usr/src/linux-headers-5.4.0-pine64'
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard

             reply	other threads:[~2020-02-22 19:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-22 19:58 Jaron Kent-Dobias [this message]
2020-02-23 15:46 ` Jason A. Donenfeld

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=0fbfcb28-47c3-5aa0-1699-e3bcd7ca7f6d@kent-dobias.com \
    --to=jaron-wg@kent-dobias.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).