Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Benedikt Morbach <benedikt.morbach@googlemail.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [PATCH] contrib: fix out-of-tree build with jerry-rig.sh
Date: Thu, 11 May 2017 14:30:45 +0200	[thread overview]
Message-ID: <CAC-H7H=LfyykpMx=vKQWA2Ag+89JOZ34o_2UF0Nf6pJjsMp1GQ@mail.gmail.com> (raw)
In-Reply-To: <CAHmME9qqPoXpf9-GpRRuQ4mSjGJ_Eh7Pn_vXPbWZXxYoLbRy6A@mail.gmail.com>

Hi Jason,

I started doing out-of-tree kernel builds with "make KBUILD_OUTPUT=/foo".
While it does work, it puts wireguards .o files in
/foo/net/../../../..../wireguard/src, which isn't exactly what I
expected/intended. By changing the path in the Makefile the .o files
end up in /foo/net/wireguard.

Thanks
Benedikt

  reply	other threads:[~2017-05-11 12:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-10 21:31 Benedikt Morbach
2017-05-11 10:25 ` Jason A. Donenfeld
2017-05-11 12:30   ` Benedikt Morbach [this message]
2017-05-11 19:54     ` 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='CAC-H7H=LfyykpMx=vKQWA2Ag+89JOZ34o_2UF0Nf6pJjsMp1GQ@mail.gmail.com' \
    --to=benedikt.morbach@googlemail.com \
    --cc=Jason@zx2c4.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).