From: Florian Anderiasch <ml+wireguard@anderiasch.de>
To: wireguard@lists.zx2c4.com
Subject: BUG: Ubuntu package doesn't return proper error code on failure
Date: Thu, 21 Feb 2019 09:25:40 +0100 [thread overview]
Message-ID: <aa99b980f14d5b0cb004e0e1b5c4ab1a@anderiasch.de> (raw)
Hi,
please excuse if this is the wrong medium to report this error, but I
couldn't manage to file a bug on Launchpad.
Ubuntu 18.04
4.15.0-45-generic
wireguard-dkms 0.0.20190123-wg1~bionic
wireguard-dkms failed to install properly because the kernel module
could not be compiled (my bad, has nothing to do with this bug report),
but the installation exited with exit code 0 and so I didn't realize at
first because everything scrolled past. IMHO this should be a non-zero
exit code because wireguard was obviously not working because I couldn't
modprobe the kernel module.
apt-get install --reinstall wireguard-dkms
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not
upgraded.
Need to get 551 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://ppa.launchpad.net/wireguard/wireguard/ubuntu bionic/main
amd64 wireguard-dkms all 0.0.20190123-wg1~bionic [551 kB]
Fetched 551 kB in 0s (1.589 kB/s)
(Reading database ... 278642 files and directories currently
installed.)
Preparing to unpack .../wireguard-dkms_0.0.20190123-wg1~bionic_all.deb
...
------------------------------
Deleting module version: 0.0.20190123
completely from the DKMS tree.
------------------------------
Done.
Unpacking wireguard-dkms (0.0.20190123-wg1~bionic) over
(0.0.20190123-wg1~bionic) ...
Setting up wireguard-dkms (0.0.20190123-wg1~bionic) ...
Loading new wireguard-0.0.20190123 DKMS files...
Building for 4.15.0-45-generic
Building initial module for 4.15.0-45-generic
Error! Bad return status for module build on kernel: 4.15.0-45-generic
(x86_64)
Consult /var/lib/dkms/wireguard/0.0.20190123/build/make.log for more
information.
The real cause of the error was me using the LLVM linker lld as
/usr/bin/lld - which unsurprisingly doesn't build kernel modules, not
that it matters for this.
Everything is working now flawlessly, thanks for your efforts :)
Cheers,
Florian
_______________________________________________
WireGuard mailing list
WireGuard@lists.zx2c4.com
https://lists.zx2c4.com/mailman/listinfo/wireguard
next reply other threads:[~2019-03-01 10:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-21 8:25 Florian Anderiasch [this message]
2019-02-27 19:49 Florian Anderiasch
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=aa99b980f14d5b0cb004e0e1b5c4ab1a@anderiasch.de \
--to=ml+wireguard@anderiasch.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).