All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <pbarker@toganlabs.com>
To: meta-virtualization@yoctoproject.org
Subject: [PATCH 2/2] runc-opencontainers: go.bbclass compile fixes
Date: Wed,  4 Oct 2017 10:40:26 +0000	[thread overview]
Message-ID: <1507113626-3022-3-git-send-email-pbarker@toganlabs.com> (raw)
In-Reply-To: <1507113626-3022-1-git-send-email-pbarker@toganlabs.com>

These fixes are needed due to updates to go.bbclass in oe-core. See commit
01a8d4537012ad93dc8510e9b762acdc8c4536c7 for more information.

Signed-off-by: Paul Barker <pbarker@toganlabs.com>
---
 recipes-containers/runc/runc-opencontainers_git.bb | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/recipes-containers/runc/runc-opencontainers_git.bb b/recipes-containers/runc/runc-opencontainers_git.bb
index 940ae95..902a93d 100644
--- a/recipes-containers/runc/runc-opencontainers_git.bb
+++ b/recipes-containers/runc/runc-opencontainers_git.bb
@@ -6,9 +6,11 @@ RUNC_VERSION = "1.0.0-rc4"
 PROVIDES += "virtual/runc"
 RPROVIDES_${PN} = "virtual/runc"
 
+GO_IMPORT = "import"
+
 do_compile_prepend() {
 	# Go looks in a src directory under any directory in GOPATH but
 	# runc-opencontainers uses 'vendor' instead of 'vendor/src'. We can fix
 	# this with a symlink.
-	ln -sfn . "${S}/vendor/src"
+	ln -sfn . "${S}/src/import/vendor/src"
 }
-- 
2.7.4



  parent reply	other threads:[~2017-10-04 10:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-04 10:40 [PATCH 0/2] runc-opencontainers updates Paul Barker
2017-10-04 10:40 ` [PATCH 1/2] runc-opencontainers: Update to v1.0.0-rc4 Paul Barker
2017-10-04 10:40 ` Paul Barker [this message]
2017-10-04 20:55   ` [PATCH 2/2] runc-opencontainers: go.bbclass compile fixes Bruce Ashfield

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=1507113626-3022-3-git-send-email-pbarker@toganlabs.com \
    --to=pbarker@toganlabs.com \
    --cc=meta-virtualization@yoctoproject.org \
    /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.