From: Kevin <anaknaga@inventati.org>
To: wireguard@lists.zx2c4.com
Subject: Trouble building WireGuard since December releases
Date: Mon, 22 Jan 2018 15:42:25 +0100 [thread overview]
Message-ID: <1516632145.2241.49.camel@inventati.org> (raw)
Hi all,
I've been having trouble building WireGuard on Solus since its December
snapshots. Earlier snapshots (e.g. November) still build without a
problem, even on new kernels. Does this have to do with Solus kernel
builds, or am I overlooking something?
user@t450s-solus ~/bin/WireGuard-0.0.20180118/src $ make debug
test -e include/generated/autoconf.h -a -e include/config/auto.conf ||
( \
echo >&2; \
echo >&2 " ERROR: Kernel configuration is invalid."; \
echo >&2 " include/generated/autoconf.h or
include/config/auto.conf are missing.";\
echo >&2 " Run 'make oldconfig && make prepare' on kernel src
to fix it."; \
echo >&2 ; \
/bin/false)
mkdir -p /home/user/bin/WireGuard-0.0.20180118/src/.tmp_versions ; rm
-f /home/user/bin/WireGuard-0.0.20180118/src/.tmp_versions/*
make -f ./scripts/Makefile.build obj=/home/user/bin/WireGuard-
0.0.20180118/src
make[2]: *** No rule to make target '/home/user/bin/WireGuard-
0.0.20180118/src/main.o', needed by '/home/user/bin/WireGuard-
0.0.20180118/src/wireguard.o'. Stop.
make[1]: *** [Makefile:1507: _module_/home/user/bin/WireGuard-
0.0.20180118/src] Error 2
make: *** [Makefile:39: module-debug] Error 2
next reply other threads:[~2018-01-22 14:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-22 14:42 Kevin [this message]
2018-01-22 15:23 ` Trouble building WireGuard since December releases Greg KH
2018-01-22 15:34 ` Jason A. Donenfeld
2018-01-22 15:53 ` Jason A. Donenfeld
2018-01-22 16:07 ` Jason A. Donenfeld
2018-01-24 18:49 ` Daniel Kahn Gillmor
2018-01-24 23:07 ` 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=1516632145.2241.49.camel@inventati.org \
--to=anaknaga@inventati.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.