From: Kalin KOZHUHAROV <me.kalin@gmail.com>
To: Dan Luedtke <mail@danrl.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Wireguard in OpenWRT/LEDE: FYI: Pull Request
Date: Wed, 16 Nov 2016 18:50:52 +0900 [thread overview]
Message-ID: <CAKXLc7fFctm__qAQ8N5Vzms_MLFXJe0hf1-A6GH8QMD8B+3zSA@mail.gmail.com> (raw)
In-Reply-To: <FE60D347-65AB-49AC-8ECC-8B5DD199DA53@danrl.com>
On Wed, Nov 16, 2016 at 6:34 PM, Dan Luedtke <mail@danrl.com> wrote:
> Hmm, could it be missing a line like
>
> $(INSTALL_DIR) $(1)/lib/netifd/proto/
>
> In the Makefile? Not sure why we would need to create it, shouldn't it be=
there?
>
> Kalin, could you try again with the installdir line?
>
Currently the Makefile had this in:
define Package/wireguard-tools/install
$(INSTALL_DIR) $(1)/usr/bin/
$(INSTALL_BIN) $(PKG_BUILD_DIR)/src/tools/wg $(1)/usr/bin/
$(INSTALL_BIN) ./files/wireguard.sh $(1)/lib/netifd/proto/
endef
I patched it:
--- a/srv/OpenWRT/openwrt/feeds/packages/net/wireguard/Makefile
2016-11-16 18:45:57.733060093 +0900
+++ b/srv/OpenWRT/openwrt/feeds/packages/net/wireguard/Makefile
2016-11-16 18:46:07.716948224 +0900
@@ -83,6 +83,7 @@
define Package/wireguard-tools/install
$(INSTALL_DIR) $(1)/usr/bin/
$(INSTALL_BIN) $(PKG_BUILD_DIR)/src/tools/wg $(1)/usr/bin/
+ $(INSTALL_DIR) $(1)/lib/netifd/proto/
$(INSTALL_BIN) ./files/wireguard.sh $(1)/lib/netifd/proto/
endef
And it seems to work now. I guess this looks as expected:
./build_dir/target-mips_34kc_musl-1.1.15/WireGuard-experimental-0.0.2016111=
0/ipkg-ar71xx/wireguard-tools/
=E2=94=9C=E2=94=80=E2=94=80 CONTROL
=E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 control
=E2=94=82 =E2=94=9C=E2=94=80=E2=94=80 postinst
=E2=94=82 =E2=94=94=E2=94=80=E2=94=80 prerm
=E2=94=9C=E2=94=80=E2=94=80 lib
=E2=94=82 =E2=94=94=E2=94=80=E2=94=80 netifd
=E2=94=82 =E2=94=94=E2=94=80=E2=94=80 proto
=E2=94=82 =E2=94=94=E2=94=80=E2=94=80 wireguard.sh
=E2=94=94=E2=94=80=E2=94=80 usr
=E2=94=94=E2=94=80=E2=94=80 bin
=E2=94=94=E2=94=80=E2=94=80 wg
(still compiling the rest)
Kalin.
next prev parent reply other threads:[~2016-11-16 9:48 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-13 22:35 Dan Lüdtke
2016-11-13 22:52 ` Dan Lüdtke
2016-11-15 16:01 ` Dan Lüdtke
2016-11-16 8:15 ` Baptiste Jonglez
2016-11-16 8:48 ` Kalin KOZHUHAROV
2016-11-16 9:34 ` Dan Luedtke
2016-11-16 9:50 ` Kalin KOZHUHAROV [this message]
2016-11-16 10:11 ` Dan Lüdtke
2016-11-16 16:55 ` Dan Lüdtke
2016-11-16 16:56 ` Jason A. Donenfeld
2016-11-16 16:58 ` Jason A. Donenfeld
2016-11-16 17:04 ` Dan Lüdtke
2016-11-16 17:45 ` Jason A. Donenfeld
2016-11-16 17:01 ` Dan Lüdtke
2016-12-12 12:03 Michal Kowalski
2016-12-12 13:27 ` Jason A. Donenfeld
2016-12-14 19:48 ` Dan Lüdtke
2016-12-14 21:07 ` Jason A. Donenfeld
2016-12-16 17:45 ` 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=CAKXLc7fFctm__qAQ8N5Vzms_MLFXJe0hf1-A6GH8QMD8B+3zSA@mail.gmail.com \
--to=me.kalin@gmail.com \
--cc=mail@danrl.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).